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

seanp-test-package-do-not-use2npm

Malicious code in seanp-test-package-do-not-use2 (npm) Remove it immediately and rotate any exposed credentials.

MAL-2026-79
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
npm uninstall seanp-test-package-do-not-use2

What this malware does

The package seanp-test-package-do-not-use2 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.

Malicious versions

all versions

Every published version of this package is considered malicious — remove it entirely.

Indicators of compromise (SHA-256)

13f418126723a2c3e194bf36b982e44701ecc22867dc329fa393199d4d7fa8a4
99e839ce8a19ba7b81bda65289233cd34aa7bc4daba6d742f102288bbc5e514d

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 seanp-test-package-do-not-use2 (all published versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging seanp-test-package-do-not-use2 across your stack and pipelines.

  2. If you installed it — respond

    Remove seanp-test-package-do-not-use2 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 seanp-test-package-do-not-use2 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 seanp-test-package-do-not-use2 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. seanp-test-package-do-not-use2 on npm has been identified as a malicious package (all published versions flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-fm2f-ghwv-hvrw

References

Credits

  • Amazon Inspector · finder

Detect & block this

O3 blocks seanp-test-package-do-not-use2-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.

Malware detection Runtime egress monitoring
seanp-test-package-do-not-use2 (npm) malicious package — MAL-2026-79 | O3 Security