Malicious code in axious-core (npm)
Historical advisory saved 24 Oct 2026 13:17:17 UTC. The publisher may have updated it since then. Latest advisory.
osv · MAL-2026-14162
Published--- _-= Per source details. Do not edit below this line.=-_ ## Source: amazon-inspector (da16d1b32b464ea73dcd68b2fbf9f3b80519453c19402d29de3bc86d79bc5d25) 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.
- Source published
- 18 Aug 2026 23:56:13 UTC
- Source modified
- 19 Aug 2026 00:30:11 UTC
- Saved here
- 24 Oct 2026 13:17:17 UTC
- Source terms
- OSV · upstream source license applies
Original source record · Cite this exact observation · Complete original publisher JSON
Source: osv · OSV · upstream source license applies. The publisher's wording is preserved. ChangeIntel groups the information and labels changes. The JSON record includes additional source fields.