Disabled GitHub Actions Came Back With Malware Still Inside

Two disabled actions-cool GitHub Actions came back online Sept. 16, again serving Mini Shai-Hulud malware through unchanged release tags.

@sharedot

Disabled GitHub Actions Came Back With Malware Still Inside

By @sharedot · · 6 pages

  • Programming
  • Github Actions
  • Supply Chain Security
  • Ci Cd

Two disabled actions-cool GitHub Actions came back online Sept. 16, again serving Mini Shai-Hulud malware through unchanged release tags.

What happened

GitHub has disabled two actions-cool repositories — `actions-cool/issues-helper` and `actions-cool/maintain-one-comment` — for a second time after they became accessible again on September 16, 2026, per The Hacker News. Both now show a terms-of-service violation notice.

The actions were compromised on May 18, 2026, during the Mini Shai-Hulud campaign, with malicious code that harvested CI/CD credentials and exfiltrated them to an attacker-controlled server. Socket researcher Karlo Zanki reported the repositories came back online between 11:09 a.m. and 6:16 p.m.

GMT+2 without their release tags being cleaned up, so tags still pointed to the malicious May 18 content.

Why the reversal is surprising

Most supply chain incidents involve something new — a malicious release, a hijacked account, or an injected workflow. This one did not, as Zanki noted: no new code was published and no configuration was changed.

All it took for the threat to reactivate was for the repositories to become downloadable again.

According to Socket, workflows calling these actions typically run on daily schedules or on new issues and pull requests, meaning most affected repositories likely executed the payload within a day of re-enablement, with no action required from the attackers.

GitHub has not explained why access returned.

The evidence trail

The activity was linked to the Mini Shai-Hulud cluster through overlaps in the exfiltration domain "t.m-kosche[.]com" used in both the GitHub Actions workflows and npm packages from the @antv ecosystem — a connection Philipp Burckhardt, head of threat intelligence at Socket, described to The Hacker News as the same cluster, not a separate npm-only incident. news.lavx.hu reports the repositories became accessible between 11:09 a.m. and 6:16 p.m.

GMT+2 on September 16 while still carrying release tags pointing to the malicious commits. Workflows that pinned either action to a full commit SHA from before May 18 were not affected.

What teams should do now

Both sources recommend the same remediation steps: locate every reference to `actions-cool/issues-helper` and `actions-cool/maintain-one-comment`, treat `actions-cool/issues-helper@v2.2.1` as affected, remove the actions or pin them to a known-clean SHA predating May 18, 2026, and rotate all exposed secrets including repository secrets, cloud tokens and package-registry keys. news.lavx.hu adds that teams should review workflow run history for newly successful runs after a period of Set up job failures, audit for unexpected commits after September 16, and preserve workflow logs before rotating credentials.

The repositories remain disabled as of September 25, but teams should treat the access window as a possible compromise period even if their workflow files never changed.

Sources

  1. thehackernews.com › Compromised GitHub Actions Came Back Online and Resumed Executing Mini Shai-Hulud Malware
  2. news.lavx.hu › Compromised GitHub Actions returned with Mini Shai-Hulud malware still in place

More on Programming