What Happened
The Australian Federal Police charged two Western Australia men, aged 21 and 23, with a combined 14 offences over their alleged role in TeamPCP, a group blamed for the longest-running spree of software supply chain attacks on record. Officers from the AFP and Western Australia Police Force executed search warrants at properties in Cottesloe, Hamilton Hill, and Mandurah on August 26, seizing electronic devices for forensic analysis. TeamPCP is the group behind the March 2026 compromise of the open source security scanners Trivy and Checkmarx KICS along with the LiteLLM AI gateway, an attack chain reaching more than 2,100 organizations and roughly 434,000 CI/CD pipelines through a poisoned package left live on PyPI for approximately 40 minutes.
Why This Matters for Canadian Organizations
The original March attack stole SSH keys, cloud credentials, Kubernetes tokens, and LLM API keys from any pipeline pulling the poisoned package during its brief publishing window, a scope wide enough to have touched Canadian development and DevOps teams using these widely adopted tools. Arrests in open source supply chain cases remain rare, since attackers distributing malicious packages through public registries typically operate anonymously across jurisdictions that complicate attribution and prosecution. This case offers a working example of cross-border law enforcement cooperation reaching a named suspect, which carries deterrence value even for organizations with no direct exposure to the original incident. Under OSFI B-13 and general PIPEDA obligations, Canadian organizations pulling the affected packages during the exposure window still carry responsibility for confirming whether credentials exposed at the time were rotated.
What to Do
Organizations using Trivy, Checkmarx KICS, or LiteLLM should confirm the March 2026 credential rotation was completed across every affected pipeline, not only primary production environments, since forgotten secondary pipelines commonly retain stale secrets. Development teams should review dependency-pinning practices and CI/CD secret scoping to reduce the blast radius of a similar future compromise, limiting any single pipeline’s access to only the credentials it needs. Security teams should treat this arrest as a prompt to audit whether lessons from the original incident were fully implemented rather than only patched in the moment. Full details are available from Krebs on Security.
