wfx
- Type
- Infostealer
- Capabilities
- Credential theftExfiltrationPrivilege escalationPersistenceDefense evasion
- Platforms
- LinuxCloud
wfx is a credential-stealing shell-script malware targeting GitHub Actions environments, particularly Linux CI runners. It was observed in a campaign beginning November 10, 2026, in which unidentified attackers used stolen developer and automation-account credentials to modify repositories accessible to those accounts. Delivery methods include injection into existing or newly created workflows, modification of CI-executed shell scripts, and npm installation hooks. These hooks can also execute the payload on developer machines. The campaign abuses legitimate repository access rather than exploiting a GitHub Actions vulnerability.
The approximately 1,500-line, unobfuscated payload implements collection, escalation, persistence, and exfiltration stages. It collects workflow secrets and variables, GitHub authentication and runtime tokens, process-memory contents, environment variables, shell histories, private keys, package-publishing credentials, cloud credentials, and API keys for AI services and development tools. It attempts to exchange GitHub OIDC tokens for AWS, Google Cloud, and Azure sessions, chain AWS roles, impersonate Google Cloud service accounts, and replay Azure authentication tokens. Persistence mechanisms include creating long-lived AWS access keys, weakening AWS role trust policies, and adding Azure federated identity credentials. It also attempts to forge successful status checks to bypass repository branch protections.
Stolen material is compressed and exfiltrated over HTTP, with later variants using Telegram. Campaign operators conceal activity by rapidly reverting malicious commits and deleting workflow runs and logs. Automated publishing has also carried malicious material into software package releases, although execution depends on the affected package and installation context. The principal targets are software-development, release, and deployment environments and the cloud resources accessible through their credentials.
Techniques & procedures
10 distinct techniques documented for this family, organized by ATT&CK tactic.
Initial Access
1 technique
Initial Access
Injection dans un workflow existant [...] Hook postinstall npm [...] Nouveau workflow sur branche jetable.
Execution
1 technique
Execution
Script shell non obfusqué d’environ 1 500 lignes, structuré en 4 étapes.
Persistence
1 technique
Persistence
création de clés IAM longue durée [...] réécriture de la trust policy AWS en "AWS": "*", ajout de federated credentials Azure nommés wfx-ci-*.
Privilege Escalation
2 techniques
Privilege Escalation
création de clés IAM longue durée [...] réécriture de la trust policy AWS en "AWS": "*", ajout de federated credentials Azure nommés wfx-ci-*.
T1548 — Abuse Elevation Control Mechanism (Privilege Escalation)
Credential Access
3 techniques
Credential Access
tous les secrets/variables Actions, GITHUB_TOKEN, tokens OIDC.
fichiers de credentials (AWS, Azure, GCP, Docker, Kubernetes, npm, PyPI, SSH, GPG, Vault, Terraform) [...] historiques shell, fichiers .env/.pem/kubeconfig.
fichiers de credentials [...] SSH, GPG [...] fichiers .env/.pem/kubeconfig.
Lateral Movement
1 technique
Lateral Movement
mint de tokens OIDC GitHub échangés contre des sessions AWS/GCP/Azure [...] impersonation de comptes de service GCP, replay de tokens Azure CLI.
Exfiltration
2 techniques
Exfiltration
Exfiltration par HTTP POST vers le serveur attaquant (port 8080, endpoint /exfil).
canaux alternatifs (cache Actions, artifacts wfx-loot-, step summary) présents dans le code mais désactivés.
Observables
17 indicators attributed across vendor reports, sandbox runs, and researcher write-ups. Values are masked here and available in full in Mallory.
Recent activity
14 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.