rebrandly-domains-search-client
Affected
- introduced
0(semver)
Fixed versions
None listed
Fix
No fixed version is listed.
Advisory
Also known as: GHSA-6q7q-73w8-xvcf
Malicious package Its source marks this package as malicious: it is not a vulnerability in a legitimate one.
Malicious code in rebrandly-domains-search-client (npm)
---
_-= Per source details. Do not edit below this line.=-_
Source: amazon-inspector (7d4464320c8530d582d35f85ce95045182d82e1dd63a830644bcb68f05bdf10e)
Package [email protected] is an empty module (index.js exports an empty object) whose package.json preinstall hook runs node callback.js. That script collects installer-side identifiers — os.hostname(), os.userInfo().username, process.cwd(), npm_config_registry, and CI repository env vars including GITHUB_REPOSITORY, CI_PROJECT_PATH, and BUILD_REPOSITORY_NAME — and transmits them via plain-HTTP GET to http://75.119.137.232:31337/depconfuse with the package name, hostname, user, cwd, configured registry, and CI repo as query parameters. The name targets the Rebrandly namespace and the version 9999.0.0 is chosen to outrank any private internal package of the same name during npm resolution. The package has no functional code; its sole on-install effect is the reconnaissance beacon used to identify networks where an internal name resolves, enabling targeted dependency-confusion follow-up.
Source: ghsa-malware (6e75c8eb2d3a4cddc86e386eff1e2a6616e6e7d4a082b5185651b9d8c2fccfbf)
Any computer that has this package installed or running should be considered fully compromised. All secrets and keys stored on that computer should be rotated immediately from a different computer. The package should be removed, but as full control of the computer may have been given to an outside entity, there is no guarantee that removing the package will remove all malicious software resulting from installing it.
Not rated by the source.
0 (semver)None listed
No fixed version is listed.
Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.
Check your own computer: guard packages check
Source: OpenSSF Malicious Packages · Apache-2.0