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

whatsapp-core-auth-drzaknpm

Malicious code in whatsapp-core-auth-drzak (npm) Remove it immediately and rotate any exposed credentials.

MAL-2026-1404
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
npm uninstall whatsapp-core-auth-drzak

What this malware does

The package whatsapp-core-auth-drzak 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

1 flagged
99.9.9

Indicators of compromise (SHA-256)

227cb525f5cae8e179d17d90b8431bed4e85d8d37c66a94fd84450d094f23e3e
c5f0056922bde61f17500081c40e73bd86df9a2ec7688a11853a071aa3b4c6d8
fc22d78ded14ee48202581812a7b085f8bd5d868f37276f2af663e6cddcbaa51
99416fd083337b2b54a9bdc285741e2e28362229a04d8a2707d3cc3ad1ffb50c

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 whatsapp-core-auth-drzak (version 99.9.9). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging whatsapp-core-auth-drzak across your stack and pipelines.

  2. If you installed it — respond

    Remove whatsapp-core-auth-drzak 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 whatsapp-core-auth-drzak 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 whatsapp-core-auth-drzak 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. whatsapp-core-auth-drzak on npm has been identified as a malicious package (version 99.9.9 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-h5f2-r2ph-vpwgRLMA-2026-01831RLUA-2026-02059

References

Credits

  • Amazon Inspector · finder
  • ReversingLabs · finder

Detect & block this

O3 blocks whatsapp-core-auth-drzak-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.

whatsapp-core-auth-drzak (npm) malicious package — MAL-2026-1404 | O3 Security