Incident Score: Analysis & Impact (AQU1774441468)
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 Aqua Security'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 Aqua Security 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 Aqua Security breach identified under incident ID AQU1774441468.
The analysis begins with a detailed overview of Aqua Security's information like the linkedin page: https://www.linkedin.com/company/aquasecteam, the number of followers: 66228, the industry type: Computer and Network Security and the number of employees: 481 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 676 and after the incident was 655 with a difference of -21 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 Aqua Security and their customers.
On 01 February 2026, Aqua Security disclosed Supply Chain Attack, Extortion Campaign issues under the banner "Supply Chain Attack on Trivy Expands into Lapsus$-Linked Extortion Campaign, Compromising Over 1,000 SaaS Environments".
A sophisticated supply chain attack targeting Trivy, a widely used open-source security scanner, has escalated into a large-scale extortion campaign linked to the cybercriminal group Lapsus$, compromising over 1,000 enterprise SaaS environments.
The disruption is felt across the environment, affecting 1,000+ enterprise SaaS environments, GitHub repositories and npm ecosystem, and exposing True.
In response, moved swiftly to contain the threat with measures like Credential revocation and Takedown of malicious packages, and began remediation that includes Rotation of compromised credentials and Architectural isolation of commercial products.
The case underscores how Ongoing, teams are taking away lessons such as The incident underscores critical weaknesses in third-party code governance, implicit trust in supply chains, and the risks of mutable version tags in open-source projects, and recommending next steps like Strengthen third-party code governance, Monitor and secure supply chain dependencies and Implement stricter access controls for open-source projects.
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 compromise of Trivy’s VS Code extension, GitHub Action, and Docker Hub artifacts, Valid Accounts: Cloud Accounts (T1078.004) with high confidence (90%), supported by evidence indicating stolen credentials likely obtained through a third-party breach, and Trusted Relationship (T1199) with moderate to high confidence (85%), supported by evidence indicating exploitation of implicit trust in supply chains. Under the Execution tactic, the analysis identified Exploitation for Client Execution (T1203) with moderate to high confidence (80%), supported by evidence indicating malicious payloads distributed through manipulated version tags and User Execution: Malicious File (T1204.002) with moderate to high confidence (75%), supported by evidence indicating malicious npm packages distributed using compromised publish 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 stolen credentials used to backdoor multiple components and Server Software Component: Web Shell (T1505.003) with moderate to high confidence (70%), supported by evidence indicating persistent access to Aqua Security’s GitHub organization. Under the Privilege Escalation tactic, the analysis identified Valid Accounts: Cloud Accounts (T1078.004) with moderate to high confidence (85%), supported by evidence indicating stolen credentials used to escalate access to enterprise SaaS environments. Under the Defense Evasion tactic, the analysis identified Hijack Execution Flow: DLL Search Order Hijacking (T1574.001) with moderate to high confidence (75%), supported by evidence indicating malicious payloads distributed through manipulated version tags, Masquerading: Match Legitimate Name or Location (T1036.005) with moderate to high confidence (80%), supported by evidence indicating cached copies of malicious Trivy artifacts via mirror.gcr.io, and Impair Defenses: Disable or Modify Tools (T1562.001) with moderate to high confidence (70%), supported by evidence indicating defacing all 44 repositories with the message TeamPCP Owns Aqua Security. Under the Credential Access tactic, the analysis identified Steal Application Access Token (T1528) with high confidence (90%), supported by evidence indicating stolen credentials likely obtained through a third-party breach and Unsecured Credentials: Cloud Instance Metadata API (T1552.005) with moderate to high confidence (70%), supported by evidence indicating compromised publish tokens used to distribute malicious npm packages. Under the Lateral Movement tactic, the analysis identified Remote Services: Cloud Services (T1021.007) with moderate to high confidence (85%), supported by evidence indicating attackers funneled stolen access to broader criminal networks and Use Alternate Authentication Material: Application Access Token (T1550.001) with moderate to high confidence (80%), supported by evidence indicating stolen credentials used to access enterprise SaaS environments. Under the Impact tactic, the analysis identified Defacement: Internal Defacement (T1491.001) with high confidence (90%), supported by evidence indicating defacing all 44 repositories with the message TeamPCP Owns Aqua Security, Data Encrypted for Impact (T1486) with moderate confidence (50%), supported by evidence indicating extortion campaign linked to Lapsus$, and Resource Hijacking (T1496) with moderate to high confidence (70%), supported by evidence indicating compromise of 1,000+ enterprise SaaS environments. Under the Exfiltration tactic, the analysis identified Exfiltration Over C2 Channel (T1041) with moderate to high confidence (80%), supported by evidence indicating attackers funneled stolen access to broader criminal networks and Transfer Data to Cloud Account (T1537) with moderate to high confidence (75%), supported by evidence indicating data theft as a motivation for the attack. These correlations help security teams understand the attack chain and develop appropriate defensive measures based on the observed tactics and techniques.
Sources & References
- Aqua Security Rankiteo Cyber Incident Details: https://www.rankiteo.com/company/aquasecteam/incident/AQU1774441468
- Aqua Security CyberSecurity Rating page: https://www.rankiteo.com/company/aquasecteam
- Aqua Security Rankiteo Cyber Incident Blog Article: https://blog.rankiteo.com/aqu1774441468-trivy-cyber-attack-march-2026/
- Aqua Security CyberSecurity Score History: https://www.rankiteo.com/company/aquasecteam/history
- Aqua Security CyberSecurity Incident Source: https://www.csoonline.com/article/4149938/trivy-supply-chain-breach-compromises-over-1000-saas-environments-lapsus-joins-the-extortion-wave.html
- 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