fundraiserserviceppnpm
Advisory published Updated
fundraiserservicepp is a confirmed malicious npm package (MAL-2026-11055) that opens a backdoor for remote access (malicious versions 1.5.0, 1.7.0). Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in fundraiserservicepp (npm)
What this malware does
On npm install, the package's preinstall lifecycle executes index.js which collects os.hostname(), os.platform(), and os.arch() and POSTs them as JSON over HTTPS to the hardcoded subdomain rpke7za0zz1pwj9fz5058j0y5pbgz82wr.oastify.com — a Burp Collaborator out-of-band collector. The package provides no advertised functionality beyond this beacon and matches the dependency-confusion probe shape, with installer host identifiers leaving the machine automatically to a third-party OOB endpoint the installer did not opt into.
The OpenSSF Package Analysis project identified 'fundraiserservicepp' @ 1.5.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
Backdoor / remote accessFind it
Search your lockfiles and build artifacts for fundraiserservicepp (2 malicious versions).
If you installed it — respond
fundraiserservicepp establishes remote access, so treat any host that installed it as fully compromised. Isolate the machine, remove the package, rotate all credentials it could reach, and rebuild from a trusted image rather than cleaning in place — a backdoor may have planted additional persistence.
Did it already run?
If fundraiserservicepp 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 fundraiserservicepp-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the C2 callback and severs the channel.