Which versions of fundraiserserv are malicious?

The following npm versions of fundraiserserv are flagged malicious: 1.0.0, 2.0.0, 28.0.0. Treat any of these as compromised.

How do I remediate fundraiserserv if I installed it?

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.

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

If fundraiserserv 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 fundraiserserv part of a known attack campaign?

Yes — fundraiserserv is associated with the GHSA-r4jv-gh5g-mhgg, IN-MAL-2026-011086, IN-MAL-2026-013292 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 fundraiserserv 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 fundraiserserv (3 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging fundraiserserv across your stack and pipelines.

Malicious package

fundraiserservnpm

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)

MAL-2026-5172

Immediate action

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

npm uninstall fundraiserserv

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

3 flagged

1.0.02.0.028.0.0

Indicators of compromise (SHA-256)

c27dec042a9f69f24c1a2c860af27a2625740dbd7b7fc3d059659fae6f628c25

a7d27784fadb684086b183d320d829361b876e5a3cafa7a6807988127c58f4e6

be2bb2ca91f34ce861258ecf47e6ec3f195ed120be0f09210b60eef8aadfb8a2

64e919ea2c2e20797cb7e1d94264d2b5cf9365c1e469be8a25de011f33c7cf51

355932d2c6fa86a575e9b4c86225d4da9d8d51990d5eeb88649c6d8cf5564090

Detection & response playbook

Credential / info stealer

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for fundraiserserv (3 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging fundraiserserv across your stack and pipelines.
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 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 fundraiserserv 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. fundraiserserv on npm has been identified as a malicious package (versions 1.0.0, 2.0.0, 28.0.0 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-r4jv-gh5g-mhggIN-MAL-2026-011086IN-MAL-2026-013292

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.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database