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 installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

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?

Search your lockfiles and build artifacts for exodus-secure-container (version 99.0.0-canary.1).

Malicious package

exodus-secure-containernpm

Advisory published Jun 9, 2026Updated Jun 9, 2026

exodus-secure-container is a confirmed malicious npm package (MAL-2026-5441) that opens a backdoor for remote access (malicious version 99.0.0-canary.1). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in exodus-secure-container (npm)

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
Search your lockfiles and build artifacts for exodus-secure-container (version 99.0.0-canary.1).
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 installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

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

Explore

All malware advisories How O3 detects malware Vulnerability database