Aikido: attacker used 4,837 hijacked GitHub accounts to steal cloud credentials
The attacker used the hijacked accounts to test write access to 61,764 repositories and ran a script in some of them that was designed to collect secrets from automated workflows as well as cloud and AI service credentials, security company Aikido said.
Security company Aikido Security has reported on the wfx-loot campaign, which BleepingComputer and The Hacker News, among others, have covered. The attack began on 10 November, and the attacker held credentials for 4,837 GitHub accounts, Aikido said.
How the script worked
The attacker used the accounts to open a pull request titled ‘docs: dependency audit notes’ from a wfx-docs branch to test whether each account could write to the repository. In some of these repositories, the attacker added a script of about 1,500 lines to GitHub Actions. The service runs a repository’s build and test steps as automated workflows, and these workflows often have access to secrets.
The script was added to an existing workflow, to a new workflow on a short-lived branch, or as an npm postinstall hook, which also runs on a developer’s machine during installation. It was designed to collect workflow secrets and tokens, AWS, Azure and Google Cloud credentials, and credentials for OpenAI, Anthropic, Gemini, Hugging Face, Cursor and GitHub Copilot, among others.
The collected data was sent to the attacker, after which the changes were reverted and the logs deleted, usually along with the runs. Early reports described two servers and a clean-up lasting less than a minute, but a separate analysis by security company SafeDep found a third server, a Telegram channel and changes that stayed in place longer, The Hacker News reported.
The sources’ figures differ
Researchers confirmed that secrets were stolen from at least 1,835 targets, BleepingComputer reported. According to The Hacker News, Aikido says the script ran in at least 1,806 repositories and estimates that the attacker likely obtained credentials from them. Aikido’s figures cover only the public repositories the company has seen.
SafeDep counted 8,093 repositories that received a malicious commit between 12:46 on Tuesday and 4:36 on Thursday morning (UTC), whether or not the script ran. The search covered only the default branches of public repositories, so the real number is higher, SafeDep said. The Hacker News found test pull requests with the same title still being opened from wfx-docs branches after Aikido’s search ended on Wednesday. It is unclear whether the script followed them.
Rotating keys alone is not enough
The script can exchange a GitHub OIDC token, a short-lived credential, for an AWS, Azure or GCP session. The Hacker News reported that it can also change an AWS role’s trust policy so that any AWS account can use the role. In Azure, it can add federated identity credentials with the prefix wfx-ci-. These let the repository’s workflows reach Azure even after the tokens are rotated.
Aikido said every account the attacker used to open a test pull request is compromised, whether or not the script ran. If the script ran, all secrets and cloud roles available to the workflow must be treated as compromised and rotated. A missing run number on the attacker’s commit indicates a run more reliably than other traces do. Researchers advise searching Entra ID for unknown wfx-ci credentials and CloudTrail for sessions whose names start with wfx and that are followed by a CreateAccessKey or UpdateAssumeRolePolicy call.
SafeDep advises owners of repositories that received a malicious commit to revoke the commit author’s tokens, OAuth app authorisations, SSH keys and sessions. Owners should also enable two-factor authentication and rotate all secrets and variables the repository can read. Any machine that has run npm install from a compromised commit must be treated as compromised and its keys rotated, SafeDep said.
Version 3.14.3 of the Packagist package digitalelvis/neuronai-studio is malicious, and Aikido advises treating every machine where it has been installed or opened as compromised. A normal composer install does not run the script, but npm install in the package’s vendor directory does. Researchers advise blocking version 3.14.3 and pinning version 3.14.2 or earlier.
In versions v1.0.278 and v1.0.280 of the Go module github.com/onuragtas/docker-env, the script sits only in a workflow file that the Go build does not run. It may therefore not have affected the module’s users, but Aikido still recommends removing the versions. Aikido also advises blocking the pseudo-version v0.0.0-20261111095532-8d5aad0cb0da of the module github.com/vkuznet/gocurl.
Read more: How an agent works · Agent map