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

ozonex-sdknpm

ozonex-sdk is a confirmed malicious npm package (MAL-2026-5651) that executes malicious code on install (malicious versions 1.0.2, 1.0.5, 1.0.6…). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in ozonex-sdk (npm)

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

What this malware does

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

5 flagged
1.0.21.0.51.0.61.0.71.0.8

Indicators of compromise (SHA-256)

b5e40322806de6c1fc8ca77941438b3481f3f12059a9c34d13645c2a4b8a82c8
c32a7e3c8bf70ac2f71bec6cd987e4218a9dd1ad9f535fb4eaf8dde07c1b5fdf
be579bae79e21636414f0bd81f06bf820eb013ebffa9297dd4c14d9ea1d6a16a

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 ozonex-sdk (5 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging ozonex-sdk across your stack and pipelines.

  2. If you installed it — respond

    Remove ozonex-sdk 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 ozonex-sdk 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 ozonex-sdk 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. ozonex-sdk on npm has been identified as a malicious package (versions 1.0.2, 1.0.5, 1.0.6, 1.0.7, 1.0.8 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-v2hc-cmv5-999pRLMA-2026-05200RLUA-2026-05588

References

Credits

  • ReversingLabs · finder

Detect & block this

O3 blocks ozonex-sdk-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

ozonex-sdk (npm) malicious package — MAL-2026-5651 | O3 Security