Incident Score: Analysis & Impact (NX1773383570)
The details regarding individual company incidents & reports gives you full view from every side.
Rankiteo Score Impact Analysis
Key Highlights From The Incident Analysis
- Timeline of Nx'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 Nx 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 Nx breach identified under incident ID NX1773383570.
The analysis begins with a detailed overview of Nx's information like the linkedin page: https://www.linkedin.com/company/nx, the number of followers: 0, the industry type: Computer Networking and the number of employees: 31 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 803 and after the incident was 790 with a difference of -13 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 Nx and their customers.
On 01 January 2026, a cybersecurity incident called "UNC6426 Exploits npm Supply Chain Attack to Compromise AWS Environment in 72 Hours" came to light.
A threat group identified as UNC6426 achieved full compromise of an organization’s AWS environment within 72 hours by leveraging credentials stolen during the August npm supply chain attack targeting Nx, an open-source codebase management platform.
The disruption is felt across the environment, affecting AWS environment, GitHub repositories and CI/CD pipeline, and exposing AWS API keys, application keys, S3 bucket objects.
Formal response steps have not been shared publicly yet.
The case underscores how teams are taking away lessons such as The attack underscores the risks of supply chain compromises and the need for enhanced security controls, including package managers that restrict postinstall scripts, sandboxing tools, and monitoring for suspicious IAM activity, and recommending next steps like Restrict postinstall scripts in package managers, Implement sandboxing tools and Monitor for suspicious IAM activity.
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%), supported by evidence indicating leveraging credentials stolen during the August npm supply chain attack. Under the Credential Access tactic, the analysis identified Steal Application Access Token (T1528) with high confidence (90%), with evidence including exfiltrating keys in the initial attack, and obtained AWS API keys and Unsecured Credentials: Cloud Instance Metadata API (T1552.005) with moderate to high confidence (80%), supported by evidence indicating generated temporary AWS Security Token Service (STS) tokens. Under the Persistence tactic, the analysis identified Account Manipulation: Additional Cloud Credentials (T1098.001) with moderate to high confidence (85%), supported by evidence indicating generated temporary AWS Security Token Service (STS) tokens. Under the Discovery tactic, the analysis identified Cloud Service Discovery (T1526) with high confidence (90%), with evidence including enumerated the environment, and enumerated and accessed S3 bucket objects and Account Discovery: Cloud Account (T1087.004) with moderate to high confidence (80%), supported by evidence indicating accessed the victim’s GitHub repository. Under the Lateral Movement tactic, the analysis identified Use Alternate Authentication Material: Application Access Token (T1550.001) with high confidence (90%), with evidence including aWS API keys, and temporary AWS Security Token Service (STS) tokens. Under the Collection tactic, the analysis identified Data from Cloud Storage Object (T1530) with high confidence (90%), supported by evidence indicating accessed S3 bucket objects. Under the Impact tactic, the analysis identified Data Destruction (T1485) with moderate to high confidence (85%), supported by evidence indicating terminated production EC2 and RDS instances and Defacement: Internal Defacement (T1491.001) with moderate to high confidence (80%), supported by evidence indicating renamed and made public the organization’s GitHub repositories. Under the Defense Evasion tactic, the analysis identified Use Alternate Authentication Material: Application Access Token (T1550.001) with moderate to high confidence (80%), supported by evidence indicating temporary AWS Security Token Service (STS) tokens and Valid Accounts: Cloud Accounts (T1078.004) with high confidence (90%), with evidence including aWS API keys, and stolen credentials. Under the Exfiltration tactic, the analysis identified Transfer Data to Cloud Account (T1537) with moderate to high confidence (70%), supported by evidence indicating accessed S3 bucket objects (implies potential exfiltration). These correlations help security teams understand the attack chain and develop appropriate defensive measures based on the observed tactics and techniques.
Sources & References
- Nx Rankiteo Cyber Incident Details: https://www.rankiteo.com/company/nx/incident/NX1773383570
- Nx CyberSecurity Rating page: https://www.rankiteo.com/company/nx
- Nx Rankiteo Cyber Incident Blog Article: https://blog.rankiteo.com/nx1773383570-nx-cyber-attack-march-2026/
- Nx CyberSecurity Score History: https://www.rankiteo.com/company/nx/history
- Nx CyberSecurity Incident Source: https://www.scworld.com/brief/nx-npm-supply-chain-hack-weaponized-to-breach-aws-environment
- Rankiteo A.I CyberSecurity Rating methodology: https://www.rankiteo.com/Images/rankiteo_algo.pdf
- Rankiteo TPRM Scoring methodology: https://static.rankiteo.com/model/rankiteo_tprm_methodology.pdf