@rocketreach/rr-componentsnpm
Advisory published Updated
@rocketreach/rr-components is a confirmed malicious npm package (MAL-2026-4427) 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 @rocketreach/rr-components (npm)
What this malware does
On npm install, both preinstall and postinstall lifecycle hooks execute postinstall.js, which collects host identifiers (hostname, platform, arch, OS username, cwd, Node version) and the full sorted list of process.env key names, then POSTs the JSON payload to a hardcoded https://webhook.site/d81181e1-e40b-478f-a0b4-f18069f9f677 collector. The package name @rocketreach/rr-components at version 9999.0.0 together with the self-identifying proof: "dependency-confusion-poc" field in the payload is the canonical dependency-confusion shape: publishing a high-version package under a target organization's private scope to public npm so that any misconfigured internal build resolves it. Even environment variable NAMES (not values) leak CI secret-naming schemes useful for follow-on attacks. Fires automatically on install with no user interaction.
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 @rocketreach/rr-components (version 9999.0.0).
If you installed it — respond
@rocketreach/rr-components 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 @rocketreach/rr-components 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 @rocketreach/rr-components-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.