fund-portfolio
Affected
- Versions:
999.9.12
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 fund-portfolio (npm)
---
_-= Per source details. Do not edit below this line.=-_
Source: amazon-inspector (27ba065e8759299d381ed1c7abd5e7721037b4ea969a384a9e70cfb6bb799e17)
Package declares scripts.preinstall: node index.js, causing index.js to run automatically on npm install. The script collects hostname, username, home directory, INIT_CWD, local IPv4, public egress IP (via api.ipify.org, icanhazip.com, ifconfig.me), DNS resolver IP and client subnet (via o-o.myaddr.l.google.com), and the parent project's package.json fields (name, author, repository, homepage). The collected JSON is exfiltrated to the hardcoded callback host da51rv0hb2uc72tg4gvgdepinjcallbk1.oast.fun (Interactsh/OAST) via DNS-chunked queries and HTTPS POST to /poc/<uuid>. The unscoped name is published at version 999.9.12 to defeat internal resolvers that fall back to the public npm registry, so any build referencing fund-portfolio without a private-registry pin will resolve to and execute this payload.
Source: ossf-package-analysis (ffad2f6c37441c2924e67b1d506d9c26dc9cb2fae325b74a596102ea5ed403bf)
The OpenSSF Package Analysis project identified 'fund-portfolio' @ 999.9.12 (npm) as malicious.
It is considered malicious because:
Not rated by the source.
999.9.12None 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