evilpostinstall
Affected
- Versions:
0.2.0,0.3.0,0.4.0,0.5.0,0.6.0,0.7.0,0.7.1,0.8.0,0.9.0,0.9.1,0.9.2,0.9.3,4127000.0.1,4192168.1.100,49.13.4074225
Fixed versions
None listed
Fix
No fixed version is listed.
Advisory
Also known as: None
Malicious package Its source marks this package as malicious: it is not a vulnerability in a legitimate one.
Malicious code in evilpostinstall (npm)
---
_-= 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:
Not rated by the source.
0.2.0, 0.3.0, 0.4.0, 0.5.0, 0.6.0, 0.7.0, 0.7.1, 0.8.0, 0.9.0, 0.9.1, 0.9.2, 0.9.3, 4127000.0.1, 4192168.1.100, 49.13.4074225None listed
No fixed version is listed.
Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.
Check your own computer: guard packages check
Source: OpenSSF Malicious Packages · Apache-2.0