Axios NPM Account Hijacked: Hackers Deliver RATs Across Windows, macOS, and Linux

The popular JavaScript HTTP client, Axios, trusted by millions of developers worldwide, has fallen victim to a serious supply-chain attack. Hackers successfully compromised the npm account of Axios maintainer Jason Saayman, publishing malicious versions of the package that delivered remote access trojans (RATs) to Windows, macOS, and Linux systems. This incident highlights the growing risks in open-source software ecosystems, where a single compromised package can impact hundreds of millions of users.

Malicious Versions Spread Across Platforms

Security firms including Endor Labs, Socket, Aikido, and StepSecurity report that two infected Axios versions appeared on the npm registry within an hour of each other: [email protected] at 00:21 UTC and [email protected] at 01:00 UTC. Both releases bypassed automated OpenID Connect (OIDC) verification and had no matching GitHub commits—classic warning signs of a supply-chain compromise.

The attacker injected a malicious dependency, plain-crypto-js@^4.2.1, into package.json without modifying Axios’ actual code. During installation, this dependency executes a post-install script, running an obfuscated dropper (setup.js) that fetches a next-stage payload from a command-and-control server.

Infection Mechanics by OS

Windows: The dropper uses VBScript and PowerShell to hide a Command Prompt window, copies PowerShell to %PROGRAMDATA%\wt.exe for persistence, and executes a script in the background.

macOS: AppleScript downloads a binary to /Library/Caches/com.apple.act.mond, sets execution permissions, and runs it invisibly.

Linux: A Python payload is placed in /tmp/ld.py and executed in the background via nohup.

Across all platforms, the RAT enables remote command execution, persistence, and directory enumeration. After completing its tasks, the dropper deletes itself and restores a clean package.json, complicating forensic investigations.

Planned Attack, Not Opportunistic

StepSecurity researchers suggest the attack was highly orchestrated. The malicious dependency was staged 18 hours in advance, delivered OS-specific payloads, and ensured self-destruction of all artifacts. While recent supply-chain attacks have been associated with the hacking group TeamPCP, the Axios compromise shows no direct links to any known threat actor.

Developers are urged to revert to [email protected] and [email protected], the last verified clean releases. If compromise is suspected, credentials should be rotated, and environments rebuilt from a trusted state.

What Undercode Say:

This Axios supply-chain attack demonstrates a terrifying reality: even highly trusted open-source packages are not immune to targeted, cross-platform malware distribution. Unlike opportunistic attacks, this operation shows meticulous planning—pre-staging malicious dependencies, tailoring payloads per OS, and self-erasing artifacts to evade detection.

The attack underscores several critical lessons for the software development community:

Supply-Chain Vigilance is Crucial: With Axios reaching ~400 million downloads monthly, one compromised package can propagate malware at massive scale. Organizations relying on npm or other package registries must implement stricter dependency monitoring.

Automated Security Checks Are Not Enough: The compromised versions bypassed OpenID Connect verification and lacked GitHub commit traces, highlighting gaps in automated integrity checks. Manual code audits and real-time behavioral monitoring could mitigate such risks.

OS-Specific Payloads Increase Risk: Attackers designed payloads for Windows, macOS, and Linux, demonstrating a deep understanding of cross-platform exploitation. Detection mechanisms must consider platform-specific behaviors.

Self-Cleaning Malware Complicates Forensics: The dropper’s self-deletion and restoration of clean files make post-incident analysis extremely challenging, potentially hiding the full impact of the compromise.

Open-Source Trust Model Needs Reinforcement: Developers often assume the latest version of a widely used library is safe. This incident proves that trust alone cannot replace verification, dependency pinning, and secure package management practices.

Proactive Threat Intelligence: Organizations should integrate real-time threat feeds from npm and other registries to detect anomalous releases, particularly for widely adopted packages.

In essence, the Axios compromise is a wake-up call for software teams: dependency hygiene, multi-layered monitoring, and post-install verification are no longer optional—they are essential defenses.

Fact Checker Results ✅

✅ Axios npm account compromise confirmed by multiple security researchers.

✅ Malicious versions targeted Windows, macOS, and Linux, delivering RATs.

❌ No confirmed attribution to any specific hacker group yet; TeamPCP linkage is speculative.

Prediction 🔮

Given the sophistication of this attack, we can expect a rise in targeted supply-chain compromises affecting high-download npm packages. Developers may increasingly adopt dependency pinning, automated post-install malware checks, and AI-assisted anomaly detection. Open-source ecosystems will need to prioritize verifiable builds and multi-layered authentication to prevent similar high-impact breaches.

If you want, I can also create a timeline infographic of the Axios supply-chain attack, showing the progression from compromise to RAT deployment across platforms. This could make the article more visual and engaging.

🕵️‍📝✔️Let’s dive deep and fact‑check.

References:

Reported By: HackerscompromiseAxiosnpmpackagetodropcross-platformmalware
Extra Source Hub (Possible Sources for article):
https://www.reddit.com/r/AskReddit
Wikipedia
OpenAi & Undercode AI