Which versions of @rocketreach/rr-components are malicious?

The following npm versions of @rocketreach/rr-components are flagged malicious: 9999.0.0. Treat any of these as compromised.

How do I remediate @rocketreach/rr-components if I installed it?

@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.

I already installed @rocketreach/rr-components — how do I know if it already compromised me?

If @rocketreach/rr-components 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 @rocketreach/rr-components part of a known attack campaign?

Yes — @rocketreach/rr-components is associated with the IN-MAL-2026-003319, IN-MAL-2026-003318 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 @rocketreach/rr-components 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 @rocketreach/rr-components (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 @rocketreach/rr-components across your stack and pipelines.

Malicious package

@rocketreach/rr-componentsnpm

Malicious code in @rocketreach/rr-components (npm) Remove it immediately and rotate any exposed credentials.

MAL-2026-4427

Immediate action

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

npm uninstall @rocketreach/rr-components

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.

Malicious versions

1 flagged

9999.0.0

Indicators of compromise (SHA-256)

8aecbc11b82f2faa08cc6f45e3829bae6e611e1dca9ed7af5acba9f7a8155b11

c1c16148ad4c13ad5d5cbfe951d9ca934a0912ab5ad75c3b4afee19be86172fa

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 @rocketreach/rr-components (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 @rocketreach/rr-components across your stack and pipelines.
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 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 @rocketreach/rr-components 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. @rocketreach/rr-components 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-003319IN-MAL-2026-003318

References

npmjs.com

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.

Malware detection Runtime egress monitoring