Skip to content
← All stories

Identity · Application Security

Thousands of GitHub accounts hijacked to steal secrets from CI workflows

Attackers used nearly 5,000 hijacked GitHub accounts to plant a secret-stealing tool in over 1,800 repositories, targeting credentials and cloud secrets used in CI pipelines, according to researchers.

Ross Grant3 min read

The short version

Attackers broke into nearly 5,000 GitHub accounts and used them to add a tool that steals secrets from software projects. This tool ran in at least 1,800 projects and targeted passwords and cloud credentials used by automated build systems. If you use GitHub, check for suspicious pull requests and rotate your secrets if you see signs of compromise.

By the numbers

  • 4,837GitHub accounts hijackedThe Hacker News
  • 1,806+Repositories where the secret stealer ranThe Hacker News
  • 8,093Repositories with malicious commits found by SafeDepThe Hacker News
  • 61,764Repositories that received test pull requestsThe Hacker News

What happened?

Attackers used stolen credentials from 4,837 GitHub accounts to plant a secret-stealing tool in at least 1,806 repositories, according to Aikido Security. The tool targeted secrets and cloud credentials available to CI workflows. SafeDep researchers found evidence of malicious commits in over 8,000 repositories. The full extent of the breach is still being investigated.

Who is affected

According to Aikido Security, attackers took over 4,837 GitHub accounts and used them to open pull requests in at least 61,764 repositories. The secret-stealing tool actually ran in at least 1,806 repositories. SafeDep, another security company, found evidence of malicious commits in 8,093 repositories, though not all of these saw the stealer run. The attack targeted public repositories, but researchers believe private repositories could also be affected. At least 50 of the compromised accounts belonged to developers who publish packages for npm, Go, Packagist, PyPI, or crates.

How the attack worked

The attacker used stolen credentials to access GitHub accounts. They then opened pull requests titled "docs: dependency audit notes" from a branch named "wfx-docs" to test write access. If the account had permission, the attacker pushed a secret stealer into the repository. In some cases, the malicious code was added to existing CI workflows; in others, it was included as an npm postinstall hook, which would also run on a developer's machine during npm install. After deploying the stealer, the attacker often reverted the change within minutes and deleted logs, making detection harder. The stealer sent stolen data to remote servers or a Telegram chat.

What was taken

The stealer was designed to collect any credentials available to the repository's CI (Continuous Integration) workflows. This includes GitHub Actions secrets, cloud provider tokens (AWS, Azure, GCP), SSH keys, API keys for AI services, and other sensitive data stored on the runner. It also copied the repository, recent commits, and workflow artifacts. On self-hosted runners, it could extract credentials from cloud instance metadata and Docker containers. The tool was able to use GitHub OIDC (OpenID Connect) tokens to create new sessions with cloud providers and, in some cases, create long-lived access keys or backdoors that could survive credential rotation.

The response

Researchers recommend that affected repository owners revoke all tokens, OAuth grants, SSH keys, and active sessions for compromised accounts. They also advise rotating every secret and variable accessible to the repository, enabling two-factor authentication (2FA), and treating any machine that ran the malicious code as compromised. For the Packagist package "digitalelvis/neuronai-studio" version 3.14.3, users should block this version and use 3.14.2 or earlier. For the Go module "github.com/onuragtas/docker-env" versions 1.0.278 and 1.0.280, removal is recommended, though the Go code itself was not altered.

What you should do

If you manage a GitHub repository, check for pull requests titled "docs: dependency audit notes" from the past week. Review commit messages such as "ci: refresh build cache" or "chore: add ci helper". If you find evidence of compromise, immediately revoke credentials and rotate all secrets. Enable 2FA on all accounts and audit for suspicious federated credentials or cloud access keys created from GitHub workflows. Treat any affected developer machine as compromised and rotate its keys as well.

Read the full report at The Hacker News (opens in a new tab)

Why it matters

This attack shows how stealing developer credentials can lead to widespread theft of sensitive data from software projects. It highlights the risks of supply chain attacks and the importance of strong account security and regular secret rotation.

Key points

  1. Attackers hijacked 4,837 GitHub accounts to plant a secret stealer.
  2. At least 1,806 repositories had secrets stolen from CI workflows.
  3. Malicious commits were found in over 8,000 repositories.
  4. The attack targeted cloud credentials and other sensitive secrets.
  5. Immediate secret rotation and 2FA are recommended for affected users.

Sources

  1. The Hacker News

    Reference

The day's cyber news in 5 minutes.

Cyberend Daily is one short email with the stories that matter, written so anyone can follow.

Includes our free beginner roadmap · No spam · Unsubscribe anytime