Two GitHub Actions previously compromised in the Mini Shai-Hulud campaign were mistakenly re-enabled, posing renewed security risks. These actions, actions-cool/issues-helper and actions-cool/maintain-one-comment, were initially compromised on May 18. The GitHub security team had removed them to prevent malware distribution. However, from September 16 to September 25, these actions were reactivated without proper cleanup and still pointed to malicious code. This resulted in workflows that referenced these actions executing the old malicious payload.

The Mini Shai-Hulud attack in May had targeted the Node Package Manager index, affecting numerous packages and versions by injecting malware designed to steal developers’ tokens, credentials, and CI/CD secrets. Researchers from Socket discovered that the release tags for the two compromised actions resolved to commits containing the obfuscated payload, leading to continued exposure.

GitHub's dependency graph shows that approximately 15,000 repositories depend on 'issues-helper,' but not all were necessarily compromised. The actions affected those running frequently, as they are used for issue management tasks. On September 25, the actions were disabled again, causing workflows referencing them to fail and stopping the execution of the malicious payload.

Socket advises developers to search for and remove references to these actions or to pin them to a verified clean commit. They also recommend reviewing any workflow runs since September 16 and rotating any exposed secrets. This incident highlights the importance of thorough dependency management and monitoring for supply chain vulnerabilities.