Axios npm Supply Chain: SANS Initial Access Broker Theory, Sapphire Sleet vs TeamPCP, and the Lockfile Discipline That Saved Some Orgs

Analysis

SANS: Axios Attackers May Be Operating as an Initial Access Broker Selling Stolen Maintainer Credentials

SANS draws a direct line between the Axios attack and TeamPCP's prior compromises of Trivy, KICS, LiteLLM, and Telnyx, suggesting the same actor is stockpiling publishing credentials and selling access downstream. If accurate, the cadence of high-download package compromises will accelerate, and every open-source maintainer account is now a high-value target.

Datadog Security Labs: Axios Account Takeover Forensics, Full Attack Timeline, and the Trusted Publishing Gap

Datadog's timeline reconstruction shows the C2 domain was registered 18 hours before the malicious packages dropped, and the attacker bypassed GitHub Actions OIDC trusted publishing by pushing directly via CLI. The 50% stat on orgs consuming new packages within a day of release is the clearest argument yet for adding a version delay policy to your CI/CD.

Elastic Security Labs: Single Cross-Platform RAT Framework, Shared C2 Protocol, and the IE8 User-Agent Detection Signal

Elastic confirms the three platform payloads are one RAT with three native implementations sharing identical C2 protocol, beacon interval, and command set, pointing to a disciplined development team rather than a cobbled-together campaign. The hardcoded IE8 Windows XP user-agent on macOS and Linux is your cheapest detection rule: one network signature covers all three platforms.

News

Microsoft Attributes Axios npm RAT to North Korean Sapphire Sleet, Issues Mitigation Guidance

Microsoft's attribution to Sapphire Sleet adds nation-state weight to what might otherwise look like opportunistic credential theft. The key mitigation is concrete: strip caret and tilde prefixes from Axios entries in package.json and pin exact versions to kill auto-update behavior the RAT relies on.

Bitdefender Technical Advisory: RAT Execution Confirmed in the Wild, Dropper Self-Deletes to Block Forensics

Bitdefender telemetry confirms actual RAT execution attempts on customer systems, and Wiz puts execution at 3% of affected environments, meaning this is not theoretical. The dropper's self-deletion and package.json replacement detail is critical for IR teams: standard file-based forensics will miss it, so focus on process telemetry and network logs instead.