Malicious code in module-relpath (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-14561
Published--- _-= Per source details. Do not edit below this line.=-_ ## Source: amazon-inspector (03bf564e2647cb828bb130eaaba71b21fb6d78928cb6e3a74165bbb2fc546b98) The package presents itself as `relative-import-path` (README title, homepage and repository URL point at github.com/marko-js/relative-import-path, and the.d.ts documents only `relativeImportPath`), but the CJS bundle at dist/index.js does not export the documented API. Instead it exports a single undocumented function `modshit(moduleName, size)` that reads `public/logo.png` from the current working directory, slices the trailing `size` bytes off the file, resolves the path `../${moduleName}/public/logo.png` relative to its own directory, creates parent directories as needed, and writes those trailing bytes to that location. The effect is a steganographic second-stage helper: bytes appended to the tail of a PNG are extracted and planted into an arbitrary sibling package's directory on the installer's disk under the caller's chosen name. The exported symbol does not match the documented API, is named to obscure its purpose, and provides a primitive whose only use is smuggling payload bytes hidden inside an image into other node_modules entries. ## Source: ghsa-malware (97776a8746c6c0d75fee50594f26150e0a791d97ade2056c489c1ca8da0196ae) 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
- 27 Aug 2026 13:51:36 UTC
- Source modified
- 31 Aug 2026 18:31:26 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.