fund-portfolionpm
Advisory published Updated
fund-portfolio is a confirmed malicious npm package (MAL-2026-14381) that steals credentials and exfiltrates sensitive data (malicious version 999.9.12). Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in fund-portfolio (npm)
What this malware does
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.
The OpenSSF Package Analysis project identified 'fund-portfolio' @ 999.9.12 (npm) as malicious.
It is considered malicious because:
- The package communicates with a domain associated with malicious activity.
Malicious versions
Indicators of compromise (SHA-256)
Detection & response playbook
Credential / info stealerFind it
Search your lockfiles and build artifacts for fund-portfolio (version 999.9.12).
If you installed it — respond
fund-portfolio is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.
Did it already run?
If fund-portfolio was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.
Frequently asked questions
Campaign
References
Credits
- Amazon Inspector · finder
- OpenSSF: Package Analysis · finder
Detect & block this
O3 blocks fund-portfolio-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.