Threat Intelligence

Hijacked GitHub Accounts Used to Plant Secret Stealer in Thousands of Code Repositories

The Hacker News · 12 Nov 2026
Key Takeaway Check your GitHub repositories for pull requests titled "docs: dependency audit notes" from a wfx-docs branch, and if you find one, rotate every secret and cloud credential your workflows can reach and enable 2FA on the accounts involved.

Starting Tuesday, an attacker used stolen credentials for 4,837 GitHub accounts to plant a secret stealer in repositories those accounts could write to, according to Aikido Security. The tool is built to take the secrets and cloud credentials that a repository's automated build workflows can reach. Aikido says it ran in at least 1,806 repositories, where the attacker has likely collected those credentials. The attacker first opened a test pull request titled "docs: dependency audit notes" from a branch named wfx-docs, in 61,764 repositories, to check whether the account could write to them.

SafeDep, a software supply chain security firm, counted 8,093 repositories that received malicious commits between 12:46 UTC on Tuesday and 04:36 UTC today. Its search covered only the default branches of public repositories, so the true total is higher. In 7,309 of them the stealer was added to an existing workflow. In 771 it came as an npm postinstall hook, which also runs on a developer's machine during npm install. The attacker usually reverted the change within minutes and deleted logs, so the activity is easy to miss. More matching pull requests appeared early today, but it is not clear whether the stealer followed. The source does not explain how the credentials were obtained.

Where the stealer ran, every secret and cloud role available to the workflows should be treated as compromised. Aikido says any account that opened one of the test pull requests is compromised, even if the stealer never ran. SafeDep advises owners to revoke the commit author's tokens, OAuth app grants, SSH keys and sessions, turn on 2FA, and rotate every secret the repository can read. Anyone who ran npm install on an affected commit should treat that machine as compromised and rotate its keys.

Answering to more than one framework? Run them as one security and AI governance programme ->

Summarised by CISO AI from The Hacker News, written with Claude Sonnet 5.5. We link back to every original so you can read it yourself.