Which versions of nodeaxois are malicious?

The following npm versions of nodeaxois are flagged malicious: 1.0.0. Treat any of these as compromised.

How do I remediate nodeaxois if I installed it?

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

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

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

Search your lockfiles and build artifacts for nodeaxois (version 1.0.0).

Malicious package

nodeaxoisnpm

Advisory published Jul 14, 2026Updated Jul 14, 2026

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

Malicious code in nodeaxois (npm)

MAL-2026-10589

Immediate action

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

npm uninstall nodeaxois

What this malware does

The package declares scripts.postinstall: node.init.js, which runs automatically on npm install. The.init.js script collects host metadata (os.hostname(), os.platform(), process.cwd(), process.pid, timestamp), enumerates approximately 60 credential-shaped environment variables (NPM_TOKEN, GITHUB_TOKEN, AWS_SECRET_ACCESS_KEY, STRIPE_, DOCKER_, CLOUDFLARE_, GCP, etc.), reads ~/.npmrc, ~/.env, ~/config.json, ~/credentials.json, and files under ~/.config/ whose names contain token/cred/secret, and POSTs the aggregated JSON to a hardcoded https://webhook.cool/at/tender-deer-80/ endpoint. The package's index.js exports an empty object; the tarball provides no legitimate functionality. The name is a likely typosquat of axios.

Malicious versions

1 flagged

1.0.0

Indicators of compromise (SHA-256)

ebf1f3f7342689c11ad7e8c17a1c584fe3ce15615db82868b289d9613b48a41a

Detection & response playbook

Credential / info stealer

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

Campaign

IN-MAL-2026-010522

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

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