MAL-2026-5439 Malicious code in exodus-checkout-signer (npm)
Malicious package
Published
MAL-2026-5439 is a malicious package: exodus-checkout-signer (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-5439/ (Markdown: https://insights.sbomify.com/MAL-2026-5439/index.md)
- Package
- exodus-checkout-signer
- Registry
- npm
What is MAL-2026-5439?
MAL-2026-5439 is a malicious package in exodus-checkout-signer, published on 9 Jun 2026.
Official description
exodus-checkout-signer is the unscoped name of the scoped package @exodus/checkout-signer and self-describes (in README and package.json) as a dependency-confusion proof-of-concept targeting installers who follow Exodus's documented install command and drop the scope. The package's main entry throws on require so any caller fails loudly, but on
npm install the postinstall script unconditionally runs node src/canary.js, which performs a DNS lookup and an HTTPS GET to 96e03fa6c292469a-172-245-86-254.serveousercontent.com — a Serveo SSH-tunneling endpoint with a raw IP (172.245.86.254) embedded in the subdomain — passing the package name and version as query parameters (/canary-install?pkg=...&ver=...). No installer secrets are exfiltrated, but every installation reveals the victim's source IP, timing, and corporate-network egress to an anonymous third-party tunnel operator that is not affiliated with the impersonated Exodus publisher. The combined name-confusion against a top-shelf wallet vendor's documented scope plus install-time beaconing to attacker-controllable infrastructure is a live supply-chain attack regardless of the author's stated 'research' intent.What should I do about MAL-2026-5439?
Remove the package from your dependencies and lockfiles, then rotate any secrets on machines where it was installed.