tj-actions/changed-files: GitHub Action Leaked CI Secrets
The malicious tags were cleaned up within about a day in March 2025; today the job is confirming you rotated any secret that a March 14-15, 2025 workflow run could have printed, and that you pin Actions by SHA.
Must act: Anyone whose workflows ran tj-actions/changed-files on March 14-15, 2025, or a reviewdog action on March 11, 2025, especially in public repositories, and who never rotated the secrets those jobs could read.
Can relax: Teams that never used these Actions, or that already audited those runs, deleted leaking logs and rotated secrets in March 2025.
- Search all repositories for uses of tj-actions/changed-files and reviewdog/action-* (code search plus a grep of .github/workflows).
- For each run on March 14-15, 2025 (tj-actions) or March 11, 2025 (reviewdog), open the logs and look for double base64-encoded blobs in the changed-files step.
- Rotate every secret those jobs could read and delete the leaking workflow run logs.