GitHub Accounts Hacked: 4,837 Credentials Used to Probe 61,764 Repos
Nearly 5,000 GitHub accounts were used to probe over 61,000 repositories for stored credentials. Here's why that reaches further than the developer world.
In short
- The wfx-loot campaign used 4,837 compromised GitHub accounts to probe 61,764 repositories and push secrets-stealing malware — reported 12 November 2026.
- The campaign ran through compromised user accounts, not a reported GitHub platform breach — which is why password hygiene and 2FA are the defence that matters.
- 'Secrets' are stored credentials — cloud keys, API tokens, database and email passwords — and most small businesses hold at least one without realising.
- A stolen secret triggers no alarm on your machine; the attacker signs in as you, legitimately.
- This is the third supply-chain attack this week — the pattern targets accounts and tools that touch many businesses at once.
On 12 November 2026, BleepingComputer reported a campaign dubbed wfx-loot: threat actors used 4,837 compromised GitHub accounts to probe 61,764 repositories, open pull requests and push secrets-stealing malware. If you've seen "GitHub accounts hacked, credentials stolen" in the news this week, those are the numbers behind the headline.
Here's the detail that matters most for small businesses: the campaign ran through compromised user accounts — real people's logins. There's no indication GitHub's platform itself was broken into. That distinction changes what you should do about it, and it's why this story reaches further than the developer community.
What Happened: 4,837 GitHub Accounts, 61,764 Repositories
The attackers logged into thousands of real GitHub accounts and used them to probe tens of thousands of repositories, opening pull requests and pushing malware designed to steal credentials. The goal wasn't the code itself.
It was the credentials stored in and around those repositories: cloud account keys, API tokens, passwords. The kind of thing developers leave in config files, deployment scripts and integration settings, often years after anyone thought about them.
This is the third credential-and-toolchain attack story in a single week, alongside SCKit targeting MSP technicians via ScreenConnect and the N-able 4EverAble2Shell zero-day we covered on 12 November. We'll come back to that pattern — it's not a coincidence.
What Are 'Secrets', in Plain English?
"Secrets" is developer shorthand for any stored credential that lets one piece of software sign into something else. To give you a feel for the category — these are illustrative examples, not a list of what wfx-loot took:
- An AWS or Azure key that lets a script upload files to cloud storage
- An API token for a payment provider like Stripe
- A database password your website uses to read its own data
- An SMTP password that your newsletter or contact form uses to send email
They live in config files, plugins, WordPress themes, integration settings and CI scripts — often put there years ago by someone who's since left.
Here's the non-developer version: your website's plugin that talks to Stripe, your email newsletter tool, your backup that uploads to cloud storage — all of those hold a secret. You don't need to write code to own one.
And here's the nasty part: a stolen secret triggers no alarm on your machine. There's no pop-up, no antivirus warning, nothing. The attacker takes your key, goes to their own computer, and logs in as you — legitimately, as far as the service is concerned.
Why Reused Passwords Are the Obvious Suspect
GitHub wasn't broken into — thousands of individual accounts were. The report doesn't say how those accounts fell, and we won't pretend it does. But when that many ordinary logins go at once, the usual mechanism in campaigns like this is credential stuffing: passwords leaked in older, unrelated breaches, replayed against GitHub to see which ones still work. It works because people reuse passwords.
We'd bet on that here — but it's our inference, not a confirmed detail. Either way, the defence is the same, and it's the part that applies to you whether or not the guess is right:
- A password manager, so every account has a unique password. One breach then stops at one account instead of cascading.
- Two-factor authentication on the account. An account with 2FA enabled resists replayed passwords even when the password is valid.
A password leaked in a 2023 breach can still open an account in 2026 if it was never changed. Neither defence costs anything. Both take minutes. That's the uncomfortable part of this story — the defence is free, and most people haven't used it.
Why Small Businesses Are in the Blast Radius (Even Without a GitHub Account)
You don't need a GitHub account to be exposed:
- Your website's theme or plugin may be maintained on GitHub by a third-party developer
- Your contractor or agency may keep your project code there
- Your SaaS integrations — accounting, email marketing, backups — all hold stored credentials of exactly the kind this campaign hunted
The pattern across this week's stories is clear: attackers are targeting the supply chain — the tools, accounts and providers that touch many businesses at once, rather than each business individually. That's what SCKit did to MSP technicians and what the N-able zero-day did to management platforms.
In our workshop experience, small businesses almost always have at least one forgotten credential — an old FTP password, a plugin API key, a former developer's account — that nobody has rotated in years. It sits there like a key under the doormat, and nobody remembers it exists until it's used.
Warning signs a stored credential has been used:
- Unexpected cloud bills (miners and spammers use your compute and your money)
- Email sent from your domain that you didn't send
- A plugin or integration that's stopped working or behaves oddly
- Logins from locations you don't recognise in an account's activity log
The Credential-Hygiene Basics (What Everyone Should Be Doing)
The principles are simple, and they're genuinely worth doing this weekend:
- Use a password manager. Every account gets a unique password. This is the single highest-value change most people can make, and it costs nothing with the free tiers.
- Turn on 2FA on the accounts that matter most — email first, because it resets everything else. Then GitHub, cloud storage, banking, your website admin.
- Treat credentials like milk, not furniture. Anything a former employee or contractor had access to should be rotated when they leave — not left until it goes off.
- Don't store live secrets in code, config files or shared documents. There are proper tools for this — and a proper audit finds what's already exposed.
What we're deliberately not giving you: a step-by-step audit of every place your business stores credentials. That's a job for proper tools and experience, because the dangerous ones are by definition the ones you've forgotten. If you want to get started, give us a ring and we'll talk through what an audit involves — and if a machine in the chain turns out to be compromised, the clean-out is firmly our end of the job.
How This Fits the Pattern: A Bad Week for the Supply Chain
Put the three stories side by side and the strategy is identical:
- wfx-loot targets developer accounts
- SCKit targets the MSP technician's machine
- 4EverAble2Shell targeted the management tool itself
Same thinking: compromise the thing that touches many victims at once. As we wrote on 13 November, we treat this week's worm-style attacks as a campaign pattern rather than a coincidence — and wfx-loot fits it neatly.
The lesson from N-able still holds: patching alone doesn't save you when the credential or tool at the top of the chain is compromised. 19 of 21 N-able victims were fully patched. Hygiene and monitoring have to sit alongside updates.
If you run a server or a WordPress site, pair this with our SSH and PHP vulnerability post from 12 November — end-of-life PHP with outdated plugins is the entry point we see most often, and stored credentials are the second.
If You Think a Credential Has Been Used: What to Do First
Different situations need different first moves — last week's Microsoft 365 outage was a "change nothing" moment, but a suspected stolen credential is the opposite: act fast.
- Change the password on the affected account first, then the email account that can reset it — in that order.
- Check the account's activity or audit log for logins or actions you don't recognise.
- Rotate any keys or tokens that account had access to. This is the step people miss: changing the password does not invalidate keys already issued.
- Watch for the quiet aftermath — unexpected cloud bills, spam from your domain, integrations that break or behave oddly.
If a machine in the chain was compromised, patching isn't enough. Backdoors need cleaning out, and sometimes a rebuild is safer than a clean-up — that's a workshop job, not a settings toggle.
Let Us Handle the Machine End of It
The account side — rotating passwords, keys and tokens — is yours to do, and the basics above will get you most of the way. The machine side is ours. If a computer in the chain was compromised, our virus and spyware removal service handles the clean-out, and a Windows reinstall is sometimes the safer call. If stolen credentials have led to data loss, our data recovery and backup team is the recovery position.
Need it looked at today? Our Fast Track repair service is the urgent route.
Collection and delivery across Portsmouth is £10 each way, or drop the machine to us on Durham Street. Students and NHS staff get our discount, and we quote before any work starts.
We do this
Virus & spyware removal
Full clean-up, hardening advice, and a 6-month labour warranty.
Book this repairQuestions people ask
Was GitHub itself hacked?
There's no indication GitHub's platform was breached — the campaign ran through 4,837 compromised ordinary user accounts, which is the detail that matters for the rest of us.
How do I know if my GitHub account or repository was affected?
Check your account's security log for unfamiliar logins, and look for pull requests or commits you didn't make. If in doubt, change the password and rotate all tokens.
I don't have a GitHub account — does this affect me?
Possibly. Your website's plugins or themes may be maintained on GitHub, and your SaaS integrations hold stored credentials of exactly the kind this campaign hunted.
What are 'secrets' and why do attackers want them?
Stored credentials — cloud account keys, API tokens, database and email passwords — that let software sign into other services. A stolen one lets an attacker log in as you, with no alarm on your machine.
Is a password manager really safe, or just one more thing to hack?
Yes, and far safer than reuse. A good manager encrypts your vault locally; one breach of a random site no longer cascades into every other account you own.
Keep reading
SCKit Malware: The ScreenConnect Attack That Makes Your IT Provider the Target
A worm-style malware toolkit called SCKit spreads from an infected customer machine to the IT technician who connects to it — then fans out to every business that technician manages.
How to Check SSH Vulnerability: What It Means and What to Do About It
New SSH flaws get disclosed every year, so last year's advice goes stale fast. Here's what an SSH or PHP vulnerability actually means for your server, and how to tell if you're exposed.
N-able 4EverAble2Shell Zero-Day: 19 of 21 Victims Were Fully Patched
A zero-day in the software your IT provider uses to manage your machines is being actively exploited — and most of the victims had already done everything right. That changes the lesson.
Rather we just sort it for you?
Free quote over the phone. Collection & delivery across Portsmouth for £10 each way, or drop it at the workshop. 6-month labour warranty on every repair, 12 months on new parts.
- Student & NHS discount
- Fast Track same-day option
- Real engineers, no call centre