Trapdex Subscribe

CampaignsPublisher / pipeline compromise

Trivy release and trivy-action / setup-trivy tag hijack

Do this now

  1. Pin third-party actions to full commit SHAs
  2. Rotate secrets exposed to any trivy-action or setup-trivy run between 19 and 23 Mar 2026
  3. Block egress from runners to the listed domains
  4. After an incident, revoke all affected credentials at once

Indicators

For blocklists and log searches. All values are defanged.

  • domain3
  • ip1

CSVJSONAll 4 indicators

What happened

After an earlier Trivy incident disclosed on 1 Mar, credential rotation was incomplete and the attacker kept access. On 19 Mar they published a malicious Trivy 0.69.4 release and force-moved most trivy-action tags plus the setup-trivy tags to credential-stealing code, then added malicious Docker images on 22 Mar. A Checkmarx GitHub Action was hit in parallel, and stolen tokens led to the LiteLLM compromise.

  • Docker Hub
  • GitHub Container Registry
  • GitHub Actions
  • GitHub Releases

Attack chain

  1. Lure

    No phishing; pipelines pinned to mutable tags pulled the malicious code automatically

    First seen

  2. Artifact

    Trivy 0.69.4-0.69.6 binaries and images; trivy-action below 0.35.0; setup-trivy below 0.2.6

  3. Actor

    TeamPCP (attribution: Wiz; basis: the malware labels itself 'TeamPCP Cloud stealer', plus a shared typosquat C2)

  4. Infrastructure

    • Typosquat C2 domain
    • Cloudflare quick tunnel
    • ICP canister fallback

    Last seen

Indicators

CSVJSON

All values are defanged (how to read them).

TypeValueCopy
domainscan[.]aquasecurtiy[.]org
ip45[.]148[.]10[.]212
domainplug-tab-protective-relay[.]trycloudflare[.]com
domaintdtqy-oyaaa-aaaae-af2dq-cai[.]raw[.]icp0[.]io

Confidence: Moderate

Strong evidence, not yet confirmed by our own analysis. See the confidence scale for what each level requires. The sources below are the evidence.

Sources

Notes

  • Tag counts differ by source (75 of 76 vs 76 of 77). No social-engineering lure; included as the root of the TeamPCP chain.
  • First seen is 19 Mar 2026 (about 17:43 UTC), when the first trivy-action and setup-trivy tags were moved, per GHSA-69fq-xp46-6x23. The earlier token theft (began late Feb 2026, disclosed 1 Mar) is a precursor and is not counted in this campaign's dates. Corrected from 1 Mar on 10 Nov 2026, before the page went public.
  • Status re-checked 10 Nov 2026: GitHub releases v0.69.4, v0.69.5 and v0.69.6 return 404, and the advisory is still published.

Corrections

No corrections.

See the corrections policy. Spotted an error? Tell us.