GhostAction Hacks 1,900 GitHub Accounts: 30,000 Repos Targeted in Massive Secret-Theft Wave




A credential-theft campaign known as GhostAction has just pulled off one of the largest attacks on developer infrastructure ever recorded. According to cybersecurity firm GitGuardian, the campaign spiked on October 8 and 9, 2026, targeting more than 30,000 repositories across roughly 3,000 users and organizations — after compromising the GitHub accounts of about 1,900 users. If you write code for a living, this one deserves your attention.

The scale of the attack

The numbers are striking. As reported by The Hacker News, GitGuardian researchers Gaetan Ferry and Guillaume Valadon said the spike "resulted from compromising the GitHub accounts of about 1,900 users. It attempted to extract 3,174 secrets from public repositories' CI."

For context, that means a single two-day wave hit tens of thousands of code repositories, trying to siphon off more than three thousand sensitive credentials from their continuous integration (CI) environments. This is not a theoretical research exercise — it is an active, evolving campaign against the software supply chain.

How GhostAction works

GhostAction was first discovered in September 2025, and its method is brutally simple. As The Hacker News explains, attackers compromise legitimate developer accounts, then use them to inject malicious GitHub Actions automation workflows into software repositories.

The attack chain typically looks like this:

  1. Steal the keys: Attackers gain write access to repositories using stolen Personal Access Tokens (PATs) or credentials harvested from infostealer malware logs and leaked data dumps.
  2. Plant the workflow: Using the hijacked account, they push a malicious workflow file disguised under trustworthy names such as "Security Audit" (security-audit.yml) or "GitHub Actions Security" — names designed to look like routine safety checks.
  3. Harvest the secrets: When the workflow runs in the victim's CI environment, it scans for and exfiltrates secrets: CI/CD credentials, cloud access keys, package registry tokens (npm, PyPI, DockerHub), and AI provider API keys.

The disguise is the clever part. A file named "security-audit.yml" looks like something a diligent maintainer would add, which is exactly why it can sit unnoticed while quietly draining credentials.

What's new in this wave

GitGuardian has been tracking a fresh wave of GhostAction since August 31, 2026, and it is getting smarter. "This new wave seems more experimental and manual than previous ones, with the payload evolving over time," the firm said. Compared with the original payload, the new version added a feature that scans the repository's git history for hidden secrets — meaning even credentials removed from current code could still be exposed.

Later variants went further, collecting nearby context to help pair AWS key IDs with their matching secret access keys. New waves were also recorded on October 10 and 12 — but there is one piece of good news: GitHub began blocking the malicious workflow on October 9, so those later waves could not extract secrets.

How developers can protect themselves

No single fix stops campaigns like GhostAction, but several practical steps sharply reduce your exposure:

  • Turn on two-factor authentication (2FA) on your GitHub account and, where possible, use passkeys or hardware keys instead of SMS codes.
  • Rotate your Personal Access Tokens and move to fine-grained tokens with the minimum permissions each task needs — a token that can only read one repo cannot push a malicious workflow to fifty.
  • Audit your workflow files regularly. Look for unfamiliar additions under .github/workflows, especially anything named "security-audit.yml" or similar that you did not author. A sudden new workflow on a push trigger is a red flag.
  • Scan for leaked secrets in both current code and git history, and rotate any credential that was ever committed — attackers now mine history, not just HEAD.
  • Limit third-party Actions to pinned, verified versions, and require reviews before workflow changes merge.

The bigger picture

GhostAction is a reminder that the modern software supply chain runs on trust — trust in maintainer accounts, in automation, and in the secrets sitting inside CI pipelines. When attackers compromise roughly 1,900 accounts at once, that trust becomes the attack surface. Some victims in this wave had been hit before, which GitGuardian says may let attackers exploit secrets that were never rotated.

The takeaway for every developer and team: rotate your tokens, lock down your workflows, and treat every new "security audit" file with healthy suspicion.

Disclaimer: Attack details are based on reports published today; verify current guidance from GitGuardian and GitHub's official security advisories.



 

Post a Comment

Previous Post Next Post