@ohos-ports/codexnpm
@ohos-ports/codex is a confirmed malicious npm package (MAL-2026-13210) that executes malicious code on install (malicious version 0.140.0-beta.0). Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in @ohos-ports/codex (npm)
What this malware does
The package's package.json declares its dependency "@openai/codex" as a direct tarball URL: https://gitcode.com/api/v5/repos/OpenHarmonyPCDeveloper/JavaScript_Package_For_HarmonyOS/raw/packages/openai-codex-0.140.0.tgz?ref=main. The reference is mutable (branch 'main', no commit SHA, no integrity hash) and is hosted by a third-party org (OpenHarmonyPCDeveloper on gitcode.com) that is not the @openai publisher. On npm install, this tarball is fetched and placed into the installer's node_modules under the well-known @openai/codex name, so any code that resolves '@openai/codex' — including this package's own bin wrapper (await import('@openai/codex/bin/codex.js')) — loads content controlled by that third-party org rather than OpenAI. Because resolution happens through the dependencies field rather than a lifecycle script, npm install --ignore-scripts does not mitigate. The mutable branch reference means the content served at that URL can change at any time without a package republish.
Malicious versions
Indicators of compromise (SHA-256)
Detection & response playbook
Malicious packageFind it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for @ohos-ports/codex (version 0.140.0-beta.0). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging @ohos-ports/codex across your stack and pipelines.
If you installed it — respond
Remove @ohos-ports/codex 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 @ohos-ports/codex 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 @ohos-ports/codex 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
Campaign
References
Credits
- Amazon Inspector · finder
Detect & block this
O3 blocks @ohos-ports/codex-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.