Two actions have been disabled again for a second time after the repositories became accessible last week This article explores github staff violation. . Visiting either repository now displays the message: "Access to this repository has been restricted by GitHub Staff due to a violation of GitHub's terms of service.
The original compromise on May 18 occurred to run malicious code that harvested sensitive credentials from CI/CD pipelines and exfiltrated the details to an attacker-controlled server. The activity was later linked to the Mini Shai-Hulud cluster, which shares overlapping exfiltration domains ("t.m-kosche[. ]com") with the GitHub Actions workflows and npm packages from the @antv ecosystem. GMT+2.
There are still several workflows that use the two GitHub Actions, which could have led to severe software supply chain security risks without the threat actors needing to use a new exploit or set up new infrastructure. "Both actions automate issue and comment housekeeping, such as closing inactive issues, checking newly opened ones, or keeping a single bot comment up to date," Socket said. Rotate all exposed secrets.
"Most supply chain incidents feature something new: a newly published malicious version, a newly hijacked account, or a newly injected workflow," Zanki explained. No new code was published, and no configuration was altered." This incident highlights that a mutable tag can be compromised, contained, and then reactivated without altering your own workflow file.












