Which versions of exodus-wallet-core are malicious?

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

How do I remediate exodus-wallet-core if I installed it?

exodus-wallet-core 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-wallet-core — how do I know if it already compromised me?

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

Yes — exodus-wallet-core is associated with the IN-MAL-2026-005114, IN-MAL-2026-005113 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-wallet-core 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-wallet-core (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-wallet-core across your stack and pipelines.

Malicious package

exodus-wallet-corenpm

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

MAL-2026-5443

Immediate action

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

npm uninstall exodus-wallet-core

What this malware does

Package name impersonates the Exodus cryptocurrency wallet brand. package.json declares "postinstall": "node src/canary.js", and src/canary.js performs a DNS lookup and HTTPS GET to a hardcoded Serveo reverse-tunnel host (96e03fa6c292469a-172-245-86-254.serveousercontent.com/c) on every npm install. Serveo (serveousercontent.com) is a reverse-SSH tunneling service frequently used to expose non-publisher hosts; this is not Exodus infrastructure. The callout leaks the installer's IP address and timing to the tunnel operator and demonstrates arbitrary install-time code execution on the installer's machine. Although the package self-describes as a HackerOne PoC canary, the technique is a live supply-chain attack pattern operating against any machine that installs it.

Malicious versions

1 flagged

99.0.0-canary.1

Indicators of compromise (SHA-256)

1ba93766fbae4c48460e40e317bf64f68251047d20cf43e4583db8d6be616bc8

53bf93b626689e980ef2e9c4ba33fd95e81d6a04c665f85908c8cf07b8b36e14

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-wallet-core (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-wallet-core across your stack and pipelines.
If you installed it — respond
exodus-wallet-core 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-wallet-core 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-wallet-core 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-wallet-core 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-005114IN-MAL-2026-005113

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks exodus-wallet-core-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