Compromised GitHub Actions Database¶
ActionScope ships a curated database of GitHub Actions with documented supply-chain compromises. This page is the canonical browsable view of every entry — each one has its own permalink, so you can deep-link from advisories, incident-response runbooks, or post-mortems.
To check whether your repository uses any of these actions:
pip install actionscope
actionscope scan .
Mutable-tag references to a compromised action (e.g. @v3 of
actions-cool/issues-helper) produce a CRITICAL finding. Full-SHA pins
to an action that has been compromised but where the specific SHA is not in
the published affected-refs list produce a HIGH finding so a human can
confirm whether the pinned commit predates the compromise.
For background on how detection works, see Compromised Actions detector.
actions-cool/issues-helper¶
- Action:
actions-cool/issues-helper - First compromised:
2026-05-18T19:10:24Z - Status: ⛔ Compromised — actively malicious as of the published advisory
- Affected references:
v3,v3.8.0,v3.7.6,v3.7.5,v3.7.4,v3.7.3,v3.7.2,v3.7.1,v3.7.0,v3.6.3,v3.6.2,v3.6.1,v3.6.0,v3.5.2,v3.5.1,v3.5.0 - Advisory: https://www.stepsecurity.io/blog/actions-cool-issues-helper-github-action-compromised-all-tags-point-to-imposter-commit-that-exfiltrates-ci-cd-credentials
All version tags redirected to imposter commit. Malicious code reads Runner.Worker process memory to exfiltrate CI/CD secrets. Exfiltration domain: t.m-kosche[.]com.
Are you affected?¶
# Scan your repo for *this* compromised action:
actionscope scan . | grep -A 5 'actions-cool/issues-helper'
Remediation¶
- Remove the action from your workflow, OR
- Pin to a verified pre-compromise SHA if one exists (consult the advisory linked above).
- Rotate any credentials the workflow had access to during the compromised window. Treat the compromise window as a credential disclosure.
actions-cool/maintain-one-comment¶
- Action:
actions-cool/maintain-one-comment - First compromised:
2026-05-18T19:10:24Z - Status: ⛔ Compromised — actively malicious as of the published advisory
- Affected references: All tags treated as ambiguous — SHA pins must be individually verified.
- Advisory: https://www.stepsecurity.io/blog/actions-cool-issues-helper-github-action-compromised-all-tags-point-to-imposter-commit-that-exfiltrates-ci-cd-credentials
All 15 version tags redirected to imposter commit. Same exfiltration technique and domain as issues-helper. Coordinated attack.
Are you affected?¶
# Scan your repo for *this* compromised action:
actionscope scan . | grep -A 5 'actions-cool/maintain-one-comment'
Remediation¶
- Remove the action from your workflow, OR
- Pin to a verified pre-compromise SHA if one exists (consult the advisory linked above).
- Rotate any credentials the workflow had access to during the compromised window. Treat the compromise window as a credential disclosure.
aquasecurity/trivy-action¶
- Action:
aquasecurity/trivy-action - First compromised:
2026-03-19T00:00:00Z - Status: 📜 Historical — past compromise, included for repos still pinned to a pre-fix tag
- Affected references: All tags treated as ambiguous — SHA pins must be individually verified.
- Advisory: https://github.com/aquasecurity/trivy/security/advisories/GHSA-69fq-xp46-6x23
Official trivy-action and setup-trivy GitHub Actions compromised alongside Trivy scanner binary. Injected credential-stealing malware.
Are you affected?¶
# Scan your repo for *this* compromised action:
actionscope scan . | grep -A 5 'aquasecurity/trivy-action'
Remediation¶
- Remove the action from your workflow, OR
- Pin to a verified pre-compromise SHA if one exists (consult the advisory linked above).
- Rotate any credentials the workflow had access to during the compromised window. Treat the compromise window as a credential disclosure.
tj-actions/changed-files¶
- Action:
tj-actions/changed-files - First compromised:
2025-03-19T00:00:00Z - Status: 📜 Historical — past compromise, included for repos still pinned to a pre-fix tag
- Affected references: All tags treated as ambiguous — SHA pins must be individually verified.
- Advisory: https://github.com/advisories/GHSA-mrrh-fwg8-r2c3
All version tags redirected to malicious commit. Exfiltrated secrets via workflow logs. Affected 23,000+ repositories.
Are you affected?¶
# Scan your repo for *this* compromised action:
actionscope scan . | grep -A 5 'tj-actions/changed-files'
Remediation¶
- Remove the action from your workflow, OR
- Pin to a verified pre-compromise SHA if one exists (consult the advisory linked above).
- Rotate any credentials the workflow had access to during the compromised window. Treat the compromise window as a credential disclosure.
Reporting a new compromise¶
Found a compromised action that is not on this list? Please open an issue using the report template so we can add it.