Back in May, the Mini Shai-Hulud campaign poisoned 323 npm packages and two GitHub Actions — `actions-cool/issues-helper` and `actions-cool/maintain-one-comment`. On September 16 their maintainer re-enabled the repositories, but nobody scrubbed the release tags first. They still point at the malicious commit from May 18, so every workflow pinning either action by version tag quietly resumed downloading and running credential-stealing code on its next run. GitHub disabled them a second time on September 25. This is the failure mode nobody plans for: not a fresh compromise, but an old one that never really got cleaned up. The payload goes after developer tokens, cloud credentials, and CI/CD secrets. If your pipelines referenced either action in the past week, pin to a known-clean commit — or drop it — and rotate anything those runners could see.