Incident Score: Analysis & Impact (SEMAQU1774434920)
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 Semgrep'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 Semgrep 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 Semgrep breach identified under incident ID SEMAQU1774434920.
The analysis begins with a detailed overview of Semgrep's information like the linkedin page: https://www.linkedin.com/company/semgrep, the number of followers: 17495, the industry type: Software Development and the number of employees: 234 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 753 and after the incident was 735 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 Semgrep and their customers.
On 22 March 2026, Aqua Security (Trivy open-source project) disclosed Supply Chain Attack issues under the banner "Sophisticated Supply Chain Attack Targets Trivy Vulnerability Scanner, Exposing CI/CD Risks".
Aqua Security uncovered a sophisticated supply chain attack targeting its open-source Trivy vulnerability scanner, demonstrating how threat actors can exploit trusted development workflows to steal sensitive data without detection.
The disruption is felt across the environment, affecting CI/CD pipelines using compromised Trivy versions, and exposing Cloud credentials (AWS, GCP, Azure), API tokens, access keys, SSH private keys, Kubernetes service account tokens, Docker configuration files.
In response, teams activated the incident response plan, moved swiftly to contain the threat with measures like Revoked compromised credentials, removed malicious artifacts, transitioned away from long-lived tokens, and began remediation that includes Upgraded to Trivy v0.69.2 or v0.69.3, pinned dependencies to immutable commit SHA hashes.
The case underscores how Contained, forensic investigation completed, teams are taking away lessons such as The attack exploited over-reliance on mutable version tags in CI/CD pipelines. Pinning dependencies to immutable commit SHA hashes could have prevented the compromise, and recommending next steps like Upgrade to Trivy v0.69.2 or v0.69.3, Use safe GitHub Action versions: trivy-action v0.35.0 or setup-trivy v0.2.6 and Rotate all secrets if v0.69.4 was executed in any pipeline, with advisories going out to stakeholders covering Organizations using Trivy in automated workflows should upgrade and rotate secrets.
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 (90%), supported by evidence indicating hijacked existing GitHub repositories aquasecurity/trivy-action and setup-trivy and Valid Accounts: Cloud Accounts (T1078.004) with moderate to high confidence (80%), supported by evidence indicating stolen credentials used to force-push malicious commits to version tags. Under the Execution tactic, the analysis identified Serverless Execution: Malicious Code Injection (T1648.001) with moderate to high confidence (80%), supported by evidence indicating injected payload ran before Trivy’s legitimate scanning process in CI/CD pipelines and Command and Scripting Interpreter: JavaScript (T1059.007) with moderate to high confidence (70%), supported by evidence indicating automated workflows pulled compromised code via mutable tags. Under the Persistence tactic, the analysis identified Server Software Component: Web Shell (T1505.003) with moderate confidence (60%), supported by evidence indicating attempts to reestablish persistence via multi-stage operation (March 22) and Account Manipulation: Additional Cloud Credentials (T1098.003) with moderate to high confidence (70%), supported by evidence indicating incomplete credential rotation allowed attackers to retain access. Under the Privilege Escalation tactic, the analysis identified Valid Accounts: Cloud Accounts (T1078.004) with moderate to high confidence (80%), supported by evidence indicating cI/CD pipelines’ broad infrastructure access enabled privilege escalation. Under the Credential Access tactic, the analysis identified Unsecured Credentials: Credentials In Files (T1552.001) with high confidence (90%), supported by evidence indicating exfiltrated cloud credentials, API tokens, SSH private keys, Kubernetes tokens and Steal Application Access Token (T1528) with moderate to high confidence (80%), supported by evidence indicating stolen credentials used to hijack GitHub repositories. Under the Collection tactic, the analysis identified Data from Cloud Storage (T1530) with moderate to high confidence (80%), supported by evidence indicating exfiltrated AWS, GCP, Azure credentials and Docker configuration files and Data from Code Repositories (T1213.003) with moderate to high confidence (70%), supported by evidence indicating hijacked GitHub repositories aquasecurity/trivy-action and setup-trivy. Under the Exfiltration tactic, the analysis identified Exfiltration Over C2 Channel (T1041) with high confidence (90%), supported by evidence indicating exfiltrated data via C2 domains such as scan.aquasecurtiy.org, plug-tab-protective-relay.trycloudflare.com and Exfiltration Over Web Service: Exfiltration to Cloud Storage (T1567.002) with moderate to high confidence (70%), supported by evidence indicating iCP-based C2 such as tdtqy-oyaaa-aaaae-af2dq-cai.raw.icp0.io. Under the Lateral Movement tactic, the analysis identified Use Alternate Authentication Material: Application Access Token (T1550.001) with moderate to high confidence (80%), supported by evidence indicating stolen cloud credentials and Kubernetes tokens enabled lateral movement. Under the Defense Evasion tactic, the analysis identified Hijack Execution Flow: DLL Search Order Hijacking (T1574.001) with moderate to high confidence (70%), supported by evidence indicating malicious commits executed undetected before legitimate Trivy scanning and Masquerading: Match Legitimate Name or Location (T1036.005) with moderate to high confidence (80%), supported by evidence indicating force-pushed malicious commits to version tags (e.g., v0.x). These correlations help security teams understand the attack chain and develop appropriate defensive measures based on the observed tactics and techniques.
Sources & References
- Semgrep Rankiteo Cyber Incident Details: https://www.rankiteo.com/company/semgrep/incident/SEMAQU1774434920
- Semgrep CyberSecurity Rating page: https://www.rankiteo.com/company/semgrep
- Semgrep Rankiteo Cyber Incident Blog Article: https://blog.rankiteo.com/semaqu1774434920-organizations-using-trivy-in-automated-workflows-aqua-security-cyber-attack-march-2026/
- Semgrep CyberSecurity Score History: https://www.rankiteo.com/company/semgrep/history
- Semgrep CyberSecurity Incident Source: https://cyberpress.org/aqua-securitys-trivy-scanner-hit-by-supply-chain-attack/
- 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