Which versions of axious-core are malicious?

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

How do I remediate axious-core if I installed it?

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

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

Yes — axious-core is associated with the IN-MAL-2026-018230 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 axious-core 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 axious-core (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 axious-core across your stack and pipelines.

Malicious package

axious-corenpm

axious-core is a confirmed malicious npm package (MAL-2026-14162) 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 axious-core (npm)

MAL-2026-14162

Immediate action

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

npm uninstall axious-core

What this malware does

axious-core has an empty index.js and no declared functionality, but its scripts/postinstall.js runs a full install-time dropper. Four opaque byte arrays are XOR-decoded at runtime with the key 'stf2026' to reconstruct a download URL and shell command. The decoded URL points to github.com/bebraz1/... which is fetched to %TEMP%\main.exe and spawned detached with stdio ignored and windowsHide. When executed on WSL/Linux (detected by reading /proc/version and WSL environment variables), a second XOR-decoded bridge command is used to launch the downloaded Windows binary from inside the Linux environment via PowerShell/WSL interop. In parallel, sendInstallMetrics POSTs a JSON payload containing the host platform to a bare IPv4 destination assembled from an array literal ('193','70','34','101').join('.') at 193.70.34.101:20099/vote — an install-success beacon to attacker-controlled infrastructure, with the IP hidden via array join to evade static scanners. The combination of an empty library facade, XOR-obfuscated URLs and shell commands, an unverified remote binary drop-and-execute on install, a WSL escape path, and a bare-IP C2 beacon is a supply-chain dropper.

Malicious versions

1 flagged

1.0.0

Indicators of compromise (SHA-256)

da16d1b32b464ea73dcd68b2fbf9f3b80519453c19402d29de3bc86d79bc5d25

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 axious-core (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 axious-core across your stack and pipelines.
If you installed it — respond
axious-core 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 axious-core 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 axious-core 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. axious-core 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-018230

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks axious-core-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