A coordinated supply chain campaign used GitHub issues to target 61 public repositories, including major projects, in just 43 minutes.
- Threat actors targeted 61 public repositories in an automated campaign spanning less than an hour on September 1.
- A total of 74 different GitHub accounts with legitimate development histories were used, pointing to widespread account takeovers.
- High-profile projects including Google LangExtract, Trivy, Brave browser, and MLflow were among those targeted.
- Radware researchers Gabi Nakibly and Zvika Babo identified 83 total attacks, with 77 occurring in a 43-minute span.
Attackers launched a coordinated supply chain campaign by weaponizing GitHub issues against 61 public repositories, including Google LangExtract and MLflow, utilizing 74 compromised developer accounts to execute commands in CI/CD environments within a 43-minute window.
Open source supply chain security faced a novel test when automated actors weaponized standard collaboration features to target high-profile public codebases. According to Radware, threat actors launched at least 83 distinct attacks against 61 public repositories in a span of under an hour on September 1. The campaign leveraged 74 different GitHub accounts, many of which displayed legitimate development histories, indicating widespread account takeovers rather than freshly minted burner profiles. Projects caught in the rapid-fire sweep included Google LangExtract, Trivy, Brave browser, and MLflow, highlighting a deliberate focus on heavily depended-upon enterprise and developer tooling. This incident demonstrates that standard developer workflows like issues and pull requests are now primary attack vectors for remote code execution in continuous integration environments.
How are GitHub issues weaponized for CI/CD supply chain attacks?
Attackers weaponize GitHub issues by injecting malicious payloads designed to execute arbitrary commands inside automated continuous integration and continuous deployment pipelines. When a project's automation scripts automatically parse incoming issues, PR titles, or comments for triage or reporting, unvalidated inputs can trigger command execution. In this particular campaign, researchers observed 77 malicious items published within a compressed 43-minute window, followed by six more just two minutes later. This velocity points to scripted automation rather than manual entry, allowing threat actors to spray payloads across dozens of targets simultaneously before maintainers or automated trust monitors can flag the anomalous activity. The ultimate objective of this execution phase is typically credential harvesting, environment variable exfiltration, or access token theft, which then paves the way for direct code tampering and downstream distribution.
The compromised account network behind the rapid assault
Attribution data gathered by Radware threat hunters Gabi Nakibly and Zvika Babo indicates a single coordinated operator behind the 74 compromised accounts used in the sweep. Using accounts with established commit histories allows threat actors to bypass simple reputation filters and heuristic checks that typically block brand-new profiles from interacting with public projects. This tactic represents a significant evolution in software supply chain threats, shifting from poisoned package registries like npm or PyPI directly into the project management layer of software forges. Security teams must now treat issue trackers and comment sections with the same zero-trust rigor traditionally reserved for external software dependencies and binary packages.
“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, VP and Researcher at RadwareAssessing your exposure risk with the GitHub Pipeline Triage Framework
Engineering and security leaders must evaluate their repositories against automated threats using a structured methodology. To help teams systematically analyze and mitigate this emerging class of repository-level threats, we developed the GitHub Pipeline Triage Framework, a three-tier model designed to evaluate automation risk across public and private codebases.
- Tier 1: Input Sanitization Audit — Review all scripts that automatically parse issue bodies, labels, and comments, ensuring strict input validation before passing strings to shell environments.
- Tier 2: CI/CD Privilege Restriction — Audit GitHub Actions workflow permissions to ensure tokens generated during pull requests and issues operate with read-only access by default.
- Tier 3: Account Behavior Monitoring — Implement automated alerts for sudden bursts of issue creation from established contributors or foreign IP addresses.
What to watch next
Engineering and security teams should monitor several key indicators following this rapid supply chain campaign:
- GitHub's platform-level mitigations and policy updates regarding automated issue creation limits and anomalous account behavior.
- Adoption rates of read-by-default token permissions in complex open source CI/CD pipeline configurations.
- New detection signatures from threat intelligence vendors tracking compromised developer account networks across code hosting forges.
Frequently asked
What happened in the GitHub issues supply chain attack?
Attackers used 74 compromised GitHub accounts to publish malicious items across 61 public repositories within a 43-minute window, attempting to execute commands in CI/CD environments and steal credentials.
Which open source projects were targeted?
High-profile open source projects including Google LangExtract, Trivy, Brave browser, and MLflow were targeted during the coordinated supply chain campaign.
Who discovered the GitHub issues attack campaign?
Radware threat hunters, including VP and researcher Gabi Nakibly and researcher Zvika Babo, discovered and analyzed the supply chain campaign ahead of public disclosure.
What was the attackers' ultimate goal?
Researchers suspect the ultimate goal was to gain repository credentials and access tokens, enabling attackers to modify source code and push malicious changes downstream.
- github issues supply chain attack
- github public repo security incident
- radware github threat research
- github actions CI/CD supply chain attack
- compromised github accounts open source
- how do attackers use github issues for supply chain attacks
- what open source repos were targeted in github attack
- why are threat actors targeting github issue trackers
- how to protect CI/CD pipelines from issue injection