rebrandly-domains-digger (npm) · Malicious Code
Affects rebrandly-domains-diggerSource GCVE Database
Malicious package : remove rebrandly-domains-digger and rotate any secrets on hosts that installed it.
Data as of 30 Jun 2026, 23:35 UTC
Malicious package
Published to npm · OSV MAL-2026-6572
What to do
Remove rebrandly-domains-digger from every project, lockfile and image that pulls it in. Treat any host that installed it as compromised: rotate the credentials, tokens and keys it could read, from a clean machine.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| npmrebrandly-domains-digger | Affected
| Fixed in– |
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
Description
--- _-= Per source details. Do not edit below this line.=-_ ## Source: amazon-inspector (4d1744d2a299b9ef0526f49b4b2297fcd6c72581c51a3359801db56318d8cfda) The package declares a `preinstall` hook that runs `node callback.js`. On `npm install`, `callback.js` collects installer-side identifiers — `os.hostname()`, `os.userInfo().username`, `process.cwd()`, the configured npm registry, and CI repo-identifying environment variables (e.g. GITHUB_REPOSITORY) — and issues an HTTP GET to `http://75.119.137.232:31337/depconfuse?pkg=...` carrying those values as query parameters. The version number `9999.0.0` and the `/depconfuse` path are consistent with a dependency-confusion reconnaissance beacon designed to identify organizations that internally use a package named `rebrandly-domains-digger`, so the attacker can target follow-on confusion attacks against their private/internal package namespace. The destination is a hardcoded bare IPv4 on a non-standard port over plain HTTP, with no relation to any legitimate publisher infrastructure. ## Source: ghsa-malware (bbcd32c6b7fb70ec11491e443913decc337d2fd8d3b5d9fcfbe973c1c1518ee3) 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.