{
  "id": 17058545,
  "title": "Attackers turn GitHub issues into supply chain campaign against 61 public repos in less than an hour",
  "url": "https://urgent.news/2026/10/29/attackers-turn-github-issues-into-supply-chain-campaign-against-61-17058545",
  "topic": "tech",
  "section": "Tech",
  "published": "2026-10-29T12:00:00.000Z",
  "source": {
    "name": "The Register",
    "slug": "the-register",
    "url": "https://www.theregister.com/security/2026/10/29/attackers-turn-github-issues-into-supply-chain-campaign-against-61-public-repos-in-less-than-an-hour/5306153"
  },
  "original_language": "en",
  "account": "Within a single hour, attackers launched a coordinated campaign against 61 public GitHub repositories, exploiting the platform's issue and pull request systems to inject malicious commands. The majority of these attacks took place within a 43-minute window on September 1, with 74 different compromised GitHub accounts used to post the malicious payloads. Researchers at Radware suspect a single individual is behind the campaign, which aims to gain control over repository credentials, enabling the attacker to modify code and push changes to other users. The attack chain involves posting an issue, pull request, or comment containing hidden malicious commands, which can trigger a vulnerable workflow and execute the commands directly within the automation environment. The researchers identified 83 GitHub items with verified payloads across 61 repositories, including widely used open source projects such as Google LangExtract, Trivy, Brave browser, and MLflow. While the researchers have disclosed their findings to the affected projects' maintainers, they cannot confirm if all repositories were fixed. The researchers advise adopting least-privilege access to CI/CD workflows, separating external-triggered workflows from elevated permission jobs, and treating external content as untrusted to mitigate the risk of such supply chain attacks.",
  "summary": "'The workflow automatically is triggered within a second, and if the workflow is indeed vulnerable, then the attack is executed successfully'",
  "key_points": [],
  "editors_take": null,
  "illustration": null,
  "coverage": {
    "outlets": 1,
    "also_reported_by": []
  },
  "ai_generated": true,
  "disclaimer": "Summaries, key points and the editor’s take are written by software from other outlets’ reporting and may contain errors — always check the linked original."
}