wfx-loot Campaign Compromises 4,837 GitHub Accounts to Steal Cloud Credentials from 61,764 Repositories

wfx-loot Operation: Attacker Probes 60,000 GitHub Repositories for Credential Theft

An attacker tested stolen access across more than 60,000 GitHub repositories and inserted credential-stealing code in thousands of them. Security firms Aikido Security, StepSecurity, and SafeDep tracked the wfx-loot campaign that began on November 10. The operation relied on valid tokens from developer and bot accounts rather than any GitHub Actions vulnerability. Malware was deployed via existing or new workflows, CI shell scripts, and npm installation hooks, targeting tokens, secrets, cloud credentials, and AI service keys. The script also read GitHub Actions runner memory and attempted persistence in AWS and Azure environments. Affected releases include one Packagist package and versions of two Go modules. Organizations are advised to revoke compromised tokens and rotate exposed secrets.

Attacker Hijacks 4,837 GitHub Accounts to Deploy CI Secret Stealer Across 1,806 Repositories

An attacker leveraged stolen credentials from 4,837 GitHub accounts to insert a sophisticated secret-stealing workflow into at least 1,806 repositories. The campaign began with test pull requests titled "docs: dependency audit notes" from branches named wfx-docs, targeting 61,764 repositories before deploying the stealer in successful cases. Aikido Security and SafeDep researchers documented the use of both workflow modifications and npm postinstall hooks, with the malware exfiltrating GitHub tokens, cloud credentials, and repository data to attacker-controlled servers and Telegram. The stealer also reached several open-source packages, including a malicious Packagist release and two Go modules, though package users were not always impacted. Overlaps with the earlier GhostAction campaign suggest credential reuse across multiple threat actors. Repository owners are advised to revoke tokens, rotate all accessible secrets, and monitor for specific indicators such as wfx- prefixed federated credentials in Azure and AWS.

ConnectWise Investigates Active ScreenConnect Attacks Breaching MSPs and Impacting Dozens of Organizations

ConnectWise is investigating an active malware campaign targeting managed service providers that uses compromised ScreenConnect environments to deploy rogue remote-access clients to customer devices. Huntress discovered the campaign on November 11, 2026, identifying six compromised MSPs and 286 affected endpoints across 47 organizations, with numbers continuing to rise. Attackers leverage ScreenConnect's Run Command functionality to install unauthorized clients, enabling remote access outside legitimate MSP control, and may also compromise technician workstations through reverse-pivot techniques during sessions with infected devices. ConnectWise has advised partners to avoid interactive sessions with suspected compromised devices, review account activity, revoke sessions, reset credentials, and verify multifactor authentication. Huntress provided indicators of compromise including attacker relay IP 185.99.255.28, C2 domains, rogue client IDs such as 2588ef5c15954b10, and files like Panel-Lateral.ps1. Earlier malicious activity linked to one rogue client ID was identified in a July 2026 batch script impersonating a Social Security Administration statement.