Which versions of okx-data are malicious?

The following npm versions of okx-data are flagged malicious: 9999.1.0. Treat any of these as compromised.

How do I remediate okx-data if I installed it?

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

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

Yes — okx-data is associated with the GHSA-whfj-85gw-8h4c, RLMA-2026-02008 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 okx-data 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 okx-data (version 9999.1.0). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging okx-data across your stack and pipelines.

Malicious package

okx-datanpm

Malicious code in okx-data (npm) Remove it immediately and rotate any exposed credentials.

MAL-2026-2647

Immediate action

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

npm uninstall okx-data

What this malware does

The package okx-data 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

9999.1.0

Indicators of compromise (SHA-256)

41edc2d01a36c24d285496e1d882419e277f6ac2ded1e21f9d6eb4fd13cada75

209ffb66607af77e18ffde023d2202862ba1cd6e382314b7f3c7b149fe2cf312

7f537a0896e3975393a32700cc7c402b5b84baade9d30694090e625ef37a8a09

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

Campaign

GHSA-whfj-85gw-8h4cRLMA-2026-02008

References

github.com

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

O3 blocks okx-data-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