Rankiteo Logo
Rankiteo
Leader in Cyber Underwriting
Loading...
NEWRankiteo Cyber Underwriting Desktop - Score, price, and bind from your desktop
WindowsmacOSLinux
Download
Analyze » Axios » AXI1775003215

Incident Score: Analysis & Impact (AXI1775003215)

The details regarding individual company incidents & reports gives you full view from every side.

Rankiteo Score Impact Analysis

Rankiteo Incident Impact-18
Company Score Before Incident759 / 1000
Company Score After Incident741 / 1000
Company LinkView Axios Profile
INCIDENT NUMBERAXI1775003215
Type of Cyber IncidentCyber Attack
ATTACK VECTORCompromised npm account
DATA EXPOSEDNA
INCIDENT DATE18/02/2021
STATUSContained

Key Highlights From The Incident Analysis

  • Timeline of Axios's Cyber Attack and lateral movement inside company's environment.
  • Overview of affected data sets, including SSNs and PHI, and why they materially increase incident severity.
  • How Rankiteo’s incident engine converts technical details into a normalized incident score.
  • How this cyber incident impacts Axios Rankiteo cyber scoring and cyber rating.
  • Rankiteo’s MITRE ATT&CK correlation analysis for this incident, with associated confidence level.

Full Incident Analysis Transcript

In this Rankiteo incident briefing, we review the Axios breach identified under incident ID AXI1775003215.

The analysis begins with a detailed overview of Axios's information like the linkedin page: https://www.linkedin.com/company/axios-media, the number of followers: 77832, the industry type: Internet News and the number of employees: 619 employees

After the initial compromise, the video explains how Rankiteo's incident engine converts technical details into a normalized incident score. The incident score before the incident was 759 and after the incident was 741 with a difference of -18 which is could be a good indicator of the severity and impact of the incident.

In the next step of the video, we will analyze in more details the incident and the impact it had on Axios and their customers.

On 31 March 2026, Axios disclosed Supply Chain Attack issues under the banner "Axios npm Account Hijacked to Distribute Cross-Platform RAT Malware".

On March 31, 2026, threat actors compromised the npm account of Axios, a widely used JavaScript library with over 100 million weekly downloads, to distribute remote access trojan (RAT) malware across Linux, Windows, and macOS.

The disruption is felt across the environment, affecting Linux, Windows, macOS.

In response, moved swiftly to contain the threat with measures like Detection and provision of IOCs by security firms, and began remediation that includes Verification of installations for malicious versions or artifacts, and stakeholders are being briefed through Advisories to organizations using Axios.

The case underscores how Contained, and recommending next steps like Verify installations for malicious versions or artifacts, monitor for IOCs provided by security firms, with advisories going out to stakeholders covering Organizations using Axios advised to verify installations.

Finally, we try to match the incident with the MITRE ATT&CK framework to see if there is any correlation between the incident and the MITRE ATT&CK framework.

The MITRE ATT&CK framework is a knowledge base of techniques and sub-techniques that are used to describe the tactics and procedures of cyber adversaries. It is a powerful tool for understanding the threat landscape and for developing effective defense strategies.

MITRE ATT&CK® Correlation Analysis

Rankiteo's analysis has identified several MITRE ATT&CK tactics and techniques associated with this incident, each with varying levels of confidence based on available evidence. Under the Initial Access tactic, the analysis identified Supply Chain Compromise: Compromise Software Supply Chain (T1195.002) with high confidence (95%), with evidence including compromised the npm account of Axios to distribute RAT malware, and malicious versions of Axios (1.14.1 and 0.30.4) were published and Valid Accounts: Cloud Accounts (T1078.004) with high confidence (90%), supported by evidence indicating compromised npm account of maintainer Jason Saayman. Under the Execution tactic, the analysis identified User Execution: Malicious File (T1204.002) with moderate to high confidence (85%), with evidence including post-install script to execute automatically, and downloading a second-stage payload tailored to the victim’s OS and Command and Scripting Interpreter: JavaScript (T1059.007) with moderate to high confidence (80%), supported by evidence indicating malicious dependency (plain-crypto-js) deployed via npm package. Under the Persistence tactic, the analysis identified Hijack Execution Flow: DLL Search Order Hijacking (T1574.001) with moderate to high confidence (70%), supported by evidence indicating malicious dependency (plain-crypto-js) injected into Axios package. Under the Defense Evasion tactic, the analysis identified Obfuscated Files or Information (T1027) with high confidence (90%), supported by evidence indicating malware used obfuscation techniques, Indicator Removal: File Deletion (T1070.004) with moderate to high confidence (85%), supported by evidence indicating malware deleted its own traces after execution, and Subvert Trust Controls: Code Signing Policy Modification (T1553.006) with moderate to high confidence (70%), supported by evidence indicating published without proper OIDC verification or matching GitHub commits. Under the Command and Control tactic, the analysis identified Application Layer Protocol: Web Protocols (T1071.001) with moderate to high confidence (80%), supported by evidence indicating c2 communication capability in macOS RAT. Under the Exfiltration tactic, the analysis identified Exfiltration Over C2 Channel (T1041) with moderate to high confidence (75%), supported by evidence indicating rAT capable of system reconnaissance and C2 communication. These correlations help security teams understand the attack chain and develop appropriate defensive measures based on the observed tactics and techniques.

Initial Access
Supply Chain Compromise: Compromise Software Supply Chain (95%)
Valid Accounts: Cloud Accounts (90%)
Execution
User Execution: Malicious File (85%)
Command and Scripting Interpreter: JavaScript (80%)
Persistence
Hijack Execution Flow: DLL Search Order Hijacking (70%)
Defense Evasion
Obfuscated Files or Information (90%)
Indicator Removal: File Deletion (85%)
Subvert Trust Controls: Code Signing Policy Modification (70%)
Command and Control
Application Layer Protocol: Web Protocols (80%)
Exfiltration
Exfiltration Over C2 Channel (75%)