Malicious code in @rocketreach/rr-components (npm)
Exploitation and risk
Source statusCISA KEV lists vulnerabilities known to be exploited. FIRST EPSS estimates the likelihood of exploitation in the next 30 days. An unavailable score does not mean zero risk.
Which CVEs have scores here?
This view includes predictions for CVE identifiers explicitly listed in public NuGet advisories. Microsoft release pages have their own prediction coverage. Check source status for the scope and latest checks.
No exploitation or prediction data is available here for these CVEs. This does not mean they are safe or unlikely to be exploited.
osv · MAL-2026-4427
Published--- _-= Per source details. Do not edit below this line.=-_ ## Source: amazon-inspector (c1c16148ad4c13ad5d5cbfe951d9ca934a0912ab5ad75c3b4afee19be86172fa) 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. ## Source: ghsa-malware (3b9765637da4d6feb524bd1a160685bf99f36e8347830ddba30b95979e72e58b) 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.
- Source published
- 20 May 2026 00:31:29 UTC
- Source modified
- 13 Aug 2026 22:15:13 UTC
- Saved here
- 24 Oct 2026 13:17:17 UTC
- Source terms
- OSV · upstream source license applies
Original source record · Cite this exact observation · Complete original publisher JSON
Source: osv · OSV · upstream source license applies. The publisher's wording is preserved. ChangeIntel groups the information and labels changes. The JSON record includes additional source fields.