Which versions of exodus-payments are malicious?

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

How do I remediate exodus-payments if I installed it?

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

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

Yes — exodus-payments is associated with the RLMA-2026-05535, IN-MAL-2026-012910, RLUA-2026-06229 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-payments 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-payments (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-payments across your stack and pipelines.

Malicious package

exodus-paymentsnpm

exodus-payments is a confirmed malicious npm package (MAL-2026-10895) that steals credentials and exfiltrates sensitive data (malicious version 99.0.0-canary.1). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in exodus-payments (npm)

MAL-2026-10895

Immediate action

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

npm uninstall exodus-payments

What this malware does

Package is self-identified as a dependency-confusion proof-of-concept. Its postinstall hook (src/canary.js) performs a DNS lookup and HTTPS GET to a hardcoded Serveo tunnel host (96e03fa6c292469a-172-245-86-254.serveousercontent.com), sending only the package's own name and version as query parameters. No environment variables, credentials, filesystem contents, or other installer data are read or transmitted; the only signal the operator gains is the installer's public egress IP from the inbound request metadata. README discloses the canary purpose. Concerns: install-time outbound network without opt-out (breaks air-gapped/sandboxed CI), destination is a third-party mutable tunneling endpoint rather than publisher-owned infrastructure, and the canary version coordinate (99.0.0-canary.1) is shaped to win dependency-confusion races against private packages. No credential theft, no code execution of remote content, no persistence.

Malicious versions

1 flagged

99.0.0-canary.1

Indicators of compromise (SHA-256)

328b16bdcd1792de22d87fbbe353e2fc58968a0c1f64f46eddd29da089df2495

51394e5297d9dc765ee318eabd49e400b9f843c342ed91e3df9bd9befc84254e

16663a5c8890c81d50b74bc27316c674904d9a157afe9ba82e1c579024624d06

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-payments (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-payments across your stack and pipelines.
If you installed it — respond
exodus-payments 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-payments 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-payments 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-payments 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

RLMA-2026-05535IN-MAL-2026-012910RLUA-2026-06229

References

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

O3 blocks exodus-payments-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

Explore

All malware advisories How O3 detects malware Vulnerability database