@equansservices/setup
This report shows the evidence for @equansservices/setup@1.0.3. 2 of 4 known versions are blocked or flagged. The newest version, 1.0.2, is flagged. See all versions.
OpenSSF/OSV Malicious Advisory
imported 4mo ago · by OpenSSF/OSVOpenSSF/OSV advisory MAL-2026-10094 confirms this npm version as malicious.
Advisory
MAL-2026-10094
Source
OpenSSF Malicious Packages via OSV
Summary
Malicious code in @equansservices/setup (npm)
Details
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.
Source & flagged code
0 flagged · loading sourceNo flagged code excerpts are attached to this scan.
Findings
1 High
HighOsv Malicious Advisory
Affected versions and remediation
This report applies to @equansservices/setup@1.0.3.
The same advisory and Firewall decision cover 2 recorded versions
1.0.1, 1.0.3
The versions list below shows the verdict for each recorded version.
- Avoid installing @equansservices/setup@1.0.3. Remove it from direct dependencies and check your lockfile for transitive copies.
- Choose an independently verified alternative or release. This report does not establish that other versions are safe.
- If this version ran, investigate the affected machine and build environment. Rotate credentials it could access and rebuild from a trusted environment.
Evidence last updated: .
Source advisory published: .
This report uses published external intelligence. The advisory does not provide a separate source-code analysis for each listed version.
Think this verdict is wrong? Dispute it on GitHub or read how reports are produced.