Which versions of exiouss are malicious?

The following npm versions of exiouss are flagged malicious: 5.0.1. Treat any of these as compromised.

How do I remediate exiouss if I installed it?

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

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

Yes — exiouss is associated with the IN-MAL-2026-020811 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 exiouss across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for exiouss (version 5.0.1).

Malicious package

exioussnpm

Advisory published Sep 30, 2026Updated Sep 30, 2026

exiouss is a confirmed malicious npm package (MAL-2026-17327) that steals credentials and exfiltrates sensitive data (malicious version 5.0.1). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in exiouss (npm)

MAL-2026-17327

Immediate action

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

npm uninstall exiouss

What this malware does

main.js in [email protected] imports child_process and issues POST requests to hardcoded endpoints, including https://gemini.google.com and https://ipc.shadxino.internal (main.js around lines 368-386). The presence of an ipc.shadxino.internal destination alongside a public Google host, combined with child_process usage and repeated ping invocations across the file (lines 202, 340, 420, 583, 611), fits an active-exfiltration/reconnaissance shape rather than any documented HTTP-client behavior. The .internal host is not a resolvable public destination and its appearance in a published npm module is consistent with an attacker-side collector or a leaked internal C2 name.

Malicious versions

1 flagged

5.0.1

Indicators of compromise (SHA-256)

43ce408818d0222061c3b6ed499d77a245aae78e30e4f57c8e6e77ee52705805

Detection & response playbook

Credential / info stealer

Find it
Search your lockfiles and build artifacts for exiouss (version 5.0.1).
If you installed it — respond
exiouss 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 exiouss 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. exiouss on npm has been identified as a malicious package (version 5.0.1 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-020811

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks exiouss-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