Which versions of exodus-ethereum-sdk are malicious?

The following npm versions of exodus-ethereum-sdk are flagged malicious: 99.0.0-canary.1. Treat any of these as compromised.

How do I remediate exodus-ethereum-sdk if I installed it?

exodus-ethereum-sdk is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.

I already installed exodus-ethereum-sdk — how do I know if it already compromised me?

If exodus-ethereum-sdk 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 exodus-ethereum-sdk part of a known attack campaign?

Yes — exodus-ethereum-sdk is associated with the IN-MAL-2026-005108, IN-MAL-2026-005107 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 exodus-ethereum-sdk 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 exodus-ethereum-sdk (version 99.0.0-canary.1). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging exodus-ethereum-sdk across your stack and pipelines.

Malicious package

exodus-ethereum-sdknpm

Malicious code in exodus-ethereum-sdk (npm) Remove it immediately and rotate any exposed credentials.

MAL-2026-5440

Immediate action

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

npm uninstall exodus-ethereum-sdk

What this malware does

Package name impersonates the Exodus cryptocurrency wallet brand and ships no real functionality (src/index.js exports an empty object; package.json self-describes as a 'HackerOne PoC'). The package.json declares a postinstall hook (node src/canary.js) which fires automatically on npm install. src/canary.js performs a DNS lookup and HTTPS GET to a hardcoded 96e03fa6c292469a-172-245-86-254.serveousercontent.com subdomain — Serveo is an anonymous reverse-tunnel service, so the destination is operator-controlled and not tied to any identifiable publisher. Each install reveals the installer's public IP and DNS resolver to whoever currently controls that tunnel. Combined with the brand-impersonating name (installers may pull this expecting a legitimate Exodus SDK), the package functions as an install-time beacon against unsuspecting installers regardless of the author's stated 'research' intent.

Malicious versions

1 flagged

99.0.0-canary.1

Indicators of compromise (SHA-256)

25c8b4456182ead7b8240cb61979ed48aaea35af26ec1dc2f259d35e7da87673

b4e52a42f8980da0a9df361ef772ca31bbdaec85eb3fc7a73dbcfc8b5ca6894a

Detection & response playbook

Credential / info stealer

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for exodus-ethereum-sdk (version 99.0.0-canary.1). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging exodus-ethereum-sdk across your stack and pipelines.
If you installed it — respond
exodus-ethereum-sdk is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.
Did it already run?
If exodus-ethereum-sdk 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 exodus-ethereum-sdk 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. exodus-ethereum-sdk on npm has been identified as a malicious package (version 99.0.0-canary.1 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-005108IN-MAL-2026-005107

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks exodus-ethereum-sdk-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.

Malware detection Runtime egress monitoring