A pull request called 'docs: dependency audit notes' hit 61,764 repos. It was a probe.
By Lior AharonovFounder, 7IT Solutions ·
What happened
From about 12:45 UTC on 10 November, a campaign Aikido Security calls wfx-loot used 4,837 compromised GitHub accounts to open probe pull requests against 61,764 repositories, BleepingComputer reported on 12 November. Where access allowed, a script planted in Actions workflows or npm install hooks stole secrets from at least 1,835 targets. The attacker then reverted the changes and deleted the workflow runs.
Why it matters
Your CI holds the keys to everything: the AWS role, the npm publish token, the OpenAI key. The script can trade GitHub OIDC tokens for AWS, Azure and Google Cloud sessions, and the evidence was wiped in under a minute.
What to do
Search your repositories for a branch named wfx-docs, that pull request title and gaps in workflow run numbers. If the payload ran, rotate every secret and cloud role those workflows could reach.

My take
Lior Aharonov
Founder, 7IT Solutions
A deleted workflow run is not a clean workflow run. The gaps in the numbering are the fingerprints.
I've seen this before
I've seen this before: in March 2025 the tj-actions/changed-files GitHub Action was compromised and exposed secrets such as access keys, GitHub tokens and npm tokens. CISA said to treat them as compromised and rotate them. Same prize, same place: the CI pipeline.
CISA: Supply Chain Compromise of Third-Party tj-actions/changed-files (CVE-2025-30066) cisa.gov
Sources
| BleepingComputer: Hackers compromise 4,800 GitHub accounts to steal cloud credentials | bleepingcomputer.com |
Researched with AI tools; every fact is checked against the linked sources.