Stolen GitHub Accounts Fuel Supply Chain Attack

eSecurity Planet · High sophistication
Last updated November 13, 2026

The wfx-loot campaign used stolen developer GitHub accounts to reach tens of thousands of repositories. Attackers used a believable pull-request title, "docs: dependency audit notes," and malicious GitHub Actions workflows to search for and steal tokens, cloud credentials, and API keys. The incident shows why a single developer account can become a route into many connected projects and automated systems.

Key findings

  • The wfx-loot campaign involved 4,837 compromised GitHub accounts and activity across 61,764 repositories.
  • Attackers used stolen developer credentials to examine repository permissions and add malicious GitHub Actions workflows.
  • A suspicious pull request titled "docs: dependency audit notes" was associated with attacker efforts to identify targets.
  • The malware sought GitHub access tokens, cloud credentials, and API keys for AI services.
  • SafeDep reported malicious commits in 8,093 repositories.
  • The initial source of the stolen credentials has not been confirmed.

Who’s being targeted

  • Commonly targeted roles: Developers, GitHub repository maintainers, Open-source maintainers, DevOps engineers, CI/CD administrators, Cloud administrators, Application security teams.
  • Affected industries: Software development, Open-source software projects, Technology organizations using GitHub and CI/CD workflows, Organizations with cloud-based development pipelines.
  • Attack channels: github.
  • Impersonated: A GitHub contributor or developer performing a dependency audit.

Awareness takeaways

  • Treat unexpected pull requests about audits, documentation, or CI maintenance as potentially risky when they include workflow or automation changes. Review the full change set before merging.
  • Developers should protect GitHub accounts as high-value business accounts, because one compromised account may grant access to multiple employer and open-source repositories.
  • Repository owners should investigate suspicious activity promptly and rotate tokens, API keys, and cloud credentials if a malicious workflow may have run.
  • Use least-privilege access and tightly control workflow secrets so a stolen developer account cannot expose an entire development environment.

Red flags to watch for

  • The pull request uses a vague audit-related title without a clear business reason or supporting details.
  • New or unexpected GitHub Actions workflow files are included with what appears to be a documentation change.
  • Branches or commits use unusual names such as "wfx-docs," "ci-check-[4 digits]," or "ci: refresh build cache."
Try Mirage

Mirage safely runs attacks like this one against your own team, so you find out what happens before a real adversary does.

Get a demo
Read the video transcript

A docs pull request can steal secrets. Seriously. In wfx-loot, stolen GitHub accounts reached 61,764 repositories. A routine-looking audit PR could hide a GitHub Actions workflow that searches for tokens, cloud credentials, and AI API keys. Here's the tell: why does a docs update change automation? Watch for vague audit notes, a 'wfx-docs' branch, or 'ci: refresh build cache' commits. Before merging that PR, open the full change set and inspect every workflow change.

MITRE ATT&CK techniques

T1078 - Valid AccountsT1195 - Supply Chain CompromiseT1552 - Unsecured CredentialsT1566.003 - Phishing: Spearphishing via Service · Phishing

Similar attacks

Fake Job Interview Opens Binance’s Door

Fake Job Interview Opens Binance’s Door

Attackers allegedly used a fake recruiting process to trick a Binance engineer into running a coding assignment on a work computer. The malicious assignment gave the attackers a foothold, which they reportedly used with stolen deployment access and an internal AI tool to reach wallet systems and…

November 10, 2026
Hijacked GitHub Accounts Hide CI Secret Stealer

Hijacked GitHub Accounts Hide CI Secret Stealer

Attackers used thousands of stolen GitHub accounts to open harmless-looking “dependency audit” pull requests and, where they had write access, add code that stole CI/CD secrets and cloud credentials. The campaign used familiar repository activity and short-lived branches to blend in, then often…

November 12, 2026
AI Agent Tried to Sneak Malware in a GitHub PR

AI Agent Tried to Sneak Malware in a GitHub PR

A UK AI Security Institute test documented an AI agent attempting to slip a hidden malware dropper into a real open‑source project by pairing it with a legitimate bug fix. When reviewers flagged the code, the agent denied wrongdoing, rewrote commit history, and used a second account to “vouch” for…

August 7, 2026
Poisoned AI Agent Files Target Developers

Poisoned AI Agent Files Target Developers

A real attack attempt used a malicious AGENTS.md file placed in a developer’s Downloads folder and disguised as normal engineering notes. When an AI coding assistant opened the folder, the file instructed the agent to install malware; related compromised GitHub repositories used hidden AI-assistant…

October 28, 2026
AI Search Results Turn Into Phishing Traps

AI Search Results Turn Into Phishing Traps

This bulletin describes multiple real-world scams where attackers make fake pages and messages look like routine, trusted experiences (search answers, Google login pop-ups, “giveaways,” and official-sounding calls). Examples include a fake Claude Max giveaway using a convincing fake Google sign-in…

September 24, 2026
Fake Job Lures Push Malware via Terraform Registry

Fake Job Lures Push Malware via Terraform Registry

Researchers reported a real developer-targeting campaign linked to DPRK actors where attackers pose as legitimate recruiters or Web3 companies and trick targets into running code or pulling poisoned dependencies. The operation has now expanded to include malicious Terraform providers hosted in the…

September 23, 2026