On March 19, an attacker published Trivy v0.69.4 with stolen credentials. The same evening, they moved 76 of the 77 tags of the trivy-action action to a secret stealer. The scanner meant to protect pipelines stole their secrets for twelve hours. After that, I counted the action references in my own repositories: 689, and zero pinned to a SHA.
TL;DR : your security scanner runs inside your CI, with the job's secrets. It is a dependency, and the Trivy attack proved it. Pin every action to a full commit SHA, every image to its digest, and ban latest . Keep Dependabot or Renovate to bump the pins. My audit: 689 action references, 0 by SHA, 170 on @main .
Figures, SHAs and digests as of November 3, 2026.…