TeamPCP exposure: are your rotation tickets actually closing access?

TL;DR: The TeamPCP archive appears to contain more than 2,500 organizations and roughly 434,000 CI/CD pipelines, according to Vectra AI, but the deeper issue is that reconstructed exposure can persist after a remediation ticket is closed. The control failure is not rotation alone, but proving that every old credential is actually rejected and every surviving identity is removed.

Editorial analysis by NHI Mgmt Group, based on content published by Vectra AI: “The Credentials Were Rotated. They Still Worked.”.

By the numbers:

• The archive was linked to more than 2,500 organizations and roughly 434,000 CI/CD pipelines.
• Hudson Rock said the archive contained a 153 GB collection of 433,909 files.
• SOCRadar found that 2,085 of 2,188 organization records, or 95 percent, showed collection activity before March 24.

Key questions

Q: What breaks when teams rotate a secret but do not remove all copies?

A: Rotation only protects the new value if every old copy is retired.

Q: Why do leaked pipeline credentials create risk even after the public incident window has passed?

A: Because collection, publication, and reuse are different phases.

Q: How do security teams know if credential rotation actually worked?

A: They need proof that every consumer rejected the old credential, every dependent workflow has moved to the replacement, and no residual access path still functions.

Practitioner guidance

• Verify revocation, not just rotation Confirm that each old cloud key, repository token, service account, and AI provider key is rejected at every system that can authenticate it, not only replaced in a vault.
• Expand hunt windows to the earliest collection point Search pipeline logs, repository events, and cloud sign-ins back to the first evidence of collection, even if that precedes the public incident date by days or weeks.
• Inventory all identities touched by automation workflows List every service account, CI runner credential, publish token, and package signing identity that the affected workflows could reach, then verify each one independently.

Bottom line: The TeamPCP disclosures show that closing a remediation ticket does not prove an old automation credential has been invalidated.

Explore further

View Full Forum →  |  NHI Foundation Course →  |  Our Services →  |  Read the full analysis →