Which versions of rebrandly-domains-digger are malicious?

The following npm versions of rebrandly-domains-digger are flagged malicious: 9999.0.0. Treat any of these as compromised.

How do I remediate rebrandly-domains-digger if I installed it?

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.

I already installed rebrandly-domains-digger — how do I know if it already compromised me?

If rebrandly-domains-digger was ever installed, its post-install/runtime payload may have already executed. O3's L7 egress monitoring and runtime eBPF sensors detect the credential exfiltration or command-and-control callback after install and block the malicious outbound channel, so you catch and contain the actual compromise — not just the presence of the package.

Is rebrandly-domains-digger part of a known attack campaign?

Yes — rebrandly-domains-digger is associated with the IN-MAL-2026-007703, GHSA-44wx-4683-p2h3 campaign. Packages in the same campaign often share infrastructure and payloads, so check whether any related packages are also in your dependency tree.

How do I find rebrandly-domains-digger across my projects, lockfiles, and CI pipelines?

Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for rebrandly-domains-digger (version 9999.0.0). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging rebrandly-domains-digger across your stack and pipelines.

Malicious package

rebrandly-domains-diggernpm

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)

MAL-2026-6572

Immediate action

Remove the package, then rotate any secrets the build/runtime could reach.

npm uninstall rebrandly-domains-digger

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

1 flagged

9999.0.0

Indicators of compromise (SHA-256)

4d1744d2a299b9ef0526f49b4b2297fcd6c72581c51a3359801db56318d8cfda

bbcd32c6b7fb70ec11491e443913decc337d2fd8d3b5d9fcfbe973c1c1518ee3

Detection & response playbook

Credential / info stealer

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for rebrandly-domains-digger (version 9999.0.0). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging rebrandly-domains-digger across your stack and pipelines.
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 ever installed, its post-install/runtime payload may have already executed. O3's L7 egress monitoring and runtime eBPF sensors detect the credential exfiltration or command-and-control callback after install and block the malicious outbound channel, so you catch and contain the actual compromise — not just the presence of the package.
How O3 protects you
O3 blocks rebrandly-domains-digger before install through its supply-chain scanner, and if it has already run, detects and severs the exfiltration or C2 callback at runtime through L7 egress monitoring and eBPF.

Frequently asked questions

No. rebrandly-domains-digger on npm has been identified as a malicious package (version 9999.0.0 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-007703GHSA-44wx-4683-p2h3

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.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database