Which versions of exodus-secure-container are malicious?

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

How do I remediate exodus-secure-container if I installed it?

exodus-secure-container establishes remote access, so treat any host that installed it as fully compromised. Isolate the machine, remove the package, rotate all credentials it could reach, and rebuild from a trusted image rather than cleaning in place — a backdoor may have planted additional persistence.

I already installed exodus-secure-container — how do I know if it already compromised me?

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

Yes — exodus-secure-container is associated with the IN-MAL-2026-005106, IN-MAL-2026-005105 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-secure-container 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-secure-container (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-secure-container across your stack and pipelines.

Malicious package

exodus-secure-containernpm

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

MAL-2026-5441

Immediate action

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

npm uninstall exodus-secure-container

What this malware does

On npm install, the package runs node src/canary.js as a postinstall hook. That script performs a DNS lookup and HTTPS GET to the hardcoded host 96e03fa6c292469a-172-245-86-254.serveousercontent.com/c — an anonymous serveo.net reverse-tunnel endpoint, not a publisher CDN. The beacon fires unconditionally on every install, signalling the installer's public IP and DNS-resolver identity to a third-party host. The package itself has no functionality: src/index.js is module.exports = {}, and the version 99.0.0-canary.1 is engineered to win semver resolution against an internal package of the same name (dependency-confusion canary shape). Whether the operator is a researcher or a hostile actor, any environment that resolves this name against the public registry leaks install-time identity to an attacker-controllable tunnel.

Malicious versions

1 flagged

99.0.0-canary.1

Indicators of compromise (SHA-256)

8ed2337fdd749accb1f4a5b190413ced8c1cd0f1b691ba3e79dd4bfe9a3f3ef8

92bc77b12251baa18392bd90e84d6bdc57aaef9a8c774f8cb29a0066e80f76b5

Detection & response playbook

Backdoor / remote access

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for exodus-secure-container (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-secure-container across your stack and pipelines.
If you installed it — respond
exodus-secure-container establishes remote access, so treat any host that installed it as fully compromised. Isolate the machine, remove the package, rotate all credentials it could reach, and rebuild from a trusted image rather than cleaning in place — a backdoor may have planted additional persistence.
Did it already run?
If exodus-secure-container 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-secure-container 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-secure-container 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-005106IN-MAL-2026-005105

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks exodus-secure-container-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the C2 callback and severs the channel.

Malware detection Runtime egress monitoring