Skip to content
NewA calmer, faster ZeroHour

Hijacked GitHub accounts planted a CI secret stealer in 1,806+ repos

Original title: Attacker Used 4,837 Hijacked GitHub Accounts to Run a CI Secret Stealer in 1,806+ Repositories

The Hacker News ()6 min read
Part of a story covered by 9 sourcesStolen GitHub tokens used to steal CI secrets from 1,800+ reposMerged summary & timeline
AI summary · x-ai/grok-4.7Summaries by Vani AI

Stolen credentials for 4,837 accounts opened test pull requests in 61,764 repositories, Aikido Security says.

Starting Tuesday, an attacker used stolen credentials for 4,837 GitHub accounts to plant a secret stealer in repositories those accounts could write to, according to Aikido Security. The stealer ran in at least 1,806 repositories and is built to collect CI secrets, cloud credentials, and tokens, then keep access after rotation. SafeDep counted malicious commits in 8,093 public default-branch repositories. How the credentials were obtained is not explained.

Unconfirmed: Aikido and SafeDep report different repository counts, and the source of the stolen credentials is unknown.

Key facts
  • Test pull requests used the title "docs: dependency audit notes" and branch wfx-docs.
  • In 771 repositories the payload arrived as an npm postinstall hook.
  • The attacker often reverted changes within minutes and deleted workflow logs.
  • About a fifth of a 200-commit sample exfiltrated through Telegram only.
  • Persistence includes AWS trust-policy changes and Azure credentials named wfx-ci-*.
Security assessment · AI, from the article

Impact: CI secrets, cloud credentials, and workflow tokens stolen

ProductAffected
GitHub—
What to do
  1. 1.Revoke the commit author's tokens, OAuth grants, SSH keys, and sessions, and enable 2FA.
  2. 2.Rotate every secret and variable the affected repository can read.
  3. 3.Check Entra ID, AWS, GCP, and Vault for wfx-ci-* or wfx-* backdoors.
Analyze this story with Vani AIImpact, who is affected and what defenders should do, in a new chat

Indicators of compromise

auto-extracted · verify before use · export allAll
TypeIndicatorContext
ipv4153.75.82.159150.166[.]244:8080/exfil IP: 18.143.168[.]96:8080/exfil IP: 153.75.82[.]159:8080 A repository can show no wfx-loot artifacts, wfx- ca
ipv418.143.168.96ed7173c2a2816c762735cf IP: 194.150.166[.]244:8080/exfil IP: 18.143.168[.]96:8080/exfil IP: 153.75.82[.]159:8080 A repository can show
ipv4194.150.166.24492d5cfd4972672961e644bb46baa98aa1ed7173c2a2816c762735cf IP: 194.150.166[.]244:8080/exfil IP: 18.143.168[.]96:8080/exfil IP: 153.75.82[.
sha25689695abb392d5cfd4972672961e644bb46baa98aa1ed7173c2a2816c762735cfstore Commit message: ci: cleanup SHA-256 (stealer script): 89695abb392d5cfd4972672961e644bb46baa98aa1ed7173c2a2816c762735cf IP: 194.150.166[.]244:8080/exfil IP: 18.143.168[.]96:8080/e

From the original article

6 min read at thehackernews.com

Starting Tuesday, an attacker used stolen credentials for 4,837 GitHub accounts to plant a secret stealer in repositories those accounts could write to, according to Aikido Security, a security software company. The stealer is built to take the secrets and cloud credentials that a repository's CI workflows can reach. It ran in at least 1,806 repositories, where the attacker has likely collected

The Hacker News

thehackernews.com

Read the full article at The Hacker News

A short excerpt; the article and its images belong to the publisher. Summary, key facts and assessment above are AI-written from the article and can be wrong.