decrypted · 15 november 2026 · supply chain · ai and llm security · digital sovereignty
Stolen GitHub tokens turned thousands of build pipelines into secret thieves
Over the past few days, attackers have used stolen GitHub access tokens to slip a secret-stealing script into the automated build pipelines of thousands of software projects, then wiped away the evidence. OX Security and Aikido, two security firms reporting separately, call the campaign wfx-loot. At least 1,806 repositories ran the payload and sent their secrets out. The attackers did not break GitHub. They held keys that belonged to someone else.
How it worked
Think of a post room that also holds the master keys. A CI/CD pipeline, the automated system that builds and ships code, needs exactly that: cloud passwords, publishing tokens and service keys, all within reach of anyone who can edit its instructions. OX counts 4,837 hijacked accounts. For each repository an account could write to, the attacker first opened a pull request titled "docs: dependency audit notes", a quiet test of whether the token had write access. Then came a commit disguised as routine maintenance, adding about 1,500 lines of shell script to a workflow or hooking into npm, JavaScript's public library of add-on packages, so it ran on install. The next build executed it. Within minutes the commit was reverted and the run logs deleted.
What it took, and what you would see
Aikido says the script harvested workflow secrets, cloud credentials, registry publishing tokens and AI service keys, then tried to swap that access for live AWS, Azure and Google Cloud sessions. To stay in, it rewrote an AWS trust policy to admit any principal and added Azure credentials named wfx-ci, which survive token rotation. Data went to raw IP addresses and, from 12 November, partly through Telegram bots, per OX, so blocking addresses is not enough.
For defenders, the tell is an absence. OX says the most reliable trace is a missing workflow run number, because the logs are gone. Search your organisation for that pull request title, branches called wfx-docs, and commits titled "ci: restore" or "ci: cleanup" since 10 November. If a malicious commit landed in a repository with Actions enabled, OX advises treating every secret that workflow could reach as stolen, even if no run is visible.
The Secure by Design lesson
The pipeline was trusted with too much, for too long. Bot accounts bypassed branch protection: in one project, OX says, two commits went in through its bot that way and were caught by a contributor about 20 minutes later. Aikido adds that the script forged "success" status checks, so required checks alone are not a safeguard.
The fixes are dull and cheap: short-lived tokens, narrow workflow permissions, bots held to the same review rules as people, and secrets released only to the jobs that need them. That costs far less than rotating every credential you own.
Ask your engineering lead three questions. Do we use GitHub Actions? Can any token or bot change our main branch without review? If a build were hijacked today, which secrets would it be holding?
Also this week
AI-powered ransomware, officially expected. The NCSC's assessment of AI and cyber intrusion, published on 3 November, judges it "highly likely" that, between now and 2028, AI-powered malware will have been used in a ransomware attack on UK critical national infrastructure. It also calls it "almost certain" that many systems will stay open to AI tools that find and exploit weaknesses. The Chancellor announced £60 million for the first phase of a national Cyber Shield and £70 million for a National Exposure and Real-Time Vulnerability Centre to help find those weaknesses first. NCSC chief executive Richard Horne said: "For decades, we have collectively got away with doing tech on the cheap." The wfx-loot script above went hunting for AI service keys too. The defence is still patching, monitoring and tight credentials, done earlier.
EU cloud sovereignty rules could shut out UK suppliers. techUK warned on 10 November that UK firms could lose sensitive EU public-sector cloud contracts under the proposed Cloud and AI Development Act, with losses of up to £22.3 billion in UK economic activity over five years. That is an industry lobby estimate, as MLex reports it, not a government figure. techUK wants the UK recognised as a trusted third-country provider, judged on technical safeguards rather than ownership. Its June analysis says the Act would judge services on operational autonomy, control, resilience and exposure to third-country jurisdictions, and could recognise third countries as giving sufficient assurances, with details still to be negotiated. The UK and EU discuss trade at a 20 November summit. Where your cloud is controlled from is becoming a procurement question, so know the answer.
Sources
- OX Security: Thousands of GitHub accounts hijacked with wfx-loot CI secret-stealing malware
- Aikido: wfx-loot campaign pushes CI secret stealer to tens of thousands of repositories
- NCSC: Artificial intelligence and cyber intrusion
- NCSC: Cyber chief: UK facing AI-powered attacks on critical infrastructure within two years
- MLex: UK tech suppliers face losses under EU cloud sovereignty rules, techUK says
- techUK: Europe's Technology Sovereignty Package and what it means for UK tech
If your build pipelines or cloud contracts need a second pair of eyes, get in touch.
More like this
- A Microsoft outage showed how one network change can stop your email 16 november 2026
- Cursor's leaked supplier key ended in a booby-trapped Claude Code extension 15 november 2026
- A record quarter of cyber incidents, and the regulator will chase almost none 14 november 2026
Get the next post by email: subscribe to Decrypted. Double opt-in, unsubscribe any time, or take the RSS feed.
Prefer to listen? Decrypted on Apple Podcasts, or paste the podcast feed into any app.