fund-list-filternpm
Advisory published Updated
fund-list-filter is a confirmed malicious npm package (MAL-2026-14380) 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-list-filter (npm)
What this malware does
On npm install, package.json's preinstall hook runs index.js which harvests installer host identifiers — os.hostname(), os.userInfo() username, local IPv4 addresses, home directory, INIT_CWD, public IP (fetched from api.ipify.org / icanhazip.com / ifconfig.me), DNS resolver IP/subnet, and the parent project's package.json metadata (name, author, repository, homepage) — and transmits them to the hardcoded Interactsh-style callback host da51rv0hb2uc72tg4gvgdepinjcallbk1.oast.fun. Exfiltration uses two channels: an HTTPS/HTTP POST to /poc/<uuid> on the callback host, and a hex-encoded DNS covert channel that splits the JSON payload into ≤60-character subdomain labels resolved against the callback host, designed to bypass egress filters that block outbound HTTP but permit DNS. The version number (999.9.12) and package name are consistent with a dependency-confusion probe.
The OpenSSF Package Analysis project identified 'fund-list-filter' @ 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-list-filter (version 999.9.12).
If you installed it — respond
fund-list-filter 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-list-filter 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-list-filter-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.