Which versions of fundraiserservicepp are malicious?

The following npm versions of fundraiserservicepp are flagged malicious: 1.5.0, 1.7.0. Treat any of these as compromised.

How do I remediate fundraiserservicepp if I installed it?

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.

I already installed fundraiserservicepp — how do I know if it already compromised me?

If fundraiserservicepp was ever installed, its post-install/runtime payload may have already executed. O3's L7 egress monitoring and runtime eBPF sensors detect the credential exfiltration or command-and-control callback after install and block the malicious outbound channel, so you catch and contain the actual compromise — not just the presence of the package.

Is fundraiserservicepp part of a known attack campaign?

Yes — fundraiserservicepp is associated with the IN-MAL-2026-011110, IN-MAL-2026-014930 campaign. Packages in the same campaign often share infrastructure and payloads, so check whether any related packages are also in your dependency tree.

How do I find fundraiserservicepp across my projects, lockfiles, and CI pipelines?

Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for fundraiserservicepp (2 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging fundraiserservicepp across your stack and pipelines.

Malicious package

fundraiserserviceppnpm

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)

MAL-2026-11055

Immediate action

Remove the package, then rotate any secrets the build/runtime could reach.

npm uninstall fundraiserservicepp

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

2 flagged

1.5.01.7.0

Indicators of compromise (SHA-256)

cefb4588a67439c112176df4b9af71d40a1e2a12e0bf81ef200affa79e0cb0e0

8ee5547a9548aa8d9a79a6b9b8a8ded3a27c1164c780957ce31645c39253ec04

6356b654b692d4c1222f3dc31dcfad683a6e193a41484d3c617c7c8d52db2313

Detection & response playbook

Backdoor / remote access

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for fundraiserservicepp (2 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging fundraiserservicepp across your stack and pipelines.
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 ever installed, its post-install/runtime payload may have already executed. O3's L7 egress monitoring and runtime eBPF sensors detect the credential exfiltration or command-and-control callback after install and block the malicious outbound channel, so you catch and contain the actual compromise — not just the presence of the package.
How O3 protects you
O3 blocks fundraiserservicepp before install through its supply-chain scanner, and if it has already run, detects and severs the exfiltration or C2 callback at runtime through L7 egress monitoring and eBPF.

Frequently asked questions

No. fundraiserservicepp on npm has been identified as a malicious package (versions 1.5.0, 1.7.0 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-011110IN-MAL-2026-014930

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.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database