Which versions of axois-utils are malicious?

The following npm versions of axois-utils are flagged malicious: 1.0.4, 1.0.5, 1.0.6, 1.0.7, 1.0.8, 1.0.9. Treat any of these as compromised.

How do I remediate axois-utils if I installed it?

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

If axois-utils 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 do I find axois-utils 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 axois-utils (6 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging axois-utils across your stack and pipelines.

Malicious package

axois-utilsnpm

Malicious code in axois-utils (npm) Remove it immediately and rotate any exposed credentials.

MAL-2026-4494

Immediate action

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

npm uninstall axois-utils

What this malware does

The package name is a single-character transposition of axios. package.json declares preinstall, install, and postinstall hooks all pointing at postinstall.js, guaranteeing execution on npm install. postinstall.js reads ~/.ssh/id_*, ~/.aws/credentials, ~/.aws/config, ~/.config/gcloud/application_default_credentials.json, ~/.azure/accessTokens.json, ~/.npmrc, shell histories, browser profile data, crypto wallet files, the entire process.env, and recursively walks ~/projects, ~/dev, ~/code, ~/workspace, and the current working directory for .env files. Collected data is POSTed via plain HTTP to http://80.200.28.28:2222/collect (hardcoded as C2_HOST at line 11). Author comments in the source explicitly label installers as 'victims' (// Change this to your PUBLIC IP when deploying to victims) and construct a VICTIM_ID, leaving no benign interpretation. The exposed fetchData API in index.js is a stub that only console.logs — the package has no legitimate function.

Malicious versions

6 flagged

1.0.41.0.51.0.61.0.71.0.81.0.9

Indicators of compromise (SHA-256)

2c958ad366d3cf211d3687734b5515662d21eb63135675984966149e7205f5ee

348b9dab1b41fbf96d8b2eb2d57a630c5173a7a59b446495ae44f2c8c270fc54

3bde7de4bfb2aa11618fdd40c2fa9148ea6528d5e0e198bf2a7148d013021d6b

48eb1a16cb7cac016f30a49f81d472b9b4e02236b97c5daaea4446b74e6aa069

6c7f0094b893662a5bccb61ccbb5acdc9cef0e7d29361133c47456ace1d46836

96352f83bd4eb19f3b558b436dbcb497759f2f44c09ba6e9f0c283a2bdf4b61a

a0138ed11110dbbde8b54451da2c6a188d1ce1b885f57b4502b0e3d15af797cc

ebd0e0c4d55ecc3d8d7d292bfbf40484d853466a4b12cbd7a4da5171cac12e74

ef6753fc762c223001f634d4abd6f0fd9e578ec3b042931a2b4ea0cdaab1ef26

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 axois-utils (6 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging axois-utils across your stack and pipelines.
If you installed it — respond
axois-utils 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 axois-utils 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 axois-utils 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. axois-utils on npm has been identified as a malicious package (versions 1.0.4, 1.0.5, 1.0.6, 1.0.7, 1.0.8, 1.0.9 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-003365IN-MAL-2026-003366IN-MAL-2026-003383IN-MAL-2026-003384IN-MAL-2026-003373IN-MAL-2026-003370IN-MAL-2026-003382IN-MAL-2026-003369IN-MAL-2026-003379

References

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks axois-utils-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