aviatrix logoAviatrix
Under Active Attack

Executive Summary

In August 2026, Australian Federal Police arrested two men aged 21 and 23 from Western Australia in connection with TeamPCP, a prolific cybercrime syndicate responsible for the longest-running software supply chain attack campaign ever recorded. The group executed sophisticated attacks starting in late 2025, embedding malicious code in hundreds of open-source software tools through their self-propagating Shai-Hulud worm, compromising developer credentials at repositories like GitHub and NPM, and extorting victims for profit. Their attacks impacted over 2,500 organizations including major technology companies, with notable breaches of LiteLLM AI infrastructure and over 3,800 GitHub repositories.

This incident highlights the growing threat of AI-enabled cybercrime and supply chain vulnerabilities as threat actors increasingly leverage large language models to compress the knowledge gap between attack research and operational execution, enabling less experienced criminals to operate at unprecedented scale without traditional operational discipline.

Why This Matters Now

Supply chain attacks are surging as threat actors exploit the interconnected nature of modern software development, with AI tools lowering barriers for less sophisticated criminals to execute complex campaigns at scale, making robust software supply chain security controls critical for organizations.

Attack Path Analysis

MITRE ATT&CK® Techniques

Potential Compliance Exposure

Sector Implications

Sources

Frequently Asked Questions

TeamPCP used their Shai-Hulud worm to compromise developer credentials at code repositories like GitHub and NPM, then injected malicious code into popular open-source tools that would spread to other developers' machines in a cyclical exploitation pattern.

Cloud Native Security Fabric Mitigations and ControlsCNSF

Based on the attack progression modeled above, these are the defensive controls that would constrain each stage.

Aviatrix Zero Trust CNSF would likely constrain TeamPCP's supply chain attack by limiting lateral propagation between development environments and reducing the blast radius of compromised credentials across cloud infrastructure.

Initial Compromise

Control: Cloud Native Security Fabric (CNSF)

Mitigation: Identity-aware access controls would likely limit the scope of compromised developer accounts, constraining their ability to access cloud infrastructure beyond authorized development environments and reducing credential reuse across multiple platforms.

Privilege Escalation

Control: Zero Trust Segmentation

Mitigation: Workload isolation policies would likely constrain privilege escalation by limiting compromised accounts to their designated cloud segments, reducing the ability to access production environments or administrative cloud service accounts across organizational boundaries.

Lateral Movement

Control: East-West Traffic Security

Mitigation: Traffic inspection and micro-segmentation would likely constrain worm propagation between cloud workloads, limiting the ability to spread laterally across development environments and reducing the reach of self-propagating malicious code in cloud infrastructure.

Command & Control

Control: Multicloud Visibility & Control

Mitigation: Unified visibility across cloud environments would likely detect suspicious communication patterns from compromised workloads, constraining persistent C2 channels and reducing the attackers' ability to coordinate operations across multiple cloud platforms undetected.

Exfiltration

Control: Egress Security & Policy Enforcement

Mitigation: Controlled egress policies would likely constrain large-scale data exfiltration by monitoring and restricting outbound data flows from cloud workloads, reducing the volume and scope of sensitive information that could be transferred to external breach forums.

Impact (Mitigations)

Despite security controls constraining the attack scope, residual impact would likely include reduced trust in development toolchains and potential exposure of cloud assets that were accessed before segmentation policies could be fully enforced across all environments.

Impact at a Glance

Affected Business Functions

  • Software Development
  • AI Infrastructure
  • Cloud Services
  • Open Source Package Management
Operational Disruption

Estimated downtime: 7 days

Financial Impact

Estimated loss: N/A

Data Exposure

Cloud service keys, API credentials, authentication tokens, and proprietary source code from over 2,500 organizations including major technology companies. Compromised GitHub repositories containing intellectual property and development secrets from 3,800+ code repositories.

Recommended Actions

  • • Implement Zero Trust Segmentation to prevent lateral movement between development environments and production systems, limiting blast radius of supply chain compromises
  • • Deploy Egress Security & Policy Enforcement to detect and block unauthorized data exfiltration to external repositories and breach forums
  • • Enable Multicloud Visibility & Control to monitor anomalous interactions across development platforms and detect suspicious automation patterns
  • • Establish Threat Detection & Anomaly Response capabilities to identify compromised developer accounts and malicious code injection attempts
  • • Implement East-West Traffic Security controls to prevent worm propagation between workloads and contain supply chain attacks within isolated network segments

Secure the Paths Between Cloud Workloads

A cloud-native security fabric that enforces Zero Trust across workload communication—reducing attack paths, compliance risk, and operational complexity.

Stop Advanced ThreatsGet a Free Workload Attack Path AssessmentUnder Active Attack?
Cta pattren Image