On November 12, 2026, Aikido and other research teams documented wfx, a campaign using stolen GitHub access to place a secret stealer in build pipelines. Activity has been tracked since November 10. For a small development team, the risk is that a familiar account can change code with access to delivery credentials.
Valid credentials open the repositories
Aikido describes reconnaissance pull requests sent through compromised accounts, followed by malicious changes where permissions allow. A familiar contributor name is therefore insufficient evidence that a change is legitimate.
Start with repositories where developers and bots have write access. Identify the services their workflows can reach too: package publishing, cloud infrastructure and metered APIs.
Keep three exposure categories separate
SecurityWeek distinguishes tens of thousands of probed repositories from those receiving malicious commits and those where execution was established. These categories describe different impacts and their counts evolve.
Decisions for your business need repository-specific evidence. A probe calls for examination; confirmed execution means treating the secrets accessible to the job as exposed, according to the researchers.
A branch can look normal after execution
StepSecurity directly examined more than 80 commits and describes several payload locations: workflows, scripts already run by CI and installation hooks. Its observations also include Telegram exfiltration variants, limiting the value of blocking only published collection IP addresses.
Semgrep examines the short interval between insertion, execution, reversion and trace deletion. A clean branch today does not establish that the code never ran. Review audit events rather than relying on the latest diff alone.
Restore delivery from a trusted environment
If execution is established, revoke compromised GitHub access and replace secrets the job could read. The analyses also describe cloud persistence attempts, so the review must include AWS keys, role trust policies and Azure federated identities.
We recommend documenting replaced secrets separately from removed permissions. Validate workflows and hooks before running them again on a trusted workstation. Installing dependencies from a suspect revision can execute the payload again.
The connection with Soclyde
wfx highlights the difference between a human password and a CI token. Soclyde keeps account passwords in an encrypted vault on your devices. This organization does not protect a secret already accessible to a malicious workflow or revoke cloud identities created by an attacker.
What to remember
Review history, establish whether the code executed and address persistent access as well as secrets. For human passwords kept separate from CI tokens, prepare unique replacements with our password generator.



