Executive Summary
In March 2026, the cybercriminal group TeamPCP executed a sophisticated supply chain attack targeting multiple software packages and cloud services. The campaign began on March 19, 2026, with successive compromises of tools like Trivy, CanisterWorm, Checkmarx, LiteLLM, and Telnyx, occurring every 1-3 days. These attacks involved injecting malicious code into widely used software packages, enabling unauthorized access and data exfiltration from numerous downstream users. The rapid succession of these breaches highlighted the group's aggressive operational tempo and their focus on exploiting trusted software supply chains.
As of March 28, 2026, a notable shift in TeamPCP's strategy was observed, with no new compromises reported in the preceding 48 hours. This pause suggests a transition from expanding their foothold to monetizing the vast trove of stolen credentials and data. The group's explicit intent to maintain a prolonged presence indicates that future supply chain attacks remain a significant threat. Organizations are advised to remain vigilant, conduct thorough security assessments, and implement robust monitoring to detect and mitigate potential breaches stemming from this campaign.
Why This Matters Now
The recent operational pause by TeamPCP indicates a strategic shift towards monetizing stolen data, posing an immediate risk of credential abuse and further exploitation. Organizations must act swiftly to secure their systems and prevent potential breaches.
Attack Path Analysis
TeamPCP initiated their attack by compromising CI/CD pipelines through malicious code injections in widely used packages, leading to unauthorized access to development environments. They escalated privileges by harvesting credentials from compromised pipelines, enabling deeper access into organizational networks. Utilizing these elevated privileges, they moved laterally across cloud environments, targeting additional resources and services. Establishing command and control channels, they exfiltrated sensitive data to external servers. The exfiltrated data was then monetized through partnerships with ransomware affiliates, leading to significant operational disruptions and data breaches.
Kill Chain Progression
Initial Compromise
Description
TeamPCP injected malicious code into popular software packages, compromising CI/CD pipelines and gaining unauthorized access to development environments.
MITRE ATT&CK® Techniques
Supply Chain Compromise
Valid Accounts
Unsecured Credentials
Exfiltration Over Web Service
Inhibit System Recovery
Data Destruction
Application Layer Protocol
Potential Compliance Exposure
Mapping incident impact across multiple compliance frameworks.
PCI DSS 4.0 – Change Control Processes
Control ID: 6.4.1
NYDFS 23 NYCRR 500 – Cybersecurity Policy
Control ID: 500.03
DORA – ICT Risk Management Framework
Control ID: Article 5
CISA ZTMM 2.0 – Identity and Access Management
Control ID: 3.1
NIS2 Directive – Incident Handling
Control ID: Article 21
Sector Implications
Industry-specific impact of the vulnerabilities, including operational, regulatory, and cloud security risks.
Computer Software/Engineering
TeamPCP supply chain attacks target CI/CD pipelines, package registries, and developer credentials, directly compromising software development infrastructure and delivery mechanisms.
Computer/Network Security
Security vendors like Trivy and Checkmarx were compromised, weaponizing trusted security tools and creating detection blind spots for downstream customers.
Financial Services
PCI compliance requirements and encrypted traffic vulnerabilities expose financial institutions to credential theft and lateral movement through compromised development environments.
Health Care / Life Sciences
HIPAA compliance mappings and AstraZeneca breach claims indicate healthcare sector exposure through compromised software supply chains and encrypted data exfiltration.
Sources
- TeamPCP Supply Chain Campaign: Update 003 - Operational Tempo Shift as Campaign Enters Monetization Phase With No New Compromises in 48 Hours, (Sat, Mar 28th)https://isc.sans.edu/diary/rss/32842Verified
- Supply Chain Compromise: Compromise Software Supply Chain, Sub-technique T1195.002 - Enterprisehttps://attack.mitre.org/techniques/T1195/002/Verified
- Supply Chain Compromisehttps://www.cisa.gov/news-events/alerts/2021/01/07/supply-chain-compromiseVerified
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 controlled egress policies.
Control: Cloud Native Security Fabric (CNSF)
Mitigation: The attacker's ability to exploit compromised CI/CD pipelines may have been limited, reducing unauthorized access to development environments.
Control: Zero Trust Segmentation
Mitigation: The attacker's ability to escalate privileges may have been constrained, limiting unauthorized access to sensitive resources.
Control: East-West Traffic Security
Mitigation: The attacker's lateral movement across cloud environments could have been limited, reducing access to additional resources.
Control: Multicloud Visibility & Control
Mitigation: The establishment of command and control channels may have been constrained, limiting data exfiltration to external servers.
Control: Egress Security & Policy Enforcement
Mitigation: The exfiltration of sensitive data to external servers could have been limited, reducing data loss.
The monetization of exfiltrated data could have been constrained, reducing operational disruptions and data breaches.
Impact at a Glance
Affected Business Functions
- Software Development
- Continuous Integration/Continuous Deployment (CI/CD) Pipelines
- Package Management
- Credential Management
Estimated downtime: 14 days
Estimated loss: $5,000,000
Compromise of CI/CD pipelines leading to unauthorized access to source code repositories and sensitive credentials.
Recommended Actions
Key Takeaways & Next Steps
- • Implement Zero Trust Segmentation to enforce least privilege access and prevent lateral movement within cloud environments.
- • Deploy Egress Security & Policy Enforcement to monitor and control outbound traffic, mitigating unauthorized data exfiltration.
- • Utilize Threat Detection & Anomaly Response systems to identify and respond to behavioral anomalies in CI/CD pipelines.
- • Establish Multicloud Visibility & Control to gain comprehensive oversight of cloud resources and detect suspicious activities.
- • Regularly review and update supply chain security policies to address emerging threats and vulnerabilities.
