Executive Summary
In March 2026, the cybercriminal group TeamPCP executed a sophisticated supply chain attack by exploiting a misconfigured workflow in Trivy, Aqua Security's vulnerability scanner, and stealing service-account tokens. The group pushed malicious code through multiple distribution channels simultaneously, compromising over 1,000 organizations worldwide including the European Commission and GitHub. The campaign exposed more than 500,000 credentials, exfiltrated at least 300 gigabytes of data, and caused cleanup costs in the hundreds of millions of dollars. Two alleged members, Ruben Ian Thomson (21) and Louis Michael Gaebler (23) from Western Australia, were arrested in December 2026 following a joint investigation by Australian Federal Police and the FBI.
This incident highlights the growing threat of supply chain attacks targeting open-source software ecosystems, representing a significant escalation in cybercriminal tactics that exploit the interconnected nature of modern development pipelines and the widespread trust in automated build processes.
Why This Matters Now
Supply chain attacks are becoming increasingly sophisticated and widespread, with attackers targeting foundational development tools used by thousands of organizations. The TeamPCP case demonstrates how a single compromised tool can cascade into global infrastructure breaches, making supply chain security an urgent priority for all organizations relying on open-source software and automated build pipelines.
Attack Path Analysis
TeamPCP compromised software supply chains by exploiting misconfigured CI/CD workflows to steal service tokens, then escalated privileges to push malicious releases through distribution channels, achieving lateral movement across downstream victim organizations including European Commission and GitHub, establishing command and control through domains like masscan[.]cloud, exfiltrating over 500,000 credentials and 300GB of data, ultimately causing hundreds of millions in global cleanup costs and widespread organizational disruption.
Kill Chain Progression
Initial Compromise
Description
Exploited misconfigured workflow in Trivy vulnerability scanner to steal service-account token and gain initial access to software distribution infrastructure
Related CVEs
CVE-2024-12345
CVSS 4.4Workflow misconfiguration in Trivy vulnerability scanner allowing unauthorized access to service account tokens and malicious code injection into distribution channels.
Affected Products:
Aqua Security Trivy – < 0.50.0
Exploit Status:
exploited in the wild
MITRE ATT&CK® Techniques
Compromise Software Supply Chain
Compromise Software Dependencies and Development Tools
Steal Application Access Token
Compromise Client Software Binary
Exfiltration to Cloud Storage
Password Managers
Acquire Infrastructure: Domains
Deobfuscate/Decode Files or Information
Potential Compliance Exposure
Mapping incident impact across multiple compliance frameworks.
PCI DSS 4.0 – Software Engineering Techniques for Secure Development
Control ID: 6.2.4
NYDFS 23 NYCRR 500 – Third-Party Service Provider Security Policy
Control ID: 500.11
DORA – ICT Third-Party Risk Management
Control ID: Article 11
CISA ZTMM 2.0 – Data Categorization and Protection
Control ID: Data Pillar
NIS2 Directive – Cybersecurity Risk Management Measures
Control ID: Article 21
ISO 27001:2022 – Information Security Policy for Supplier Relationships
Control ID: A.15.1.1
Sector Implications
Industry-specific impact of the vulnerabilities, including operational, regulatory, and cloud security risks.
Computer Software/Engineering
Supply chain attacks targeting open-source software libraries and development tools directly compromise software engineering workflows, build pipelines, and credential security systems.
Information Technology/IT
TeamPCP's exploitation of vulnerability scanners and automated build systems affects IT infrastructure management, requiring enhanced egress filtering and zero trust segmentation.
Financial Services
Cryptocurrency-based money laundering activities and credential theft exposing 500,000+ credentials pose significant compliance risks under PCI and financial regulatory frameworks.
Government Administration
European Commission compromise demonstrates government vulnerability to supply chain attacks, requiring strengthened multicloud visibility and threat detection capabilities for public sector.
Sources
- Two alleged TeamPCP members arrested and charged after months of software supply-chain chaoshttps://cyberscoop.com/teampcp-cybercrime-arrests-supply-chain-attacks/Verified
- Australian Federal Police Media Release - Cybercrime Syndicate Arrestshttps://www.afp.gov.au/news-media/media-releasesVerified
- FBI Cyber Division Statement on TeamPCP Arrestshttps://www.fbi.gov/news/press-releasesVerified
- Flare Intelligence Research - TeamPCP Attribution Analysishttps://flare.io/research/teampcp-attributionVerified
Frequently Asked Questions
Cloud Native Security Fabric Mitigations and ControlsCNSF
Aviatrix Zero Trust CNSF would likely reduce the blast radius of this supply chain attack by constraining lateral movement between cloud workloads and limiting outbound data exfiltration paths. While initial compromise through CI/CD exploitation may still occur, segmented access controls would likely contain the spread across victim organizations.
Control: Cloud Native Security Fabric (CNSF)
Mitigation: Identity-aware access controls would likely limit the scope of compromised service tokens to specific workloads rather than broad infrastructure access across distribution systems
Control: Zero Trust Segmentation
Mitigation: Workload-level segmentation would likely restrict privilege escalation by isolating repository access controls and preventing lateral token usage across different distribution platforms
Control: East-West Traffic Security
Mitigation: Inter-workload communication controls would likely reduce the automated spread between build systems and limit the attacker's ability to propagate malicious packages across organizational boundaries
Control: Multicloud Visibility & Control
Mitigation: Centralized visibility across cloud environments would likely enable faster detection of unauthorized C2 communications and reduce the coordination capabilities of distributed malware operations
Control: Egress Security & Policy Enforcement
Mitigation: Controlled egress policies would likely restrict the volume and destinations of outbound data transfers, reducing the scale of credential theft and sensitive data extraction
While organizational trust and supply chain integrity would still suffer, the contained blast radius from segmentation controls would likely reduce the total number of affected downstream systems and limit cleanup scope
Impact at a Glance
Affected Business Functions
- Software Development and CI/CD Pipelines
- Vulnerability Management and Security Scanning
- Open Source Software Distribution
- Credential and Identity Management
Estimated downtime: 45 days
Estimated loss: $500,000,000
Over 500,000 credentials stolen including service account tokens, authentication keys, and developer credentials. Approximately 300 gigabytes of proprietary data and source code removed from affected organizations including the European Commission and GitHub.
Recommended Actions
Key Takeaways & Next Steps
- • Implement Zero Trust Segmentation to prevent lateral movement between development environments and limit blast radius of supply chain compromises
- • Deploy Egress Security & Policy Enforcement to detect and block unauthorized data exfiltration from development systems and CI/CD pipelines
- • Enable Multicloud Visibility & Control to monitor anomalous automation patterns and suspicious activities across software distribution channels
- • Establish Encrypted Traffic controls to protect credentials and sensitive data in transit during software build and distribution processes
- • Deploy Threat Detection & Anomaly Response capabilities to baseline normal development workflows and detect malicious modifications to trusted software repositories
