Trusence Technology, daily
Last updated 26 September 2026 Türkçe
← All stories
Security

GitHub Actions briefly reactivated with old Mini Shai-Hulud payload

Two previously abused actions were live again for nine days, leaving workflows exposed until GitHub disabled them once more.

The maintainer of two GitHub Actions tied to the May Mini Shai-Hulud campaign restored them on September 16, even though their release tags still led to the earlier malicious code; workflows using those tags could run it again. Socket found the payload in obfuscated form in index.js, and GitHub disabled both actions again on September 25, causing affected workflows to fail instead of execute the code. The May campaign infected 323 npm packages and 639 package versions with malware targeting developers’ tokens, credentials and CI/CD secrets. GitHub’s dependency graph lists about 15,000 repositories using issues-helper, but Socket has not determined how many dependents used mutable tags, and that count does not show how many were compromised. Socket advises teams to remove the actions or pin a verified clean commit, review runs from September 16 onward and rotate secrets available to workflows that ran an affected tag.

Why it matters

For any project that relied on these actions via their release tags, workflows triggered between September 16 and 25 may have executed code that included an obfuscated payload, rather than the expected automation. That risk sits on top of a May campaign that already planted malware in hundreds of npm packages to go after developer credentials and CI/CD secrets. Teams using the affected actions now face extra cleanup work to secure tokens, audit runs and decide whether to keep or replace them.

Sources

  • BleepingComputer