Hijacked GitHub accounts pushed wfx-loot CI secret stealer to thousands of repositories

· CyberSecurity

TLDR

  • Aikido counts 4,837 accounts and 61,764 probed repositories; GitGuardian counts 17,715 repositories with payload patches in its dataset.111
  • Fly.io says tokens exposed in public .git/config files were used; revocation of its app's tokens stopped partway, per GitHub support.10
  • GitGuardian says GitHub held workflow-file payloads, but an npm install hook ran in repositories' existing workflows.11

Aikido Security reports that, in a mass wave starting on 10 November, a threat actor used stolen GitHub credentials to probe tens of thousands of repositories and push a malicious workflow payload into thousands of them, where it steals GitHub Actions secrets and cloud credentials.1 Aikido tracks the campaign as wfx-loot and puts the start of that wave at about 12:45 UTC on 10 November.1 For each repository a stolen token could write to, the attacker first opened a pull request titled "docs: dependency audit notes" from a branch named wfx-docs to confirm write access, then pushed a shell script of about 1,500 lines, and then reverted the change and deleted the workflow run and its logs, usually within a minute, though The Hacker News says a second analysis found some changes left in place for longer.12 Aikido says 10,431 of the probe pull requests went into repositories the account does not own, reached through collaborator or organisation access, and that 92 per cent were still open.1 SecurityWeek reports that StepSecurity said the attacker does not exploit a bug in GitHub Actions and instead relies on valid tokens belonging to developer and bot accounts.4

Aikido counts 4,837 accounts and 61,764 probed repositories, and SecurityWeek describes roughly 4,800 accounts and more than 60,000 repositories.14 On repositories where the payload ran, Aikido's body text says at least 1,806 while its summary list says at least 1,835; The Hacker News gives 1,806 and BleepingComputer gives 1,835.123 SafeDep separately counted 8,093 public repositories that received malicious commits between 12:46 UTC on 10 November and 04:36 UTC on 12 November, 7,309 of them through an existing workflow, 771 through an npm postinstall hook and 16 through a new workflow file.6 The Hacker News says that figure covers every repository that received malicious commits, not only those where the stealer ran, and that the true total is higher because the search covered only default branches of public repositories.2 Endor Labs, in an update at 21:35 UTC on 12 November, counted 8,926 repositories with payload evidence.7 OX Security reports more than 66,200 probe pull requests, up from the 61,764 repositories reported on 11 November, and StepSecurity counted more than 63,000 as of 07:40 UTC on 12 November.85

The script collects Actions secrets and variables, the workflow's GITHUB_TOKEN, cloud credential files and AI service keys, and Aikido says it exchanges GitHub OIDC tokens for AWS, GCP and Azure sessions.1 Aikido says it also rewrites an AWS role's trust policy to open it to any AWS account and adds Azure federated identity credentials named wfx-ci, steps it describes as designed to outlast credential rotation.1 StepSecurity reports that Telegram first appears in its samples at 01:10 UTC on 12 November and that from about 05:30 UTC new copies send stolen data only to a Telegram chat, so blocking the published IP addresses no longer stops it.5 OX Security reports the same switch around 05:30 UTC.8 The payload reached a Packagist package and a Go module through what Aikido describes as automated publishing triggers, though SafeDep found the Packagist tag was not produced by a GitHub Actions run; Aikido says the Go tags carry it only in a workflow file, which Go builds never run.16 SafeDep and OX Security also list a further tag of the Go module and a gocurl pseudo-version.68 BleepingComputer reports that researchers believe the primary objective was CI secrets, with the package releases a byproduct, and that some compromised accounts belonged to Fortune 100 organisations, the US General Services Administration, the French government, Nextcloud and WebdriverIO, though the other cited sources do not confirm the Fortune 100, GSA or French government entries.3 StepSecurity says one bot account pushed 56 commits across 28 WebdriverIO repositories and that no WebdriverIO package release was affected.5

How the tokens were obtained is not established. The Hacker News says Aikido's technical analysis does not explain how the attacker obtained the credentials, and Semgrep says researchers have not established where every token came from.29 Endor Labs says one victim reported that the attacker used a leaked GitHub CLI OAuth token.7 StepSecurity traced 173 probe pull requests from 19 accounts to tokens issued to the Fly.io GitHub app, says it has no evidence of a breach of Fly.io's own infrastructure, and says most activity uses other credentials such as personal access tokens.5 Aikido says accounts hit by October's GhostAction campaign were significantly more likely to be hit again, that wfx-loot was injected into GhostAction workflow files in more than 100 repositories, and that it assesses the two as likely different actors.1 Semgrep argues the tokens had been stolen earlier and never rotated.9

Update, 14 November 2026: Fly.io has said that some of the tokens used in the campaign came from its own GitHub App. Its community post says that on 12 November it learned that GitHub access tokens issued to the Fly.io GitHub App had been used by an unauthorised party to act on customer repositories, and that its systems were not breached.10 Fly.io says apps deployed from GitHub through its dashboard or automatic deploys had a token left in the .git/config file of the build directory, and that apps serving that directory over HTTP exposed the token at a public URL.10 It says tokens from a small number of its accounts were used, more than 250 "docs: dependency audit notes" pull requests were opened on them, and deploys with flyctl, Fly.io API tokens and running apps were not affected.10 CSO Online and heise online also report the .git/config leak.1314 StepSecurity had traced 173 probe pull requests from 19 accounts to the Fly.io app's tokens, so its count differs from Fly.io's.

Fly.io says it started revoking every user token issued to the app, but an addendum posted at 15:54 UTC on 13 November says not all were revoked, because GitHub support acknowledged that the process had started and stopped partway, and GitHub is looking into why.10 CSO Online reports that some of the stolen tokens may therefore still be valid.13 heise online, on 12 November, reported that GitHub had not yet commented.14

GitGuardian, in a post dated 13 November, says GitHub's requirement for approval held the workflow-file forms of the payload: all seven November payload runs it could still see were in the action_required state and never started.11 It says the npm hook form changes no workflow file, so the repository's own unchanged workflows ran npm install and the hidden script, with none of 30 sampled repositories blocked, and 18 of 19 public job logs it examined reporting successful exfiltration.11 GitGuardian says hook commits rose from 10 to 70 per three hours to 838 on the morning of 11 November and 1,210 on the morning of 12 November, and that developers who ran npm install from an affected repository may have run the payload on their own machines.11 It counts 28,500 payload patches from 2,367 accounts across 17,715 repositories in its own dataset, and 66,001 probe pull requests in GitHub search on 12 November.11 GitGuardian dates the first payload commit to 00:05 UTC on 24 October, with a precursor of 80 patches in 12 repositories to 29 October, while Mate Security, working from SafeDep's repository list, counts 27 trial commits from 25 to 29 October, which is not like for like with GitGuardian's 80.1112 GitGuardian and Mate Security both caution that a missing workflow run does not prove the payload executed, which bears on Aikido's 1,806 figure, as Aikido infers it from deleted run logs.1112 Mate Security also says 5,191 of the 7,225 workflow files the stealer was added to had been planted by an earlier campaign (140 attributed to GhostAction and 34 to Megalodon), among repositories on SafeDep's list.12

Why it matters: Aikido says the persistence steps are designed to outlast credential rotation, GitGuardian says the npm hook ran past GitHub's approval hold, and Fly.io says not all of its app's tokens were revoked, so checking repositories and revoking tokens still matters alongside rotating secrets.11011

Sources

  1. wfx-loot campaign pushes CI secret stealer to tens of thousands of repositories (Aikido Security)
  2. Attacker Used 4,837 Hijacked GitHub Accounts to Run a CI Secret Stealer in 1,806+ Repositories (The Hacker News)
  3. Hackers compromise 4,800 GitHub accounts to steal cloud credentials (BleepingComputer)
  4. Attacker Targets 60,000 GitHub Repositories in Credential Theft Campaign (SecurityWeek)
  5. WFX Phantom: The GitHub Actions Secret Stealer That Deletes Its Tracks (StepSecurity)
  6. wfx: GitHub Actions Credential Stealer Hits 8,000 Repos (SafeDep)
  7. Hijacked GitHub Accounts Push "wfx" CI Secret Stealer to Thousands of Repositories (Endor Labs)
  8. Thousands Of GitHub Accounts Hijacked With wfx-loot CI Secret Stealing Malware Via GitHub Actions & npm (OX Security)
  9. Seconds from Disaster: WFX Phantom and the CI Pipeline Nobody Was Watching (Semgrep)
  10. Security: GitHub tokens exposed by apps deployed from GitHub (Fly.io Community)
  11. wfx-loot: GitHub Actions Secret Stealer and the npm Bypass (GitGuardian)
  12. The wfx GitHub stealer: an October rehearsal, and what a deleted run proves (Mate Security)
  13. Thousands of GitHub repos hit with secret-stealing malware (CSO Online)
  14. Stolen tokens: Secret stealer targets thousands of GitHub repositories (heise online)