Skip to main content
Mallory
Threat actor

wfx-loot

Updated 5 days ago
Trending this weekNot trendingOutside this week’s top 100
Mention activity · 30 days4 mentions · peak 3 in a dayToday
CVEs0Associated
Malware0Families
ATT&CK0Techniques
IOCs0Tracked
Motivation
—
Capabilities
Credential theftInitial accessReconnaissanceScanningExfiltrationPersistenceLateral movementDefense evasion
Also known aswfx-loot

wfx-loot is an unattributed threat operation targeting GitHub repositories and their connected continuous integration and cloud environments. The name identifies the operation and its CI secret-stealing malware rather than an established, independently attributed threat group. Beginning November 10, the operation used stolen credentials for 4,837 GitHub accounts to probe 61,764 repositories, with confirmed stealer execution in at least 1,806 repositories. Targets include open-source software projects and repositories accessible through compromised developer, collaborator, organization, and bot accounts. The attackers authenticate using legitimate account access rather than exploiting a GitHub Actions vulnerability. They test repository write permissions with innocuous pull requests, then insert malicious workflows, modify existing CI scripts, or introduce package installation hooks. Compromised bot permissions have enabled branch-protection bypass. Payload changes are often reverted within a minute, and workflow runs and logs are deleted to conceal execution. Repeated attacks against previously compromised repositories can expose replacement secrets introduced after an initial incident. The malware steals GitHub Actions secrets and variables, workflow authentication tokens, OIDC tokens, and credentials associated with cloud platforms, container infrastructure, package registries, SSH, and secret-management systems. It also searches runner-process memory for secrets and collects API keys for AI services and coding tools. Cloud persistence mechanisms include creating long-lived AWS access keys, weakening AWS role trust policies, and adding unauthorized Azure federated identity credentials. These mechanisms can remain effective after ordinary secret rotation. Earlier payloads exfiltrated through HTTP endpoints, while later versions used Telegram. The operation has also affected package-publishing accounts and introduced malicious changes into distributed package versions, although repository or package contamination does not by itself establish payload execution. Its initial account-compromise mechanism, geographic origin, sponsorship, and dominant motivation remain unconfirmed.

Are they targeting you?See whether this actor's campaigns touch your sector, your geography, or the products you run, and get alerted when that changes.
Check your exposure
Operational profile

Targeting

Who, where, and from where this actor operates. Pulled from open-source reporting and Mallory's analyst review.

Who they target

Sectors the actor has been observed targeting.

  • Software & Services
FAQ

Frequently asked questions

Who does wfx-loot target?
wfx-loot targets Software & Services.
Mallory platform

The version that knows your environment.

This page is what's public. Mallory adds the parts that aren't: whether this actor's tooling has touched your footprint, the IOCs they're burning right now, and the detections to deploy next.
Target overlapMatch sector + geo + tech-stack targeting against your real footprint.
Tradecraft mappingMITRE ATT&CK techniques reported for this actor, grouped by tactic.
Associated malwareFamilies linked to this actor, with IOCs and behavior.
Associated CVEsCVEs linked to this actor, with the reporting behind each link.
Detection signaturesYARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
ObservablesDomains, IPs, and hashes tied to this actor, refreshed continuously.