rebrandly-domains-diggernpm
Advisory published Updated
rebrandly-domains-digger is a confirmed malicious npm package (MAL-2026-6572) that steals credentials and exfiltrates sensitive data (malicious version 9999.0.0). Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in rebrandly-domains-digger (npm)
What this malware does
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.
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.
Malicious versions
Indicators of compromise (SHA-256)
Detection & response playbook
Credential / info stealerFind it
Search your lockfiles and build artifacts for rebrandly-domains-digger (version 9999.0.0).
If you installed it — respond
rebrandly-domains-digger is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.
Did it already run?
If rebrandly-domains-digger was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.
Frequently asked questions
Campaign
References
Credits
- Amazon Inspector · finder
Detect & block this
O3 blocks rebrandly-domains-digger-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.