Attacker used 4,837 hijacked GitHub accounts to run a CI secret stealer in 1,806+ repositories
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 malware — built to take the secrets and cloud credentials reachable by a repository's continuous-integration (CI) workflows — ran in at least 1,806 repositories, where the attacker likely collected those credentials, then wiped the logs.
The attack pattern
Every attempt started the same way: a pull request titled `docs: dependency audit notes`, opened from a branch named `wfx-docs` to test whether the account could write to the repository. These test pull requests were pushed to 61,764 repositories; in some of them, the stealer followed. After pushing it, the attacker reverted the change within a minute and usually deleted the workflow run and its logs.
The practical consequences, per Aikido: wherever the stealer ran, **every secret and cloud role available to the repository's workflows should be treated as compromised**. And any account that opened one of the test pull requests is compromised, even if the stealer never ran. Of the test PRs, 10,431 were submitted via collaborator or organization access, and 92% were still open when Aikido checked. The Hacker News verified that new PRs with the same title were opened early today (between 05:04 and 05:38 UTC) from `wfx-docs` branches; it is not clear whether the stealer followed. The figures cover only the public repositories the company could see.
Signs to audit in your repositories
From Tuesday onward, in any repo you can write to, look for (Aikido's list via The Hacker News):
- Branches: `wfx-docs`, `chore/[a-z0-9]{8}` (short-lived), `ci-check-[0-9]{4}` - Pull request title: `docs: dependency audit notes` - Commit messages: `ci: refresh build cache` (adds ~1,500 lines to an existing workflow), `chore: add ci helper` (a `.ci-xxxxxx.sh` script plus a `postinstall` hook in `package.json`), `chore: add dependency audit workflow` (`.github/workflows/build-audit-xxxxxx.yml`), `ci: restore`, `ci: cleanup` - Stealer script SHA-256: `89695abb392d5cfd4972672961e644bb46baa98aa1ed7173c2a2816c762735cf` - Exfiltration via HTTP POST to: `194.150.166[.]244:8080/exfil` and `18.143.168[.]96:8080/exfil`
Careful: a repository can show no `wfx-loot` artifacts or `WFX-BEGIN` step summaries and still have lost data; a missing run number on the attacker's commit is the more reliable sign. Aikido also found that versions v1.0.278 and v1.0.280 of the Go module `github.com/onuragtas/docker-env` carry the stealer only in a GitHub Actions workflow file (Go builds never run workflow files); it still recommends removing those versions.
The GhostAction shadow
The accounts used this week overlap with those hit in GhostAction's October wave, when stolen GitHub accounts pushed secret-stealing workflows into repositories: accounts compromised in October were about 1,000 times more likely to be reused this week. In more than 100 repositories, the new stealer was added on top of October's workflow files. Still, Aikido does not attribute November to the same actor "at this stage" — infrastructure, tools and methods differ, and stolen credentials often end up with several attackers.
Closing
CI/CD is the highest-value attack surface in your stack: the secrets living in your pipelines can be worth half your cloud. The immediate action is threefold: audit repositories with write access from external accounts, rotate CI secrets, and search for the indicators above. Want to go deeper on pipeline security with real cases? Join us at X-Ops Conference.
--- **Primary source:** The Hacker News — "4,837 Hijacked GitHub Accounts Ran a CI Secret Stealer in 1,806+ Repositories, Then Wiped the Logs", 2026-11-12. https://thehackernews.com/2026/11/4837-hijacked-github-accounts-ran-ci.html (HTTP 200 verified 2026-11-12; Argos batch 1). **Cited within the source:** Aikido Security technical analysis (aikido.dev), The Hacker News' own verification. **Category:** Cybersecurity · **Topics:** GitHub, CI/CD, secrets, cloud credentials, Aikido Security, hijacked accounts. **Verification status:** figures and indicators taken from the verified primary article, which cites Aikido's technical analysis; active campaign at publication time.