Which versions of okxglobal are malicious?

The following npm versions of okxglobal are flagged malicious: 9999.0.1, 9999.1.0. Treat any of these as compromised.

How do I remediate okxglobal if I installed it?

Remove okxglobal 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 okxglobal — how do I know if it already compromised me?

If okxglobal 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 okxglobal part of a known attack campaign?

Yes — okxglobal is associated with the GHSA-633r-f3rq-76g4, RLMA-2026-02010, RLUA-2026-05190 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 okxglobal 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 okxglobal (2 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging okxglobal across your stack and pipelines.

Malicious package

okxglobalnpm

okxglobal is a confirmed malicious npm package (MAL-2026-2649) that executes malicious code on install (malicious versions 9999.0.1, 9999.1.0). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in okxglobal (npm)

MAL-2026-2649

Immediate action

Remove the package, then rotate any secrets the build/runtime could reach.

npm uninstall okxglobal

What this malware does

The package okxglobal 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

2 flagged

9999.0.19999.1.0

Indicators of compromise (SHA-256)

6fbd6d2866029238fe53fa341215f4c413767014dc0e6bf5688addd872f109df

e473abf783cdbbd7eb62f849866dfc8dc9aa42bf697e2a383949ea13666a648a

69c773213dce504325f6d7d1508b8b2c8f2586998ab8240577610d71643d496d

51f231f7e0c2c5b3142bf81a23fc521acd569edb07b8d3d652cd3d6a76a0d809

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 okxglobal (2 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging okxglobal across your stack and pipelines.
If you installed it — respond
Remove okxglobal 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 okxglobal 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 okxglobal 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. okxglobal on npm has been identified as a malicious package (versions 9999.0.1, 9999.1.0 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-633r-f3rq-76g4RLMA-2026-02010RLUA-2026-05190

References

github.com

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

O3 blocks okxglobal-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

Explore

All malware advisories How O3 detects malware Vulnerability database