Skip to main content
Mallory
← Back to News
build-pipeline-compromisecredential-stealer-activitydefense-evasion-methoddata-exfiltration-method

Hijacked GitHub Accounts Spread WFX CI Secret Stealer to Nearly 9,000 Repositories

Supply Chain Risk · 4 sources · Updated 4d ago · First seen Nov 12, 2026

Hijacked GitHub Accounts Spread WFX CI Secret Stealer to Nearly 9,000 Repositories

Attackers are using stolen GitHub credentials to inject the WFX credential stealer into repositories and execute it through GitHub Actions, according to an Endor Labs investigation published November 12. The ongoing supply-chain campaign reportedly probed 61,764 repositories and infected 8,926, with confirmed credential theft affecting more than 1,806 repositories. WFX collects CI/CD secrets, developer credentials, and cloud tokens, then attempts cloud privilege escalation and persistence before exfiltrating the stolen data.

The attackers deliver WFX through existing workflows, npm postinstall hooks, or newly created workflows, and conceal activity by reverting commits and deleting workflow runs and logs. Five payload versions appeared between November 10 and 12; later versions added Telegram exfiltration and revisited previously compromised repositories. Affected organizations should audit workflow and package changes, investigate cloud activity, and revoke or rotate exposed GitHub credentials, CI/CD secrets, and cloud tokens; reverted commits or missing workflow logs should not be treated as evidence that a repository is clean.

Does this reach your builds?Trace attribution and downstream blast radius.
Trace the chain
Event timeline

How this story unfolded

Events from the most recent confirmed update back to the earliest known activity.

8 events · Nov 10, 2026 – Nov 12, 2026
  1. Reported Nov 12, 20265d ago

    Malicious package versions are released on Packagist and Go

    Confirmed malicious releases included digitalelvis/neuronai-studio@3.14.3 on Packagist and github.com/onuragtas/docker-env versions v1.0.278 and v1.0.280 in the Go ecosystem. The account did not specify their release dates.

    Attaque supply chain GitHub : le stealer CI 'wfx' compromet +8900 dépôts via comptes détournés | CyberVeille
  2. Reported Nov 12, 20265d ago

    Wfx v2 adds npm postinstall delivery and AWS persistence

    Version 2 appeared during November 10–11, 2026, and affected 7,342 repositories. It fixed bugs, added npm postinstall delivery and AWS IAM persistence, and introduced 194.150.166.244:8080 as an exfiltration endpoint.

    Attaque supply chain GitHub : le stealer CI 'wfx' compromet +8900 dépôts via comptes détournés | CyberVeille
  3. Nov 12, 20266d ago

    Endor Labs discloses wfx campaign affecting 8,926 repositories

    Endor Labs published its technical analysis on November 12, 2026, reporting 61,764 probed repositories, 8,926 infected repositories, and confirmed credential theft from more than 1,806 repositories using credentials belonging to 4,837 developers. The analysis detailed CI and cloud credential collection, privilege escalation and persistence capabilities, and concealment through commit reversions and workflow-log deletion.

    AndreGironda: EndorLabs , Hijacked Github accounts push WFX CI secret stealer to thousands of repos -- https://t.co/e9DopKTbZp
  4. Nov 12, 20266d ago

    Wfx v5 expands delivery and retargets previously compromised repositories

    Version 5 affected 2,473 repositories, including 1,838 previously targeted by versions 1 or 2. It enabled all delivery vectors, used Telegram on every run, and contained Indonesian-language comments.

    Attaque supply chain GitHub : le stealer CI 'wfx' compromet +8900 dépôts via comptes détournés | CyberVeille
  5. Nov 12, 20266d ago

    Wfx v4 makes Telegram its primary exfiltration channel

    Version 4 appeared in one test repository, made Telegram the primary exfiltration channel, and set its C2 IP to 127.0.0.1 as a reported detection-evasion measure.

    Attaque supply chain GitHub : le stealer CI 'wfx' compromet +8900 dépôts via comptes détournés | CyberVeille
  6. Nov 12, 20266d ago

    Wfx v3 tests Telegram exfiltration

    Version 3 appeared in one test repository and added Telegram exfiltration using five bots. It also introduced the server 153.75.82.159:8080.

    Attaque supply chain GitHub : le stealer CI 'wfx' compromet +8900 dépôts via comptes détournés | CyberVeille
  7. Nov 11, 20267d ago

    Compromised WebdriverIO Bot bypasses branch protection to inject wfx

    On November 11 at 12:11 UTC, attackers used the compromised WebdriverIO Bot account to bypass branch protection in webdriverio/webdriverio, adding a 1,493-line malicious script and a silent pnpm postinstall hook. A contributor flagged the changes within about 20 minutes, and a revert pull request followed at 12:30 UTC.

    Hijacked GitHub Accounts Push “wfx” CI Secret Stealer to Thousands of Repositories | Endor Labs
  8. Nov 10, 20268d ago

    Wfx campaign begins with workflow injection into 695 repositories

    The campaign began on November 10, 2026, using stolen GitHub credentials to inject a CI secret stealer into repositories. Its first payload version affected 695 repositories, used GitHub Actions workflow injection, and exfiltrated data to 18.143.168.96:8080.

    Attaque supply chain GitHub : le stealer CI 'wfx' compromet +8900 dépôts via comptes détournés | CyberVeille
Linked entities

Related entities

Vulnerabilities, threat actors, malware, products, organizations, breaches, and observables Mallory has linked to this story. Indicator values are masked here and available in full in the app.

Open in app →

Malware

1 linked

Affected products

1 linked
Github

Organizations

1 linked
Nextcloud

Observables

12 linked

Indicator values are masked on this page. View all 12 in Mallory Domains, IPs, hashes, and URLs are exportable to your SIEM.

Do you run this?See attribution and downstream blast radius, and whether this package or vendor reaches your builds.
Trace the Supply Chain
Mallory platform

See the full picture, correlated to your attack surface.

This page covers what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which threat actors are using it right now, and what to deploy next.

Exposure mappingMap indicators from this story to your assets and identify affected systems in minutes.
Threat actor evidenceEvery observed campaign, victim, and pivot linked to actors named in this story.
Associated malwareMalware, exploits, and IOCs connected to the activity described here.
Detection signaturesYARA, Sigma, and Snort rules deployed to your SIEM as soon as they’re published.
Scheduled alertsGet matching new stories delivered to your team as they break, not the next morning.
AI threadsAsk questions about this story and take action on the answers.