Notifications
Clear all
Topic starter
02/08/2026 11:44 am
TL;DR: TeamPCP chained GitHub Actions misconfigurations, package tampering, and credential harvesting across Trivy, Checkmarx, LiteLLM, and Bitwarden CLI, showing how one CI foothold can pivot through multiple trusted channels, according to Semgrep. The real control question is not whether a single repository is secure, but whether CI, publishing, and secret-bearing workflows are pinned, isolated, and auditable enough to stop token reuse.
NHIMG editorial — based on content published by Semgrep covering the TeamPCP supply chain campaign: supply chain attacks, CI credential theft, and package tampering
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 CI and publishing systems create such a large identity risk?
A: Because they combine automation, secrets access, and downstream distribution rights in one place.
Q: What breaks when GitHub Actions are referenced by tag instead of SHA?
A: The trust target becomes mutable.
Practitioner guidance
- Pin release workflows to immutable commit SHAs Replace mutable action tags in release and deployment pipelines with commit SHA references, especially where the workflow can publish packages or access secrets.
- Separate build steps from publish authority Split untrusted build or test stages from the job that requests publish tokens or registry credentials.
- Treat CI jobs as credential collection points Inventory which workflows can read environment variables, access secret managers, or echo tokens into logs.
What's in the full article
Semgrep's full analysis covers the operational detail this post intentionally leaves for the source:
- Exact package and workflow windows for Trivy, Checkmarx, LiteLLM, and Bitwarden CLI exposure
- Semgrep detection rule examples for insecure pull_request_target workflow patterns
- Step-by-step guidance for pinning GitHub Actions to SHAs and setting package cooldowns
- File-level and hash-level indicators that security teams can use to triage affected environments
👉 Read Semgrep's analysis of the TeamPCP supply chain campaign →
CI credential theft in TeamPCP: what practitioners need to review?
Explore further
02/08/2026 12:55 pm
Mutable build references are a governance failure, not a convenience feature. The TeamPCP campaign succeeded because many pipelines still treat tags as stable identity, even though tags can be moved after review. That is a broken assumption in NHI governance, because the consuming system is not binding trust to an immutable artifact. Practitioners should see mutable references as identity drift in the supply chain.
A question worth separating out:
Q: Who is accountable when a workflow compromise leads to malicious package releases?
A: Accountability is shared, but it cannot be vague. Repository owners, platform engineering, security, and package maintainers all have control over workflow design, secret scoping, and publishing identity governance. In regulated environments, incident response and control ownership should be documented before the next compromise happens.
👉 Read our full editorial: TeamPCP shows how supply chain attacks pivot through CI credentials
