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

tradepmr-api-utils-drzaknpm

Malicious code in tradepmr-api-utils-drzak (npm) Remove it immediately and rotate any exposed credentials.

MAL-2026-1402
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
npm uninstall tradepmr-api-utils-drzak

What this malware does

The package tradepmr-api-utils-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)

33e5b06fa98b6b58cc23217744c863c0c7cde6ab5c1a071ae47fd11a9466e586
ed879324b5de23922f365eaef686660dd2a42745f101998d954eda9c03449b1b
96daba07d298af7ca06c3026287d0b4fbe8bca5083d7c431aeeba35aec8e447b
b5cb9e5d2e34624b6824d49ac4334e06495af94677eb50c02539efba63c20539

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 tradepmr-api-utils-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 tradepmr-api-utils-drzak across your stack and pipelines.

  2. If you installed it — respond

    Remove tradepmr-api-utils-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 tradepmr-api-utils-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 tradepmr-api-utils-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. tradepmr-api-utils-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-c69r-v442-p36qRLMA-2026-01825RLUA-2026-02051

References

Credits

  • Amazon Inspector · finder
  • ReversingLabs · finder

Detect & block this

O3 blocks tradepmr-api-utils-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.

Malware detection Runtime egress monitoring
tradepmr-api-utils-drzak (npm) malicious package — MAL-2026-1402 | O3 Security