TeamPCP poisoned developer tools and stole GitHub internal repos
First merged summary.
TeamPCP’s poisoned Trivy, LiteLLM, and Nx Console releases led to theft of about 3,800 GitHub internal repositories; GitHub says customer repos were not accessed.
GitHub says customer-owned repositories were not accessed after TeamPCP stole about 3,800 internal repositories, some containing customer-support excerpts. GBHackers, citing Aqua Security, says a late-February intrusion through a misconfigured GitHub Actions environment let attackers poison Trivy release automation; Cyber Security News, citing BlackFog, dates entry into Aqua’s build systems to March 2026. Malicious Trivy 0.69.4, LiteLLM 1.82.8, and Nx Console 18.95.0 followed, and a poisoned VS Code build that remained available about 18 minutes compromised a GitHub employee device on May 18. GitHub removed that build, isolated the device, and rotated secrets. According to Cyber Security News, stolen repositories were listed for at least $50,000, while Australian charges and a US indictment remain unproven.
- Malicious Trivy 0.69.4 published; 76 of 77 trivy-action tags redirected.
- LiteLLM 1.82.8 added a malicious .pth file that runs at Python startup.
- Nx Console has more than 2.2 million installations across versions.
- Poisoned Nx Console build stayed on the VS Code Marketplace about 18 minutes.
- GitHub later required a GitHub Enterprise Server signing-key update.
- BlackFog also ties the campaign to Checkmarx KICS.
What each outlet adds
beyond the shared facts- GBHackersAqua’s late-February path, package versions, tag redirects, and GitHub’s response.
- Cyber Security News18-minute marketplace window, $50,000 listing, March timing, and unproven charges.
Coverage
oldest first · one row per article · UTCTeamPCP stole about 3,800 GitHub repos via poisoned developer tools
GitHub says customer-owned repositories were not accessed, but some stolen internal repos held customer support excerpts.
Poisoned Nx Console extension stole GitHub tokens in 18 minutes
TeamPCP claims about 3,800 internal repositories from one GitHub employee; GitHub says customer repositories were not affected.