Skip to main content
Mallory
Malware

wfx

Tracked since Nov 12, 2026 · Updated 2 days ago
Trending this week#25of 30,235 malware families
Mention activity · 30 days14 mentions · peak 10 in a dayToday
Vulns0Associated
Actors0Associated
ATT&CK10Techniques
IOCs17Tracked
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.

Is this in your environment?See whether this family's indicators match your telemetry and which of your assets are exposed to the CVEs associated with it.
Check your exposure
MITRE ATT&CK

Techniques & procedures

10 distinct techniques documented for this family, organized by ATT&CK tactic.

Initial Access

1 technique
T1195.001Compromise Software Dependencies and Development ToolsEvidence1

Injection dans un workflow existant [...] Hook postinstall npm [...] Nouveau workflow sur branche jetable.

Execution

1 technique
T1059.004Unix ShellEvidence1

Script shell non obfusqué d’environ 1 500 lignes, structuré en 4 étapes.

Persistence

1 technique
T1098Account ManipulationEvidence1

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
T1098Account ManipulationEvidence1

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-*.

T1548Abuse Elevation Control MechanismEvidence1

T1548 — Abuse Elevation Control Mechanism (Privilege Escalation)

Credential Access

3 techniques
T1528Steal Application Access TokenEvidence1

tous les secrets/variables Actions, GITHUB_TOKEN, tokens OIDC.

T1552.001Credentials In FilesEvidence1

fichiers de credentials (AWS, Azure, GCP, Docker, Kubernetes, npm, PyPI, SSH, GPG, Vault, Terraform) [...] historiques shell, fichiers .env/.pem/kubeconfig.

T1552.004Private KeysEvidence1

fichiers de credentials [...] SSH, GPG [...] fichiers .env/.pem/kubeconfig.

Lateral Movement

1 technique
T1550.001Application Access TokenEvidence1

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
T1041Exfiltration Over C2 ChannelEvidence1

Exfiltration par HTTP POST vers le serveur attaquant (port 8080, endpoint /exfil).

T1537Transfer Data to Cloud AccountEvidence1

canaux alternatifs (cache Actions, artifacts wfx-loot-, step summary) présents dans le code mais désactivés.

Indicators of compromise

Observables

17 indicators attributed across vendor reports, sandbox runs, and researcher write-ups. Values are masked here and available in full in Mallory.

View all in app →
Indicator values are available in Mallory. Pivot on every hash, domain, URL, and IP, or pipe them straight into your SIEM.View all in Mallory
Activity feed

Recent activity

14 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.

View more in app →
security affairsNews · Nov 15, 2026SECURITY AFFAIRS MALWARE NEWSLETTER ROUND 123A credential stealer targeting GitHub Actions, reportedly affecting 8,000 repositories. No implementation or delivery details are supplied.Read more ↗security affairsNews · Nov 15, 2026Security Affairs newsletter Round 604 by Pierluigi Paganini - INTERNATIONAL EDITION - Security AffairsA credential stealer associated with GitHub Actions that reportedly affected 8,000 repositories. Delivery mechanisms and the credentials stolen are not detailed.Read more ↗blueteamsecNews · Nov 14, 2026WFX Phantom: The GitHub Actions Secret Stealer That Deletes Its Tracks - StepSecurity - Infosec.PubA malicious shell script pushed directly to repository default branches by a coordinated botnet of compromised GitHub accounts after opening seemingly harmless pull requests. It executed through GitHub Actions to steal secrets; attackers then quickly reverted their changes to minimize traces.Read more ↗linuxsecurityNews · Nov 13, 2026GitHub Actions Account Hijack Puts Build Secrets at RiskCredential stealer deployed through malicious GitHub Actions workflows and project scripts using compromised developer and automation accounts. It targets Linux build runners, scanning memory, credential files, configuration files, and package-installation history for secrets, passwords, SSH keys, publishing tokens, and cloud credentials. Samples initially exfiltrated data to HTTP collection servers; later samples supported Telegram. Activity began November 10, 2026, and researchers reported execution in more than 1,800 projects, without confirming credential theft from every project.Read more ↗
+8 more in the timeline. Sign up to see them
Is this in your environment?See whether this family's indicators match your telemetry and which of your assets are exposed to the CVEs associated with it.
Check your exposure
Mallory platform

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets match these IOCs, which detections are missing, which campaigns to expect next, and what to do in the next 30 minutes.
IOC matching17Match every observed IP, domain, and hash against your live telemetry.
Associated threat actorsGroups linked to this family, with evidence pinned to each claim.
Associated vulnerabilitiesCVEs linked to this family, with the reporting behind each link.
Detection signaturesYARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
MITRE ATT&CK mapping10Every documented technique, ranked by evidence weight.
Researcher chatterReddit, Mastodon, and CTI community discussion around this family.