Executive Summary
In March 2026, the threat actor group TeamPCP executed a sophisticated supply chain attack targeting Aqua Security's Trivy, a widely used open-source vulnerability scanner. By exploiting unrotated credentials from a prior breach, they injected credential-stealing malware into Trivy's official releases, compromising CI/CD pipelines globally. This attack led to unauthorized access to sensitive credentials, including cloud access keys and SSH keys, across numerous organizations. The incident underscores the critical need for robust security measures within software supply chains, as attackers increasingly exploit trusted tools to infiltrate development environments. Organizations must enhance their monitoring and validation processes to detect and prevent such compromises.
Why This Matters Now
The Trivy supply chain attack highlights the escalating threat of attackers leveraging trusted security tools to infiltrate development environments. As supply chain attacks become more prevalent, organizations must prioritize securing their CI/CD pipelines and implement stringent validation processes to prevent similar incidents.
Attack Path Analysis
Attackers compromised the Trivy and KICS security scanners by injecting malicious code into their GitHub repositories, leading to credential theft and unauthorized access to development environments. They escalated privileges by exploiting the compromised scanners to gain access to sensitive credentials and production databases. Using the stolen credentials, attackers moved laterally to infiltrate additional systems within the development pipeline. They established command and control by creating backdoors and using exfiltration methods to maintain persistent access. Sensitive data, including cloud credentials and personal access tokens, were exfiltrated to external servers. The attack resulted in widespread credential theft and potential fraud, impacting multiple organizations relying on the compromised scanners.
Kill Chain Progression
Initial Compromise
Description
Attackers injected malicious code into the GitHub repositories of Trivy and KICS security scanners, compromising their integrity.
Related CVEs
CVE-2026-33634
CVSS 8.8A supply chain attack on Trivy allowed attackers to publish malicious versions of the software, leading to potential credential theft.
Affected Products:
Aqua Security Trivy – 0.69.4
Aqua Security trivy-action – 0.0.1 – 0.34.2
Aqua Security setup-trivy – 0.2.0 – 0.2.6
Exploit Status:
exploited in the wild
MITRE ATT&CK® Techniques
Compromise Software Supply Chain
Compromise Software Dependencies and Development Tools
Compromise Hardware Supply Chain
Supply Chain Compromise
Potential Compliance Exposure
Mapping incident impact across multiple compliance frameworks.
PCI DSS 4.0 – Ensure all system components and software are protected from known vulnerabilities
Control ID: 6.2
NYDFS 23 NYCRR 500 – Application Security
Control ID: 500.08
DORA – ICT Risk Management Framework
Control ID: Article 6
CISA ZTMM 2.0 – Supply Chain Risk Management
Control ID: 3.1
NIS2 Directive – Cybersecurity Risk Management Measures
Control ID: Article 21
Sector Implications
Industry-specific impact of the vulnerabilities, including operational, regulatory, and cloud security risks.
Computer Software/Engineering
Supply chain attacks targeting AppSec scanners directly compromise development pipelines, exposing source code, credentials, and customer data through malicious repository scanning.
Computer/Network Security
Security vendors face reputational and operational risks as compromised scanning tools enable downstream attacks against Fortune 1000 clients and government agencies.
Financial Services
Banking institutions using vulnerable AppSec scanners risk exposure of production databases, cloud credentials, and sensitive customer data through supply chain compromises.
Defense/Space
Defense contractors utilizing compromised security scanning tools face potential state-sponsored infiltration of classified development environments and sensitive project repositories.
Sources
- When AppSec Scanners Become a Supply Chain Attack Vectorhttps://www.darkreading.com/application-security/when-appsec-scanners-become-supply-chain-attack-vectorVerified
- Guidance for detecting, investigating, and defending against the Trivy supply chain compromisehttps://www.microsoft.com/en-us/security/blog/2026/03/24/detecting-investigating-defending-against-trivy-supply-chain-compromise/Verified
- Trivy ecosystem supply chain was briefly compromisedhttps://advisories.gitlab.com/pkg/golang/github.com/aquasecurity/trivy/CVE-2026-33634/Verified
- Trivy CVE-2026-33634 Turned CI/CD Scanners Into Secret-Stealing Malwarehttps://threatfrontier.com/articles/trivy-cve-2026-33634-cicd-scanner-supply-chain-secret-stealingVerified
Frequently Asked Questions
Cloud Native Security Fabric Mitigations and ControlsCNSF
Aviatrix Zero Trust CNSF is pertinent to this incident as it could have constrained the attacker's ability to move laterally and exfiltrate data by enforcing strict segmentation and identity-based access controls.
Control: Cloud Native Security Fabric (CNSF)
Mitigation: The CNSF may have limited the attacker's ability to exploit compromised scanners by enforcing strict workload isolation and identity-based access controls.
Control: Zero Trust Segmentation
Mitigation: Zero Trust Segmentation would likely have restricted unauthorized access to sensitive credentials and databases by enforcing least-privilege access policies.
Control: East-West Traffic Security
Mitigation: East-West Traffic Security may have constrained lateral movement by monitoring and controlling internal traffic flows between workloads.
Control: Multicloud Visibility & Control
Mitigation: Multicloud Visibility & Control would likely have detected and constrained unauthorized command and control communications across cloud environments.
Control: Egress Security & Policy Enforcement
Mitigation: Egress Security & Policy Enforcement may have restricted unauthorized data exfiltration by controlling outbound traffic and enforcing egress policies.
The overall impact of credential theft and potential fraud could have been reduced by limiting the attacker's reach and access to sensitive systems.
Impact at a Glance
Affected Business Functions
- Software Development
- Continuous Integration/Continuous Deployment (CI/CD) Pipelines
Estimated downtime: 7 days
Estimated loss: $500,000
Potential exposure of sensitive credentials and secrets used within CI/CD pipelines.
Recommended Actions
Key Takeaways & Next Steps
- • Implement Zero Trust Segmentation to restrict access and minimize lateral movement within development environments.
- • Enhance Threat Detection & Anomaly Response capabilities to identify and respond to suspicious activities promptly.
- • Enforce Egress Security & Policy Enforcement to monitor and control outbound traffic, preventing unauthorized data exfiltration.
- • Utilize Multicloud Visibility & Control to gain comprehensive insights into cloud environments and detect anomalies.
- • Regularly audit and update security scanners and development tools to ensure their integrity and prevent supply chain compromises.
