Malicious code in mham-js (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-14478
Published--- _-= Per source details. Do not edit below this line.=-_ ## Source: amazon-inspector (f0dc3c71ee333b190e3e7202f7a222b4fe242fd50974cda9ec122b4200bd5f4f) On import of mham-js, src/api/session-api.js runs top-level code that reads a file outside the package tree at../../../../public/logo.ico, decrypts its contents with CryptoJS.DES using the hardcoded password 'bf497c0b9cee', then spawns a detached node subprocess and pipes the decrypted bytes to its stdin for execution. The loader is disguised with cover-story names ('readLogoIco', 'rsa_exec', 'ThetaSDK initialization error'), and the README states the package does nothing on import, contradicting the actual behavior. The executed payload is stored encrypted outside the tarball, is not verified or documented, and consists of opaque attacker-controlled bytes handed directly to the Node interpreter as arbitrary code.
- Source published
- 25 Aug 2026 07:09:24 UTC
- Source modified
- 25 Aug 2026 23:49:44 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.