Which versions of okx-nav are malicious?

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

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

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

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

Yes — okx-nav is associated with the GHSA-qgr4-v84c-p4g7, RLMA-2026-02009 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-nav 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-nav (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-nav across your stack and pipelines.

Malicious package

okx-navnpm

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

MAL-2026-2648

Immediate action

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

npm uninstall okx-nav

What this malware does

The package okx-nav 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)

3961b5dc52e388cd7ea999f85a4541bfc0e083e63afad50184fea746d70d275d

8cf60dc32c2bc06227d0ed8ad95d30782267203cf8e69d42cf4045f20552a406

6ab3eb270d52d290185b24d8da75ec720b1c6d2403eb5bfeee0127d98edff14f

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-nav (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-nav across your stack and pipelines.
If you installed it — respond
Remove okx-nav 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-nav 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-nav 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-nav 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-qgr4-v84c-p4g7RLMA-2026-02009

References

github.com

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

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