fundraiserservnpm
Advisory published Updated
fundraiserserv is a confirmed malicious npm package (MAL-2026-5172) that steals credentials and exfiltrates sensitive data (malicious versions 1.0.0, 2.0.0, 28.0.0). Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in fundraiserserv (npm)
What this malware does
package.json declares scripts.preinstall = 'node index.js', which runs automatically on npm install. index.js collects host identifiers (os.hostname, os.platform, os.arch, os.homedir, dns.getServers) and POSTs them to gyi3gojp8oae58i48u9uh89neek681wq.oastify.com/hit, a Burp Collaborator out-of-band subdomain. The package self-describes as a dependency-confusion proof of concept; the shipped code is a working install-time exfiltration beacon that reports installation of the name to an attacker-controlled OOB endpoint.
Any computer that has this package installed or running should be considered fully compromised. All secrets and keys stored on that computer should be rotated immediately from a different computer. The package should be removed, but as full control of the computer may have been given to an outside entity, there is no guarantee that removing the package will remove all malicious software resulting from installing it.
The OpenSSF Package Analysis project identified 'fundraiserserv' @ 28.0.0 (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 fundraiserserv (3 malicious versions).
If you installed it — respond
fundraiserserv 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 fundraiserserv 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 fundraiserserv-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.