Malicious code in cbc97b7a (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-15878
Published--- _-= Per source details. Do not edit below this line.=-_ ## Source: amazon-inspector (7d772b04ff3be605aae9022f0462b9834f488dbb6c1397b7cc1075bb68db63c0) The tarball ships only package.json with no code, scripts, main, or bin. The description field contains a ~41KB base64-encoded POSIX shell script that, when decoded and executed, downloads an xmrig cryptominer from gitlab.com/albertotrindade131/al and a github.com/lucas77335/xmrig-amd mirror, installs cron-based persistence, and mines Monero to the hardcoded pool xmr.kryptex.network:8029 with an embedded wallet/worker identifier. Operational strings (pool host, wallet, miner URLs, fallback bare-IP C2 hosts 66.23.199.44, 45.94.31.89, 139.59.59.33, 154.89.152.115, 84.21.173.223, 142.132.131.238) are individually base64-encoded and decoded at runtime via a helper function. The payload script self-references https://registry.npmjs.org/cbc97b7a/latest, indicating the package is designed to be pulled by a companion loader that fetches this metadata and pipes the decoded description to sh, delivering miner installation, persistence, and secondary C2 fetches to the installer. ## Source: ghsa-malware (eaba3d6da8c9f60e47cd6aef7d9f02e3204d556589e4af9cb1cbcde06ab3b17b) 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
- 3 Sep 2026 08:59:06 UTC
- Source modified
- 4 Sep 2026 06:45:07 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.