Updated 2026-11-15
Short answer: if a pull request titled docs: dependency audit notes or a wfx-docs branch appeared in a repository you can write to on or after 10 November 2026, the account that opened it is compromised. If the payload ran, assume every secret and cloud role available to that repository's workflows is stolen (Aikido).
docs: dependency audit noteswfx-docs, chore/ plus eight random characters, ci-check- plus four digitsci: refresh build cache, ci: restore, chore: add ci helper, ci: cleanup, chore: add dependency audit workflowgh search prs "docs: dependency audit notes" --owner YOUR_ORG
git log --all --oneline | grep -E 'ci: refresh build cache|chore: add ci helper|chore: add dependency audit workflow'
git branch -r | grep -E 'wfx-docs|chore/[a-z0-9]{8}$'These only read. Replace YOUR_ORG with your user or organisation name.
A shell script of about 1,500 lines collects GitHub Actions secrets and variables, the GITHUB_TOKEN, OIDC tokens, cloud and package-registry credential files, AI tool credentials and shell histories. It mints OIDC tokens for AWS, GCP and Azure, creates long-lived AWS access keys, opens AWS role trust policies to any account and adds federated credentials named wfx-ci- to Azure AD applications so access survives token rotation. It also posts forged success status checks to get past branch protection (Aikido).
"Principal": {"AWS": "*"}, and new IAM access keys.wfx-ci-.Packages that picked up the payload through automated publishing: Packagist digitalelvis/neuronai-studio 3.14.3 and Go github.com/onuragtas/docker-env v1.0.278 and v1.0.280, where the payload is in a workflow file only (Aikido).
FixLane's page: CI secret stealer pushed through compromised GitHub accounts.
It is the probe of the wfx-loot campaign: a compromised account opens it from a wfx-docs branch to confirm write access, then pushes a CI secret stealer. If you see it, the account that opened it is compromised.
Look for a missing run number in the workflow history next to the attacker's commit. The attacker deletes the run and its logs, so the gap is often the only trace.
No. If the payload ran, rotate every secret its workflows could reach and check AWS role trust policies and Azure federated credentials it may have added.
Connect an AI agent to the free, read-only FixLane MCP server or ask the Telegram bot: it checks what you have installed against verified fixed versions and serves a reviewed fix procedure. All guides.