Which versions of @ozon-complt/antibot-handler are malicious?

The following npm versions of @ozon-complt/antibot-handler are flagged malicious: 99.0.2, 99.0.4. Treat any of these as compromised.

How do I remediate @ozon-complt/antibot-handler if I installed it?

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.

I already installed @ozon-complt/antibot-handler — how do I know if it already compromised me?

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

Is @ozon-complt/antibot-handler part of a known attack campaign?

Yes — @ozon-complt/antibot-handler is associated with the GHSA-m2jf-j5v5-wwx9 campaign. Packages in the same campaign often share infrastructure and payloads, so check whether any related packages are also in your dependency tree.

How do I find @ozon-complt/antibot-handler across my projects, lockfiles, and CI pipelines?

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

Malicious package

@ozon-complt/antibot-handlernpm

Malicious code in @ozon-complt/antibot-handler (npm) Remove it immediately and rotate any exposed credentials.

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

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for @ozon-complt/antibot-handler (2 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging @ozon-complt/antibot-handler across your stack and pipelines.
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.
Did it already run?
If @ozon-complt/antibot-handler 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.
How O3 protects you
O3 blocks @ozon-complt/antibot-handler 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. @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

github.com

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.

Malware detection Runtime egress monitoring