Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
Malicious package

fanduelnpm

fanduel is a confirmed malicious npm package (MAL-2026-3334) that executes malicious code on install (malicious versions 100.0.0, 100.2.0, 100.4.0…). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in fanduel (npm)

MAL-2026-3334
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
npm uninstall fanduel

What this malware does

The package fanduel was found to contain malicious code.

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 'fanduel' @ 100.5.0 (npm) as malicious.

It is considered malicious because:

  • The package communicates with a domain associated with malicious activity.

Malicious versions

4 flagged
100.0.0100.2.0100.4.0100.5.0

Indicators of compromise (SHA-256)

49d980743cd761f6fb629d32e14864e720d1269e4208ec9e0f075c5e9f6eb433
b2d9b4e8ab1ef054d5774929963bc61b004f7914e48179850c51f77e67410a41
031c1b526196f26d62b4ef54e450a2b85f88b3eab78f69f17e73c83f49ebabef

Detection & response playbook

Malicious package
  1. Find it

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

  2. If you installed it — respond

    Remove fanduel from your project and lockfile, then assume any secrets accessible to the build or runtime were exposed: rotate API keys, tokens, and credentials, and audit for unexpected outbound activity or persistence.

  3. Did it already run?

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

  4. How O3 protects you

    O3 blocks fanduel 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. fanduel on npm has been identified as a malicious package (versions 100.0.0, 100.2.0, 100.4.0, 100.5.0 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-mjhc-2rfg-vh93

References

Credits

  • Amazon Inspector · finder
  • OpenSSF: Package Analysis · finder

Detect & block this

O3 blocks fanduel-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the malicious outbound activity and severs the channel.

Explore

fanduel (npm) malicious package — MAL-2026-3334 | O3 Security