What Is wfx-loot? The GitHub Actions Secret Stealer Attack Explained

wfx-loot is a GitHub Actions secret stealer. It used thousands of hijacked developer accounts to raid CI pipelines for cloud and AI credentials. Security researchers first spotted it on November 10, 2026. An attacker had pushed the stealer script into public repositories at scale. The campaign opened probe pull requests in over 61,000 repositories and ran its payload in at least 1,806 of them. It matters for any team running GitHub Actions. CI secrets are only as safe as the accounts that can touch them.

What Is wfx-loot?

wfx-loot is the name researchers gave to a shell script that steals secrets from GitHub Actions workflows. Aikido Security identified the campaign first. StepSecurity, SafeDep, and Endor Labs each published separate analyses within days. The script itself runs about 1,500 lines and skips obfuscation entirely. That let researchers read its full logic directly.

The attacker did not exploit a flaw in GitHub Actions. Instead, they used stolen credentials, tokens, or OAuth grants tied to 4,837 real developer accounts. Those accounts had either direct write access to repositories or indirect access through a collaborator role or organization membership. Researchers have not confirmed how the attacker first obtained the credentials.

How the wfx-loot Attack Works

Each attack began with a probe. The attacker opened a pull request titled “docs: dependency audit notes” from a branch named wfx-docs. That PR tested whether the compromised account could actually write to the repository. Researchers logged more than 61,764 of these probe pull requests by November 12.

Where write access worked, the attacker pushed the real payload. Most commits, 7,309 by SafeDep’s count, added steps to an existing workflow file under a message like “ci: refresh build cache.” A smaller group of 771 repositories hid the script inside an npm postinstall hook instead. It ran the moment someone installed the package. Sixteen repositories got an entirely new workflow file instead.

In most cases, the attacker reverted the malicious commit within about a minute. Then they deleted the workflow run and its logs. DevX’s past coverage of the Node2Shell vulnerability in Node.js shows a similar pattern. Both incidents show how quickly a CI pipeline can process and discard evidence. A missing run number in a repository’s Actions history is often the only trace wfx-loot leaves behind.

See also  PostgreSQL 19: What's New, What Got Reverted, and When It Ships

What Secrets and Cloud Access wfx-loot Targets

The script dumps every configured secret and variable in a workflow using GitHub’s own toJSON(secrets) and toJSON(vars) functions. It also scans the Runner. Worker and Runner. Listener processes in memory, where GitHub briefly decrypts secrets during a job.Listener processes in memory, where GitHub briefly decrypts secrets during a job. That technique can surface values even when a workflow file never references them directly.

Confirmed targets include API keys for OpenAI, Anthropic, Gemini, Hugging Face, Cursor, GitHub Copilot, and Codex. The stealer also grabs AWS, Azure, and GCP credentials, plus Docker and Kubernetes configs. It takes npm and PyPI tokens, SSH and GPG keys, Vault tokens, and Terraform state files too. On self-hosted runners, it reaches instance metadata credentials as well.

Why wfx-loot’s Cloud Persistence Survives Key Rotation

Credential theft is only part of the story. Researchers found that wfx-loot also builds durable backdoors into cloud accounts. A Cloud Security Alliance research note explains what happens next. The script trades a repository’s GitHub OIDC token for a short-lived AWS, Azure, or GCP session. It then uses that session to plant something more permanent.

In AWS, it creates long-lived IAM access keys. It also rewrites role trust policies so any AWS account can assume the role. In Microsoft Entra ID, it plants a federated identity credential called wfx-ci. That credential lets future workflow runs on the main branch log in without storing a secret. Rotating the original stolen secret does nothing to remove either backdoor. Teams have to hunt for the backdoor itself.

Who Is at Risk After the wfx-loot Attack?

At least 50 of the compromised accounts maintain packages on npm, PyPI, Packagist, Go’s module registry, or crates.io. Three confirmed cases clearly show the risk. A Packagist package called neuronai-studio shipped a new version carrying the stealer. Two separate Go modules also picked up malicious workflow files. Twenty-eight repositories in the WebdriverIO testing framework were also hit through commits made under its own bot account.

See also  What Is the PHP2Shell Vulnerability? The Critical PHP RCE Flaw Explained

That overlap matters for downstream users who never touched a compromised repository directly. Anyone who ran npm install against an affected commit, even briefly, should treat that machine as compromised too.

How to Detect and Remediate wfx-loot in Your Repositories

Search every repository you can write to, including private ones. Look for a branch named wfx-docs or a pull request titled “docs: dependency audit notes.” Confirm it dates from November 10, 2026, or later. Also look for commit messages like “ci: refresh build cache” or “chore: add ci helper.” Gaps in your Actions run numbers are another clue.

If you find any of these signs, rotate every secret the affected workflow could reach. Do not stop at the ones it obviously used. Revoke the committing account’s personal access tokens, OAuth app grants, and SSH keys. Turn on phishing-resistant multi-factor authentication too. Then check AWS CloudTrail for AssumeRoleWithWebIdentity sessions named wfx, and check Entra ID for federated credentials with the same prefix.

Longer term, require pull request review on every branch that can trigger a deployment. Also set GITHUB_TOKEN to read-only by default. DevX has already covered the discipline this kind of incident calls for, in its explainer on the OpenCode breach. There, stored API keys leaked through a different kind of compromise. The lesson repeats: a CI pipeline should never hold more access than the job in front of it actually needs.

Key Takeaways

  • wfx-loot used 4,837 hijacked GitHub accounts to open probe pull requests in over 61,000 repositories.
  • The stealer ran in at least 1,806 repositories between November 10 and 12, 2026.
  • It targets AI provider keys, cloud credentials, npm and PyPI tokens, and SSH keys alike.
  • Its AWS and Azure backdoors survive ordinary secret rotation.
  • At least 50 compromised accounts maintain public packages, extending the risk downstream.
See also  What Is Microsoft's November 2026 Patch Tuesday? Outlook Zero-Day Explained

Frequently Asked Questions About wfx-loot

What Is wfx-loot?

wfx-loot is a GitHub Actions secret stealer that an attacker pushed into repositories using 4,837 hijacked developer accounts. Security researchers first identified it on November 10, 2026.

Did wfx-loot Exploit a Vulnerability in GitHub Actions?

No. Researchers confirmed the attacker used stolen credentials and tokens, not any flaw in GitHub’s platform. The attack works because a compromised account can already write to a repository.

How Do I Know if My Repository Was Affected?

Search your repositories, including private ones. Look for a branch called wfx-docs, a pull request titled “docs: dependency audit notes,” or a commit message like “ci: refresh build cache.” Gaps in your Actions run numbers are another sign.

Does Rotating My Secrets Remove the wfx-loot Backdoor?

Not by itself. The script also creates AWS IAM keys and Azure federated identity credentials that survive routine secret rotation. Teams need to audit and remove those separately.

Is wfx-loot Connected to the October GhostAction Campaign?

Possibly. Researchers found that accounts tied to October’s GhostAction campaign were roughly 1,000 times more likely to show up in wfx-loot. In more than 100 repositories, the new stealer landed inside October’s existing malicious workflow files.

Has GitHub Responded to wfx-loot?

As of this writing, GitHub has not issued a public statement about the campaign. Researchers note that GitHub previously blocked workflow files from a related campaign in October.

Final Thoughts

wfx-loot is not a GitHub Actions vulnerability. Instead, it reminds us that stolen credentials alone can trigger a cloud breach when CI pipelines hold broad access. Teams should treat every secret a workflow can reach as a potential target. A job’s own secrets are not the only ones at risk. Audit your repositories for the signs researchers have published. Then rotate what you find, and hunt for the cloud backdoors separately. Attackers often reuse compromised accounts within weeks, so recovery has to be thorough, not fast.

Photo by Rafael Minguet Delgado: Pexels

About Our Editorial Process

At DevX, we’re dedicated to tech entrepreneurship. Our team closely follows industry shifts, new products, AI breakthroughs, technology trends, and funding announcements. Articles undergo thorough editing to ensure accuracy and clarity, reflecting DevX’s style and supporting entrepreneurs in the tech sphere.

See our full editorial policy.