rebrandly-domains-search-clientnpm
Malicious code in rebrandly-domains-search-client (npm) Remove it immediately and rotate any exposed credentials.
What this malware does
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.
Malicious versions
Indicators of compromise (SHA-256)
Detection & response playbook
Credential / info stealerFind it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for rebrandly-domains-search-client (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-search-client across your stack and pipelines.
If you installed it — respond
rebrandly-domains-search-client 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-search-client 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-search-client 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
Campaign
References
Credits
- Amazon Inspector · finder
Detect & block this
O3 blocks rebrandly-domains-search-client-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.