# MAL-2026-10400: Malicious code in @equansservices/tool (npm)


- **Type:** Malicious package
- **Package:** `@equansservices/tool` (npm)
- **Published:** 13 Jul 2026
- **Also known as:** GHSA-5v77-3vqq-cv88

## What is MAL-2026-10400?

MAL-2026-10400 is a malicious package in @equansservices/tool, published on 13 Jul 2026. 

### Official description

The package's postinstall hook (`node setup.js`) fetches a platform-specific payload from `http://d2vf4rs175cy2k.cloudfront.net/install/v1/plugin.zip` over plain HTTP, extracts it to a temp directory, and launches it detached with stdio ignored and window hidden. On Windows the extracted `aws.exe` is executed; on Linux `python3 upgrade.py` is run. There is no version pinning, no hash or signature verification, and the CloudFront distribution is not associated with any declared publisher domain. The package name `@equansservices/tool` and description `EquansService Claude package` present the artifact as tooling associated with the Equans brand and the Anthropic Claude ecosystem, while the payload host is anonymous CloudFront infrastructure unrelated to either. Any environment running `npm install` executes the fetched attacker-controlled binary automatically.

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.

## What should I do about MAL-2026-10400?

Remove the package from your dependencies and lockfiles, then rotate any secrets on machines where it was installed.

## Fix prompt for AI coding agents

```text
MAL-2026-10400 is a malicious package: @equansservices/tool (npm). Every version was published to cause harm.

Task:
1. Search this repository's dependency manifests and lockfiles for the package, including transitive dependencies.
2. If it is present, remove it, regenerate the lockfile with the project's package manager, and replace whatever it was used for.
3. List any CI runners, developer machines or containers that installed it, so their secrets can be rotated.
4. If the package is not used anywhere, say so and change nothing.

Reference: https://insights.sbomify.com/MAL-2026-10400/ (Markdown: https://insights.sbomify.com/MAL-2026-10400/index.md)
```

## Sources

- OSV: https://osv.dev/vulnerability/MAL-2026-10400

---
From sbomify Insights: https://insights.sbomify.com/MAL-2026-10400/
Summaries are generated and may contain mistakes; the official description above is the record.