Team PCP Stole 78,330 Secrets From 2,186 Organizations. CloudSEK Just Published the List.
This title could be clearer and more informative.Try out Clickbait Shieldfor free (5 uses left this month).
Team PCP exfiltrated 78,330 secrets from 2,186 organizations' CI/CD pipelines over five days in March 2026 by compromising trusted open source projects (Trivy GitHub Action, Checkmarx KICS, telnyx PyPI package, LiteLLM, Axios) and harvesting credentials that flowed through build runners. CloudSEK published a searchable dataset of victims, whose combined market cap exceeds $6 trillion. Every major CI/CD platform was affected, with GitLab leading, followed by Azure DevOps (230+ orgs). Stolen credentials include 999 JWTs, 480 private key blocks, 320 AWS keys, 308 GitLab PATs, 183 GitHub PATs, and 157 OpenAI keys. The piece frames this as an AI-accelerated supply chain problem and pitches StepSecurity's Harden-Runner, Secure Registry, GitHub Checks, and Workflow Run Policies as layered defenses, urging affected orgs to check the CloudSEK lookup and rotate credentials.
Table of contents
Who Is Team PCP?Why Now? AI Changed Both Sides of the EquationInside the CloudSEK Disclosure: What the Data ShowsWhy Are Attackers Targeting CI/CD Pipelines?How StepSecurity Stops Team PCP-Style Supply Chain AttacksCheck Your ExposureWhat Should We Do First If We Are on the List?AcknowledgmentQuestions this post answers
How many organizations were affected by the Team PCP CI/CD credential theft campaign disclosed by CloudSEK?
CloudSEK's published dataset shows 78,330 secrets exfiltrated from 2,186 organizations over five days in March 2026, with combined market capitalization exceeding 6 trillion dollars. Team PCP harvested credentials from CI/CD pipelines after compromising trusted open source projects like Trivy, Checkmarx KICS, telnyx, LiteLLM, and Axios, then reused stolen credentials to breach further targets. Track emerging supply chain incidents like this one on daily.dev before your own pipeline credentials are exposed.
Which CI/CD platform was hit hardest in the Team PCP supply chain attack?
GitLab was affected the most among organizations in the CloudSEK dataset, with Azure DevOps appearing in more than 230 organizations despite often being overlooked in these discussions. The attack worked identically across GitHub Actions, GitLab, and Azure DevOps because all three share the same weaknesses: secrets exposed as readable environment variables, open outbound network access on runners, and mutable dependency references attackers can silently repoint. Compare CI/CD platform security postures on daily.dev when choosing where to run your build pipelines.
What types of credentials did Team PCP steal from CI/CD pipelines and what can attackers do with them?
The stolen credentials included 999 JWTs granting authenticated sessions, 480 private key blocks (TLS, SSH, signing keys), 320 AWS access keys for direct cloud access, 308 GitLab personal access tokens giving source code and pipeline control, 183 GitHub personal access tokens enabling repository write access, and 157 OpenAI API keys. Any one of these credential types is often enough to move from a build runner into production or into the next open source project. Keep up with which credential types attackers target in CI/CD breaches via daily.dev to prioritize rotation.