AEGLIX News
Researchers have verified that the wfx-loot operation commenced near 12:45 UTC on November 10, leveraging credentials harvested from 4,837 hijacked GitHub accounts to scan 61,764 repositories for write privileges. The adversary created pull requests labeled 'docs: dependency audit notes,' masquerading them as routine dependency audits, with 92% of those requests still open. Secret material was successfully exfiltrated from a minimum of 1,835 victims. The breached accounts spanned Fortune 100 enterprises, the U.S. General Services Administration, the French government, Nextcloud, and WebdriverIO.
A credential-harvesting shell script gathered GitHub Actions secrets, cloud keys for AWS, Azure, and Google Cloud, plus developer tokens from Git, SSH, GPG, Docker, Kubernetes, npm, PyPI, Vault, and Terraform. The collected material was packed into tarballs and shipped out through HTTP POST requests to one of two attacker-operated endpoints. Roughly 50 of the compromised accounts held publishing permissions on open-source registries including npm, PyPI, Go, crates, and Packagist, extending the supply-chain danger beyond the initially breached repositories.
Automated publishing pushed the malicious payload into Packagist's digitalelvis/neuronai-studio 3.14.3 and two releases of the Go module github.com/onuragtas/docker-env, namely v1.0.278 and v1.0.280. The wfx-loot campaign struck tens of thousands of GitHub repositories via poisoned workflows designed to swipe GitHub Actions secrets and cloud credentials, while the operator employed thousands of hijacked GitHub accounts to file pull requests against repositories those accounts could reach, probing for write access.
Repository maintainers should watch for the 'wfx-docs' branch, the probe pull request named 'docs: dependency audit notes,' and missing workflow run numbers as compromise indicators. The inquiry confirmed that credentials were stolen from at least 1,835 targets across numerous prominent organizations and government bodies, with the attacker preserving persistent access through open pull requests in most of the scanned repositories.
Report prepared 2026-11-12 · Based on reporting from BleepingComputer. Source publication date above; subsequent developments may not be reflected.
Sources
Read original source · BleepingComputer (opens in a new tab)