conv.

All stories
SecurityQuiet 12d · day 14

Radware finds coordinated GitHub supply chain attack across 61 repos in 43 minutes

Researchers identified 83 attacks on popular open-source projects using hidden commands in issues to steal CI/CD credentials.

newest coverage 12d agosummary written 13d ago6 pieces10 likes & upvotes2 comments NewswiresMastodonHacker NewsReddit

What to know

  • Coordinated attack on 61 public GitHub repositories including Google LangExtract, Trivy, Brave, and MLflow using 74 compromised accounts within a 43-minute window on September 1.
  • Attack uses hidden commands in HTML comments within issues/pull requests to trigger automated workflows and exfiltrate CI/CD credentials and environment variables.
  • Researchers found evidence of successful command execution in two cases but cannot yet confirm whether attacker obtained write access or modified source code.
  • Single attacker suspected; attack is low-barrier — any GitHub user can attempt it — making supply-chain compromise a persistent risk for open-source projects.

“Considering that dozens of accounts posted the same type of payload, on the same day, within a narrow time window, and to the same infrastructure, it is reasonable to assess that the activity was coordinated”

Radware research team, Security researchers · The Register ↗

Gabi Nakibly Radware VP and researcherZvika Babo Radware researcherRadware threat hunters Security research team

Radware finds coordinated GitHub supply chain attack across 61 repos in 43 minutes
theregister.com

How it unfolded 1 development · click the chart to see its coverage articlesposts

Peak 4 pieces in 3h at Oct 29, 10 AM; 6 pieces over 14 days (1 article · 5 posts) Oct 29, 7 AM — 1 piece · 1 article — Newswires 1Oct 29, 10 AM — 4 pieces · 4 posts — Hacker News 2, Mastodon 2Oct 29, 1 PM — quietOct 29, 4 PM — quietOct 29, 7 PM — quietOct 29, 10 PM — quietOct 30, 1 AM — quietOct 30, 4 AM — quietOct 30, 7 AM — quietOct 30, 10 AM — quietOct 30, 1 PM — quietOct 30, 4 PM — 1 piece · 1 post — Reddit 1Oct 30, 7 PM — quietOct 30, 10 PM — quietOct 31, 1 AM — quietOct 31, 4 AM — quietOct 31, 7 AM — quietOct 31, 10 AM — quietOct 31, 1 PM — quietOct 31, 4 PM — quietOct 31, 7 PM — quietOct 31, 10 PM — quietNov 1, 1 AM — quietNov 1, 3 AM — quietNov 1, 6 AM — quietNov 1, 9 AM — quietNov 1, 12 PM — quietNov 1, 3 PM — quietNov 1, 6 PM — quietNov 1, 9 PM — quietNov 2, 12 AM — quietNov 2, 3 AM — quietNov 2, 6 AM — quietNov 2, 9 AM — quietNov 2, 12 PM — quietNov 2, 3 PM — quietNov 2, 6 PM — quietNov 2, 9 PM — quietNov 3, 12 AM — quietNov 3, 3 AM — quietNov 3, 6 AM — quietNov 3, 9 AM — quietNov 3, 12 PM — quietNov 3, 3 PM — quietNov 3, 6 PM — quietNov 3, 9 PM — quietNov 4, 12 AM — quietNov 4, 3 AM — quietNov 4, 6 AM — quietNov 4, 9 AM — quietNov 4, 12 PM — quietNov 4, 3 PM — quietNov 4, 6 PM — quietNov 4, 9 PM — quietNov 5, 12 AM — quietNov 5, 3 AM — quietNov 5, 6 AM — quietNov 5, 9 AM — quietNov 5, 12 PM — quietNov 5, 3 PM — quietNov 5, 6 PM — quietNov 5, 9 PM — quietNov 6, 12 AM — quietNov 6, 3 AM — quietNov 6, 6 AM — quietNov 6, 9 AM — quietNov 6, 12 PM — quietNov 6, 3 PM — quietNov 6, 6 PM — quietNov 6, 9 PM — quietNov 7, 12 AM — quietNov 7, 3 AM — quietNov 7, 6 AM — quietNov 7, 9 AM — quietNov 7, 12 PM — quietNov 7, 3 PM — quietNov 7, 6 PM — quietNov 7, 9 PM — quietNov 8, 12 AM — quietNov 8, 3 AM — quietNov 8, 6 AM — quietNov 8, 9 AM — quietNov 8, 12 PM — quietNov 8, 3 PM — quietNov 8, 6 PM — quietNov 8, 9 PM — quietNov 9, 12 AM — quietNov 9, 3 AM — quietNov 9, 6 AM — quietNov 9, 9 AM — quietNov 9, 12 PM — quietNov 9, 3 PM — quietNov 9, 6 PM — quietNov 9, 9 PM — quietYesterday, 12 AM — quietYesterday, 3 AM — quietYesterday, 6 AM — quietYesterday, 9 AM — quietYesterday, 12 PM — quietYesterday, 3 PM — quietYesterday, 6 PM — quietYesterday, 9 PM — quietToday, 12 AM — quietToday, 3 AM — quietToday, 6 AM — quietToday, 9 AM — quietToday, 12 PM — quietToday, 3 PM — quietToday, 6 PM — quiet 1
Oct 30Oct 31Nov 1Nov 2Nov 3Nov 4Nov 5Nov 6Nov 7Nov 8Nov 9now · 8:58 PM ET
  1. 1

    Radware publishes exclusive findings on campaign mechanics and suspected single attacker

    Researchers conclude a single individual coordinated the attacks using 74 mostly compromised accounts with legitimate development histories. They found evidence the malicious commands executed in two cases, exfiltrating environment variables to attacker-controlled servers, but cannot confirm write access or code modifications.

    “Our guess is that the final aim was a supply-chain attack in which the attacker gains credentials for the repo, and then he has the power to change the contents – the code – as he wishes…”
    — Gabi Nakibly
    1. 1 outlet Attackers turn GitHub issues into supply chain campaign against 61 public repos in less than an hour

      first by The Register, 13d ago

    • AAKL@infosec.exchange

      New. Radware: Inside a GitHub Supply Chain Attack Campaign: Command Injection, Attempts to Exfiltrate CI/CD Data, and Evidence of Execution https://www. radware.com/blog/inside-a-gith ub-supply-chain-attack-campaign/ @ ifin More: The Register: Attackers turn GitHub issues into supply chain campaign against 61 public repos in less than an hour…

      AAKL@infosec.exchangeMastodon13d agoview on Mastodon ↗
  2. background

    Radware verifies 83 attacks targeting AI frameworks, security tools, and databases — As of October 13, researchers confirmed 83 GitHub items with verified payload across 61 repositories spanning AI frameworks, security tools, development infrastructure, and databases including Google LangExtract, Trivy, Brave browser, and MLflow.

  3. background

    Attack uses hidden commands and CI/CD workflow triggers — Attacker publishes issues, pull requests, or comments containing malicious commands hidden in HTML comments, invisible in rendered pages. GitHub events automatically trigger workflows within seconds if repository is configured to respond, executing attacker-controlled payload injected into shell code.

  4. background

    Attacker launches coordinated GitHub supply chain campaign — Malicious items posted to 61 public repositories using 74 GitHub accounts. Most (77 of 83) attacks published within a 43-minute window, with six more following within two minutes.