NIST deprecates RSA-2048 from 2030. Find every one of them before attackers do.
Malicious package

@ozon-complt/antibot-handlernpm

Advisory published Updated

@ozon-complt/antibot-handler is a confirmed malicious npm package (MAL-2026-3066) that executes malicious code on install (malicious versions 99.0.2, 99.0.4). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in @ozon-complt/antibot-handler (npm)

MAL-2026-3066
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
npm uninstall @ozon-complt/antibot-handler

What this malware does

The package @ozon-complt/antibot-handler 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.

The OpenSSF Package Analysis project identified '@ozon-complt/antibot-handler' @ 99.0.2 (npm) as malicious.

It is considered malicious because:

  • The package executes one or more commands associated with malicious behavior.

Malicious versions

2 flagged
99.0.299.0.4

Indicators of compromise (SHA-256)

635144e1855e8043e5a490b0773e140407788d3d1a9b80275932ad8ad1a2ba0e
c9b0712f953c0d5d9bd81d0bcd39f9bf956b002f3a8d4c549acfc757746cbb0e
3d2b2c8d66cf69cda5e16765e70a8c3615ecfc57baa6a283228bab60dcc337dc
6d3db9690eca86f4d58bbf72bc19c3dda0682ff833daf0cfe3e8c74795289f97

Detection & response playbook

Malicious package
  1. Find it

    Search your lockfiles and build artifacts for @ozon-complt/antibot-handler (2 malicious versions).

  2. If you installed it — respond

    Remove @ozon-complt/antibot-handler 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 @ozon-complt/antibot-handler was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

Frequently asked questions

No. @ozon-complt/antibot-handler on npm has been identified as a malicious package (versions 99.0.2, 99.0.4 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-m2jf-j5v5-wwx9

References

Credits

  • Amazon Inspector · finder
  • OpenSSF: Package Analysis · finder

Detect & block this

O3 blocks @ozon-complt/antibot-handler-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

@ozon-complt/antibot-handler (npm) malicious package — MAL-2026-3066 | O3 Security