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.
AI Analysis
Technical Summary
The [email protected] npm package is an empty module whose package.json preinstall hook executes a script that gathers installer-side information including hostname, username, current working directory, npm registry configuration, and continuous integration repository environment variables. This data is transmitted via plain HTTP GET requests to a remote IP address (http://75.119.137.232:31337/depconfuse) with the goal of identifying environments where an internal package name resolves, enabling follow-up targeted dependency confusion attacks. The package version 9999.0.0 is deliberately chosen to outrank internal packages during npm resolution. There is no functional code beyond this reconnaissance behavior.
Potential Impact
The package leaks sensitive environment and system information to an external attacker-controlled server during installation. This information disclosure can aid attackers in identifying targets for dependency confusion attacks within internal networks. There is no direct code execution or payload beyond data exfiltration, and no known exploits in the wild have been reported.
Mitigation Recommendations
No official patch or fix is available for this malicious package version. Users should avoid installing the rebrandly-domains-search-client package version 9999.0.0 from untrusted sources. Implement strict package source verification and use scoped or private registries to prevent dependency confusion. Monitor package dependencies for unexpected or suspicious versions. Since this is a malicious package published to npm, removing or blocking this version from internal registries and build pipelines is recommended.
Malicious code in rebrandly-domains-search-client (npm)
Description
--- _-= 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.
Affected software
Run on your own infrastructure? Check whether these packages are installed with threat-finder — our free open-source scanner.
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
The [email protected] npm package is an empty module whose package.json preinstall hook executes a script that gathers installer-side information including hostname, username, current working directory, npm registry configuration, and continuous integration repository environment variables. This data is transmitted via plain HTTP GET requests to a remote IP address (http://75.119.137.232:31337/depconfuse) with the goal of identifying environments where an internal package name resolves, enabling follow-up targeted dependency confusion attacks. The package version 9999.0.0 is deliberately chosen to outrank internal packages during npm resolution. There is no functional code beyond this reconnaissance behavior.
Potential Impact
The package leaks sensitive environment and system information to an external attacker-controlled server during installation. This information disclosure can aid attackers in identifying targets for dependency confusion attacks within internal networks. There is no direct code execution or payload beyond data exfiltration, and no known exploits in the wild have been reported.
Mitigation Recommendations
No official patch or fix is available for this malicious package version. Users should avoid installing the rebrandly-domains-search-client package version 9999.0.0 from untrusted sources. Implement strict package source verification and use scoped or private registries to prevent dependency confusion. Monitor package dependencies for unexpected or suspicious versions. Since this is a malicious package published to npm, removing or blocking this version from internal registries and build pipelines is recommended.
Technical Details
- Gcve Source
- db.gcve.eu
- Osv Id
- MAL-2026-6573
- Osv Schema Version
- 1.7.4
- Aliases
- []
- Ecosystems
- ["npm"]
- Database Specific Severity
- null
- Cvss Version
- null
Threat ID: 6a42ed7d27e9c79719939d00
Added to database: 06/29/2026, 22:11:09 UTC
Last enriched: 06/29/2026, 22:43:32 UTC
Last updated: 07/27/2026, 11:47:27 UTC
Views: 27
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
External Links
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.