@pelmnaads/naads-common-logger
Affected
- Versions:
19999.0.1
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 @pelmnaads/naads-common-logger (npm)
---
_-= Per source details. Do not edit below this line.=-_
Source: amazon-inspector (68990dfacdc750bf464d646aca4855c2dd23bbefcadef1d9638e2d663a23fc57)
The package is published to the public npm registry under @pelmnaads/naads-common-logger with version 19999.0.1 — the canonical dependency-confusion pattern, where an abnormally high version is used to make npm's resolver prefer this public package over a private internal package of the same name. On npm install, a preinstall lifecycle script (preinstall.js:5-9) makes an HTTPS GET to h5nvwrz2815ubw84cpkwhezm5db9z1nq.b.mburpcollab.com with query parameters package=<npm_package_name>&hostname=<os.hostname()>, transmitting the installer's hostname off-host to a Burp Collaborator out-of-band interaction endpoint. The README states this is an authorized security test, but the code path and effect on an unsuspecting installer are identical to a hostile dependency-confusion attack: build hosts silently disclose their identity to a third-party domain during npm install, with no opt-in. Any build system that resolves this package (e.g., an internal Pelmorex pipeline expecting the private @pelmnaads/naads-common-logger) would leak hostname data.
Not rated by the source.
19999.0.1None 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