Which versions of axois-http are malicious?

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

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

axois-http is a typosquat — you almost certainly intended a legitimately-named package. Remove axois-http, install the correct package, and rotate any secrets exposed during the install since post-install scripts may have already run.

I already installed axois-http — how do I know if it already compromised me?

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

Yes — axois-http is associated with the IN-MAL-2026-018238 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 axois-http 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-http (version 1.0.0). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging axois-http across your stack and pipelines.

Malicious package

axois-httpnpm

axois-http is a confirmed malicious npm package (MAL-2026-14163) that typosquats a legitimate package to trick installs (malicious version 1.0.0). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in axois-http (npm)

MAL-2026-14163

Immediate action

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

npm uninstall axois-http

What this malware does

axois-http is a typosquat of axios (index.js exports an empty object). Its scripts/postinstall.js unconditionally POSTs a JSON body containing a detected-platform label (Windows/MacOS/Linux, with WSL detection via /proc/version and /proc/sys/kernel/osrelease) to a hardcoded bare-IP endpoint http://193.70.34.101:20099/vote at npm install time. On Windows or WSL, the script XOR-decodes a hidden URL (key 'stf2026', decoded prefix 'https://') and a XOR-decoded PowerShell launcher command, downloads a native binary to %TEMP%\main.exe via fetchAddonBinary, and spawns it detached with windowsHide:true and stdio:'ignore'. URL, PowerShell command, and surrounding bridge script fragments are stored as byte arrays and decoded at runtime via unpackSegment(data, 'stf2026') solely to hide the payload URL and shell command. The package has no legitimate need for a native binary and offers no first-party functionality.

Malicious versions

1 flagged

1.0.0

Indicators of compromise (SHA-256)

69703c3a809c078834e321ae3777e144413bcef3d17ea7a712d6108f9ca34885

Detection & response playbook

Typosquat

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for axois-http (version 1.0.0). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging axois-http across your stack and pipelines.
If you installed it — respond
axois-http is a typosquat — you almost certainly intended a legitimately-named package. Remove axois-http, install the correct package, and rotate any secrets exposed during the install since post-install scripts may have already run.
Did it already run?
If axois-http 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-http 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-http 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-018238

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks axois-http-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the malicious outbound activity and severs the channel.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database