Which versions of fundraiserservpp are malicious?

The following npm versions of fundraiserservpp are flagged malicious: 1.9.0, 2.0.0. Treat any of these as compromised.

How do I remediate fundraiserservpp if I installed it?

fundraiserservpp 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 fundraiserservpp — how do I know if it already compromised me?

If fundraiserservpp 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.

Is fundraiserservpp part of a known attack campaign?

Yes — fundraiserservpp is associated with the IN-MAL-2026-014837, IN-MAL-2026-015807 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 fundraiserservpp across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for fundraiserservpp (2 malicious versions).

Malicious package

fundraiserservppnpm

Advisory published Aug 5, 2026Updated Aug 5, 2026

fundraiserservpp is a confirmed malicious npm package (MAL-2026-12386) that opens a backdoor for remote access (malicious versions 1.9.0, 2.0.0). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in fundraiserservpp (npm)

MAL-2026-12386

Immediate action

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

npm uninstall fundraiserservpp

What this malware does

[email protected] runs node index.js as a preinstall lifecycle script on npm install. The script collects host metadata from the installer machine — os.hostname(), os.platform(), os.arch(), the user home directory path, and configured DNS servers — and issues an HTTPS POST to a hardcoded Burp Collaborator subdomain (mrh99ucv1u3kyeba1020ae2t7kdc12pr.oastify.com/hit) with that data as a JSON body. The beacon fires automatically at install time with no user interaction. The destination is an attacker-controlled out-of-band interaction endpoint typical of dependency-confusion reconnaissance, confirming to the operator that the package name was successfully resolved and installed inside a target build environment.

Malicious versions

2 flagged

1.9.02.0.0

Indicators of compromise (SHA-256)

542a9a32b033b5188849fa81e6ec448528308f1251256d861ee7917a7cdcb473

0bca913238607a18079a675e2fe652c25c04c2bbc62f5c577bb2b6d2424cd4a8

Detection & response playbook

Backdoor / remote access

Find it
Search your lockfiles and build artifacts for fundraiserservpp (2 malicious versions).
If you installed it — respond
fundraiserservpp 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 fundraiserservpp 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

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

Campaign

IN-MAL-2026-014837IN-MAL-2026-015807

References

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks fundraiserservpp-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