$ techbeacon▋
Phishing

Thousands of GitHub Accounts Hijacked in 'wfx-loot' Campaign to Harvest Cloud Secrets

Thousands of GitHub Accounts Hijacked in 'wfx-loot' Campaign to Harvest Cloud Secrets

A coordinated intrusion campaign identified as "wfx-loot" has leveraged nearly 5,000 compromised GitHub accounts to harvest cloud service credentials, security researchers reported. The operation, which began surfacing in recent weeks, targets open-source repositories to embed malicious code that can exfiltrate authentication tokens, API keys and other sensitive data used by developers and organizations.

According to the analysis, threat actors gained control of 4,837 GitHub accounts and used them to scan 61,764 repositories. In many cases the attackers opened pull requests that appeared legitimate, then pushed payloads designed to locate and steal stored cloud credentials. The scale of the activity suggests an automated approach, allowing the group to probe a large portion of the public codebase in a short period.

The malicious payloads operate by searching for common patterns of secret storage—such as hard‑coded AWS access keys, Azure connection strings, or Google Cloud service account files—and then transmitting the findings to command‑and‑control servers. By inserting the code through pull requests, the attackers increase the likelihood that the malicious changes will be merged, especially in projects with limited review processes. Once merged, the code runs in the context of the victim's CI/CD pipelines, giving the adversaries a foothold in production environments.

If successful, the theft of cloud credentials can enable a range of follow‑on attacks, including unauthorized resource provisioning, data exfiltration, and ransomware deployment. Enterprises that rely heavily on open‑source components are particularly vulnerable, as compromised libraries can propagate the malicious code across multiple downstream projects. The incident underscores the persistent risk that credential leakage poses to the broader software supply chain.

GitHub has responded by revoking the compromised accounts, resetting associated tokens, and enhancing its secret‑scanning capabilities. The platform also urges developers to enable two‑factor authentication, rotate any exposed keys immediately, and adopt automated tools that detect hard‑coded secrets before code is merged. Security experts recommend treating any repository that has received a pull request from an unknown source as suspicious until it is thoroughly vetted.

The wfx‑loot operation joins a growing list of supply‑chain attacks that exploit trusted development ecosystems. Past incidents have demonstrated how attackers can move from code repositories to production environments, turning seemingly innocuous open‑source contributions into vectors for large‑scale breaches. The frequency of such campaigns reflects both the attractiveness of cloud credentials and the challenges of policing a platform that hosts hundreds of millions of repositories.

Investigations are ongoing, with law‑enforcement and cybersecurity firms collaborating to trace the actors behind wfx‑loot. Meanwhile, the security community advises organizations to conduct comprehensive audits of their secret management practices and to monitor for anomalous activity in their cloud accounts. As attackers continue to refine automated methods for credential harvesting, vigilance at every stage of the development lifecycle remains essential.

Deepak Chandra Meena — Deepak covers the dark web and underground hacking forums, reporting on marketplace activity and access broker listings. Monitors Tor-based forums and encrypted leak channels.

Comments (0)

Be the first to comment.

Join the discussion

Protected by reCAPTCHA v3

Related