Which versions of @equansservices/codex are malicious?

The following npm versions of @equansservices/codex are flagged malicious: 1.0.1. Treat any of these as compromised.

How do I remediate @equansservices/codex if I installed it?

@equansservices/codex is a typosquat — you almost certainly intended a legitimately-named package. Remove @equansservices/codex, install the correct package, and rotate any secrets exposed during the install since post-install scripts may have already run.

I already installed @equansservices/codex — how do I know if it already compromised me?

If @equansservices/codex was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

Is @equansservices/codex part of a known attack campaign?

Yes — @equansservices/codex is associated with the IN-MAL-2026-009797 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 @equansservices/codex across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for @equansservices/codex (version 1.0.1).

Malicious package

@equansservices/codexnpm

Advisory published Jul 13, 2026Updated Jul 13, 2026

@equansservices/codex is a confirmed malicious npm package (MAL-2026-10399) that typosquats a legitimate package to trick installs (malicious version 1.0.1). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in @equansservices/codex (npm)

MAL-2026-10399

Immediate action

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

npm uninstall @equansservices/codex

What this malware does

@equansservices/codex is a typosquat of @openai/codex (it also declares @openai/codex as a dependency to appear legitimate). Its package.json declares a postinstall hook (node setup.js) that, at npm install time, downloads a platform-specific payload from http://d2vf4rs175cy2k.cloudfront.net/install/v1/ (plugin.zip on Windows, marketplace on Linux) over plain HTTP with no pinning and no hash/signature verification, extracts it to a temp directory, and spawns it detached (aws.exe on Windows, python3 upgrade.py on Linux). Installer machines execute attacker-controlled bytes as a side effect of installation.

Malicious versions

1 flagged

1.0.1

Indicators of compromise (SHA-256)

c5e64d3c1e1d799f465001f52813a12ba2cf757ce9ea50c27d184b7549000dc9

Detection & response playbook

Typosquat

Find it
Search your lockfiles and build artifacts for @equansservices/codex (version 1.0.1).
If you installed it — respond
@equansservices/codex is a typosquat — you almost certainly intended a legitimately-named package. Remove @equansservices/codex, install the correct package, and rotate any secrets exposed during the install since post-install scripts may have already run.
Did it already run?
If @equansservices/codex was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

Frequently asked questions

No. @equansservices/codex on npm has been identified as a malicious package (version 1.0.1 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-009797

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks @equansservices/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.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database