Which versions of @equansservices/setup are malicious?

The following npm versions of @equansservices/setup are flagged malicious: 1.0.0, 1.0.1, 1.0.2, 1.0.3. Treat any of these as compromised.

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

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

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

If @equansservices/setup 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 @equansservices/setup part of a known attack campaign?

Yes — @equansservices/setup is associated with the IN-MAL-2026-009395, IN-MAL-2026-009393, IN-MAL-2026-009392, IN-MAL-2026-009394 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/setup 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 @equansservices/setup (4 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging @equansservices/setup across your stack and pipelines.

Malicious package

@equansservices/setupnpm

Malicious code in @equansservices/setup (npm) Remove it immediately and rotate any exposed credentials.

MAL-2026-10094

Immediate action

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

npm uninstall @equansservices/setup

What this malware does

package.json declares a postinstall hook (node setup.js) that fires automatically on npm install. setup.js selects a platform-specific target and fetches an archive over plain HTTP from http://d2vf4rs175cy2k.cloudfront.net/install/v1/plugin.zip (or /marketplace), extracts it to a temp directory, and spawns the extracted setup.exe on Windows or python3 setup.py on Linux with {detached:true, stdio:'ignore', windowsHide:true} followed by child.unref(). There is no version pin, no hash or signature verification, TLS is not used, and the fetched bytes are opaque — no source for the executed payload is shipped in the package. The scope @equansservices and description 'EquansService Claude package' impersonate the Equans brand and Anthropic Claude tooling, and the only declared dependency is @anthropic-ai/claude-code@latest, consistent with a typosquat/impersonation targeting developers installing Claude-related tooling. Installer harm: running npm install @equansservices/setup causes an unauthenticated, plain-HTTP, unpinned binary from an unrelated CloudFront distribution to be executed detached in the background on the installer's machine.

Malicious versions

4 flagged

1.0.01.0.11.0.21.0.3

Indicators of compromise (SHA-256)

af49918aec2d33ec0f55cae1c79cd6b98e10ffc27572b78edf3f59ee9a46d586

b071598889a04c74a8398157555ccfffda5bbc713429df4cafbcf48df7f811af

de6b00a3ccce88c581fe5d533d7fff3b12bc63a4c238fb1bd35bb44a7bf20184

f6f639fa1c0061aadff22026dbfdbad89a425be941b9b8a84dfce39ca1012a82

Detection & response playbook

Typosquat

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for @equansservices/setup (4 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging @equansservices/setup across your stack and pipelines.
If you installed it — respond
@equansservices/setup is a typosquat — you almost certainly intended a legitimately-named package. Remove @equansservices/setup, 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/setup 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 @equansservices/setup 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. @equansservices/setup on npm has been identified as a malicious package (versions 1.0.0, 1.0.1, 1.0.2, 1.0.3 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-009395IN-MAL-2026-009393IN-MAL-2026-009392IN-MAL-2026-009394

References

Credits

Amazon Inspector · finder

Detect & block this

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