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

@draftauth/corenpm

Malicious code in @draftauth/core (npm) Remove it immediately and rotate any exposed credentials.

MAL-2026-3595
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
npm uninstall @draftauth/core

What this malware does

This package was compromised as part of the "Mini Shai-Hulud is back" worm by the TeamPCP threat actor.

The package will steal credentials and then propogate it to every package it has access to. The package also attempts to remain persistent.

Malicious versions

2 flagged
0.13.10.13.2

Indicators of compromise (SHA-256)

5e1924464368f0c5816ee84e000cc47017f44045140feafbbc9e685d847ed5a5

Detection & response playbook

Credential / info stealer
  1. Find it

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

  2. If you installed it — respond

    @draftauth/core 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.

  3. Did it already run?

    If @draftauth/core 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 @draftauth/core 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. @draftauth/core on npm has been identified as a malicious package (versions 0.13.1, 0.13.2 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

References

Detect & block this

O3 blocks @draftauth/core-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.

@draftauth/core (npm) malicious package — MAL-2026-3595 | O3 Security