GitHub Actions re-enabled with Mini Shai-Hulud payload still active
Two third-party GitHub Actions previously compromised in the Mini Shai-Hulud supply-chain malware campaign were re-enabled by their maintainer in September 2026 without removing the malicious payload. These actions, named actions-cool/issues-helper and actions-cool/maintain-one-comment, remained accessible and continued to deliver malware to workflows referencing them for over a week. The malicious payload targets developer tokens, credentials, and CI/CD secrets. GitHub disabled these actions again on September 25, 2026. Developers are advised to remove or pin to clean commits and rotate secrets potentially exposed during this period.
AI Analysis
Technical Summary
In May 2026, the Mini Shai-Hulud campaign compromised 323 npm packages, including two GitHub Actions repositories: actions-cool/issues-helper and actions-cool/maintain-one-comment. These actions were removed by GitHub security to prevent malware distribution. However, starting September 16, 2026, the maintainer re-enabled these repositories without cleaning the malicious payload, causing workflows referencing these actions by version tags to resume downloading and executing the malware. The payload is obfuscated in the 'index.js' file and targets developer tokens, credentials, and CI/CD secrets. Approximately 15,000 repositories depend on 'issues-helper', though the exact number affected by mutable tags is unknown. GitHub disabled the actions again on September 25, 2026. Socket researchers recommend removing references or pinning to clean commits and rotating secrets.
Potential Impact
The re-enabled malicious GitHub Actions allowed workflows that referenced them by version tags to download and execute malware, potentially exposing developer tokens, credentials, and CI/CD secrets. This could lead to unauthorized access or compromise of development environments and continuous integration/deployment pipelines. The exposure lasted from September 16 to September 25, 2026. The exact number of affected repositories is unclear, but the dependency graph shows about 15,000 repositories depending on one of the affected actions. The incident could have led to widespread supply-chain compromise within affected development workflows.
Mitigation Recommendations
GitHub disabled the malicious actions again on September 25, 2026, preventing further execution of the payload. Developers should identify any workflows referencing actions-cool/issues-helper or actions-cool/maintain-one-comment, remove these references, or pin them to verified clean commits. Additionally, developers should review workflow runs between September 16 and September 25, 2026, and rotate any secrets or credentials accessible to those workflows to mitigate potential compromise. No further action is required from GitHub users beyond these steps as the malicious actions are currently disabled.
GitHub Actions re-enabled with Mini Shai-Hulud payload still active
Description
Two third-party GitHub Actions previously compromised in the Mini Shai-Hulud supply-chain malware campaign were re-enabled by their maintainer in September 2026 without removing the malicious payload. These actions, named actions-cool/issues-helper and actions-cool/maintain-one-comment, remained accessible and continued to deliver malware to workflows referencing them for over a week. The malicious payload targets developer tokens, credentials, and CI/CD secrets. GitHub disabled these actions again on September 25, 2026. Developers are advised to remove or pin to clean commits and rotate secrets potentially exposed during this period.
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
In May 2026, the Mini Shai-Hulud campaign compromised 323 npm packages, including two GitHub Actions repositories: actions-cool/issues-helper and actions-cool/maintain-one-comment. These actions were removed by GitHub security to prevent malware distribution. However, starting September 16, 2026, the maintainer re-enabled these repositories without cleaning the malicious payload, causing workflows referencing these actions by version tags to resume downloading and executing the malware. The payload is obfuscated in the 'index.js' file and targets developer tokens, credentials, and CI/CD secrets. Approximately 15,000 repositories depend on 'issues-helper', though the exact number affected by mutable tags is unknown. GitHub disabled the actions again on September 25, 2026. Socket researchers recommend removing references or pinning to clean commits and rotating secrets.
Potential Impact
The re-enabled malicious GitHub Actions allowed workflows that referenced them by version tags to download and execute malware, potentially exposing developer tokens, credentials, and CI/CD secrets. This could lead to unauthorized access or compromise of development environments and continuous integration/deployment pipelines. The exposure lasted from September 16 to September 25, 2026. The exact number of affected repositories is unclear, but the dependency graph shows about 15,000 repositories depending on one of the affected actions. The incident could have led to widespread supply-chain compromise within affected development workflows.
Defensive Guidance
GitHub disabled the malicious actions again on September 25, 2026, preventing further execution of the payload. Developers should identify any workflows referencing actions-cool/issues-helper or actions-cool/maintain-one-comment, remove these references, or pin them to verified clean commits. Additionally, developers should review workflow runs between September 16 and September 25, 2026, and rotate any secrets or credentials accessible to those workflows to mitigate potential compromise. No further action is required from GitHub users beyond these steps as the malicious actions are currently disabled.
Technical Details
- Classification
- {"confidence":0.71,"severitySource":"default","classifier":"rss-v2"}
- Article Source
- {"url":"https://www.bleepingcomputer.com/news/security/github-actions-re-enabled-with-mini-shai-hulud-payload-still-active/","fetched":true,"fetchedAt":"2026-09-26T14:32:50.928Z","wordCount":687}
Threat ID: 6ab7d792f7a7c541066050f0
Added to database: 09/26/2026, 14:32:50 UTC
Last enriched: 09/26/2026, 14:32:56 UTC
Last updated: 09/27/2026, 02:21:06 UTC
Views: 14
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
External Links
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.