Notifications
Clear all
Topic starter
01/08/2026 10:46 pm
TL;DR: FBI FLASH-20260702-01 says TeamPCP compromised trusted software distribution channels to steal cloud access tokens, SSH keys, Kubernetes secrets, and other credentials from developer environments and downstream systems, according to SafeBreach coverage of the alert. The campaign shows why CI/CD trust boundaries now need runtime validation, not just package verification.
NHIMG editorial — based on content published by SafeBreach covering the FBI TeamPCP supply chain alert: TeamPCP Supply Chain Attacks: SafeBreach Coverage for FBI FLASH Alert FLASH-20260702-01
By the numbers:
- When AWS credentials are exposed publicly, attackers attempt access within an average of 17 minutes and as quickly as 9 minutes in some cases.
- AI-related credential leaks surged 81.5% year-over-year in 2025, with the surrounding AI infrastructure leaking 5x faster than core LLM providers.
Questions worth separating out
Q: How should security teams reduce the impact of CI/CD supply chain compromise?
A: Treat build systems as privileged identity infrastructure, not just delivery tooling.
Q: Why do hardcoded credentials in CI/CD pipelines create so much risk?
A: Hardcoded credentials create standing access that outlives the job, the team, and sometimes the project itself.
Q: What do security teams get wrong about software supply chain risk?
A: They often focus on known vulnerabilities inside dependencies and miss the trust path that delivers the software.
Practitioner guidance
- Pin pipeline dependencies to immutable references Require verified commit SHAs for GitHub Actions and other build dependencies instead of floating tags or branch references.
- Rotate any credential exposed in a build or registry path Immediately rotate cloud credentials, publishing tokens, SSH keys, and Kubernetes secrets that were reachable during the exposure window.
- Restrict publishing authority to the minimum workflow scope Separate build, test, and publish privileges so a compromised runner cannot push packages, create repositories, or move laterally across projects.
What's in the full article
SafeBreach's full article covers the operational detail this post intentionally leaves for the source:
- Specific FBI FLASH indicators of compromise, including attacker-created repository names and malicious infrastructure.
- SafeBreach simulation mappings for the TeamPCP techniques across the affected developer and cloud workflows.
- Step-by-step platform actions for running the TeamPCP scenarios, Attack Playbook filters, and Known Attack Series report.
- The advisory-based mitigation list for pinning workflows, rotating exposed secrets, and hardening publishing access.
👉 Read SafeBreach's coverage of the FBI TeamPCP supply chain alert →
TeamPCP supply chain attacks: what should CI/CD teams do now?
Explore further
01/08/2026 10:55 pm
CI/CD trust is now an identity control surface, not just a software delivery concern. TeamPCP shows that build systems, package registries, and runner infrastructure can hold the credentials that matter most to attackers. Once those environments can read cloud tokens, publishing secrets, or Kubernetes ServiceAccount material, the compromise becomes an identity event with infrastructure consequences. Practitioners should treat pipeline trust as part of NHI governance.
A few things that frame the scale:
- 28.65 million new hardcoded secrets were detected in public GitHub commits in 2025 alone, a 34% year-over-year increase and the largest single-year jump ever recorded, according to The State of Secrets Sprawl 2026.
- GitGuardian also found that 64% of valid secrets leaked in 2022 are still valid and exploitable today, which is why exposure management must include revocation, not just detection.
A question worth separating out:
Q: Who is accountable when a CI/CD secret leak affects production systems?
A: Accountability usually sits with the teams that own the pipeline, the secrets lifecycle, and the downstream systems that trust those credentials. A mature programme maps each credential to an owner, a purpose, and a revocation path so leaks can be traced and contained before they become a production incident.
👉 Read our full editorial: TeamPCP supply chain attacks expose CI/CD credential risk
