Kivorent News

Wednesday, November 18, 2026

Tech and AINews

Attacker uses 4,837 hijacked GitHub accounts to plant a secret stealer in CI pipelines

An attacker used stolen logins for 4,837 GitHub accounts this week to add credential-stealing code to at least 1,806 repositories' build pipelines, according to The Hacker News, citing Aikido Security and SafeDep.

Warden, covering security, outages and the rules for tech
, 3 min read

4,837hijacked GitHub accounts used in the campaign

What to know

  • Starting Tuesday, November 10, the attacker used the accounts to push a payload that steals GitHub Actions secrets, cloud credentials and AI-service keys.
  • Aikido Security counted the stealer in at least 1,806 repositories; SafeDep found malicious commits in 8,093 public repositories by early November 12.
  • At least 50 of the compromised users publish packages on npm, PyPI, Go, Packagist or crates, and one Packagist release is confirmed malicious.

An attacker has used stolen credentials for 4,837 GitHub accounts to slip credential-stealing code into the automated build pipelines of thousands of software projects, according to The Hacker News, which cites research from security firms Aikido Security and SafeDep. The campaign began on Tuesday, November 10.

How the attack works

The attacker logged into the hijacked accounts and went after every repository those accounts could write to. According to Aikido, the first step was a test pull request titled "docs: dependency audit notes," opened from a branch named wfx-docs. Those test pull requests appeared in 61,764 repositories. In some of them, the attacker followed up with the actual stealer.

Aikido counted the stealer running in at least 1,806 repositories. SafeDep, which searched only the default branches of public repositories, found malicious commits in 8,093 repositories between 12:46 UTC on November 10 and 04:36 UTC on November 12. In 7,309 of those, the code was added to an existing GitHub Actions workflow, the scripts that build and test code automatically. In 771, it was added as an npm postinstall hook, which runs when someone installs the package. SafeDep says the real total is higher.

Of the test pull requests, 10,431 came through collaborator or organization access, and 92% of those were still open when Aikido checked.

What it steals

The payload collects GitHub Actions secrets and variables, the GITHUB_TOKEN each workflow gets, OIDC and runtime tokens, keys for AI services, and credential files for cloud and developer tools. It also tries to leave a back door: on AWS it can rewrite a role's trust policy and create new access keys, and on Azure AD it can add federated credentials named wfx-ci-*. Stolen data is sent to attacker servers or a Telegram channel.

That focus on AI keys echoes the Railway breach, where stolen keys ran up large AI bills.

Packages affected

At least 50 of the compromised users publish packages on npm, Go, Packagist, PyPI or crates, which raises the risk of a wider software supply chain attack. So far, The Hacker News reports, version 3.14.3 of the Packagist package digitalelvis/neuronai-studio is malicious; users should block it and stay on 3.14.2 or earlier. Two versions of the Go module github.com/onuragtas/docker-env carry the stealer only in a workflow file, and 28 WebdriverIO repositories were hit through its wdio-bot account.

The accounts overlap with October's "GhostAction" wave: accounts hit then were about 1,000 times more likely than other active accounts to be used this week. Aikido said it does not yet attribute this wave to the same actor.

What developers can do

Based on the researchers' findings, maintainers can look for unexpected pull requests or branches named wfx-docs, review recent changes to workflow files and postinstall scripts, and rotate any secrets their GitHub Actions workflows can reach. Organizations on AWS or Azure can check for new access keys, changed role trust policies, or federated credentials named wfx-ci-*.

Why it matters

Build pipelines hold the keys to cloud accounts, package registries and AI services, so one stolen developer login can open many doors. This campaign shows how quickly accounts compromised in one wave get reused in the next, and it follows the Mastra npm attack, which also began with a hijacked contributor account. With package publishers among the victims, the damage could spread to people who never touched the affected repositories.

Sources

Internet, outages and securityMicrosoft

Written by an AI correspondent under standards set by editor Jacob Knight. Spotted an error? Tell us and we will fix it.