Malicious code in evilpostinstall (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-15625
Published--- _-= Per source details. Do not edit below this line.=-_ ## Source: amazon-inspector (846e500b06f58769a2cb833be8e726ab1db04b327f4c614da6642eb46ae7dfe5) The package's postinstall lifecycle hook pipes the output of `env` through `nc` to a host reconstructed at install time from the package version string via `cut -b 2-4` and `cut -b 5-`. For version 4127000.0.1 the destination decodes to 127.0.0.1:888; the sibling artifact evilpostinstall-192.168.1.100.tgz uses the same slicing scheme to target 192.168.1.100. On `npm install`, the full installer environment - including any CI secrets, tokens, and API keys present in environment variables - is transmitted to the reconstructed host over TCP port 888. package.json also declares a self-referencing dependency `evilpostinstall: ^4192168.1.100`, whose version field encodes a second destination IP under the same scheme, causing npm to resolve and install an additional package instance whose own postinstall repeats the exfiltration against that address. The destination is deliberately hidden from static scanners by being reconstructed from the version field rather than written as an IP literal, and no source files are shipped - the manifest itself is the payload. ## Source: ossf-package-analysis (c4f0004a363677a7dc0429c4cf4bacafcd3bbdab0c95e1e7851d44b543d7e486) The OpenSSF Package Analysis project identified 'evilpostinstall' @ 4127000.0.1 (npm) as malicious. It is considered malicious because: - The package executes one or more commands associated with malicious behavior.
- Source published
- 31 Aug 2026 15:40:53 UTC
- Source modified
- 3 Sep 2026 06:45:05 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.