WhatBrokeToday
GTA 6FAQ
GitHub

GitHub Compromised Accounts and Repositories Targeted by CI Secret Stealer

critical

Is it fixed? Yes.

Resolved after <1 min. First reported Nov 12, 14:54 UTC, resolved Nov 12, 14:54 UTC. It never appeared on the vendor’s status page.

What happened

Researchers report that 4,837 compromised GitHub accounts were used to probe 61,764 repositories by inserting a CI secret stealer, reverting the code, and deleting workflow logs. This security incident is separate from the November 9 npm incident.

What caused it?

Under active investigation. No report has identified a root cause yet.

No verified workaround yet

This incident was resolved upstream without a reported workaround.

Timeline

  1. Investigating(done)
  2. Workaround available(skipped)
  3. Resolved(current)
  1. First report on Bluesky post

    GitHub again. Researchers report 4,837 compromised accounts probing 61,764 repositories. Attackers inserted a CI secret stealer, then reverted the code and deleted workflow logs. This is separate from the Nov 9 npm incident. #CyberSecurity

    Source
  2. Status changed

    Status changed: investigating → resolved (no new reports for 48h).

Evidence

1 report · 1 BlueskyShow
  1. [1]
    Bluesky First report
    GitHub again. Researchers report 4,837 compromised accounts probing 61,764 repositories. Attackers inserted a CI secret stealer, then reverted the code and deleted workflow logs. This is separate from the Nov 9 npm incident. #CyberSecurity(opens Bluesky post in a new tab)

    GitHub again. Researchers report 4,837 compromised accounts probing 61,764 repositories. Attackers inserted a CI secret stealer, then reverted the code and deleted workflow logs. This is separate from the Nov 9 npm incident. #CyberSecurity

    by inclinq.bsky.social 0upvotes 1comments

FAQ

What happened in the GitHub issue?

Researchers report that 4,837 compromised GitHub accounts were used to probe 61,764 repositories by inserting a CI secret stealer, reverting the code, and deleting workflow logs. This security incident is separate from the November 9 npm incident.

What is affected by the GitHub issue?

GitHub. Also affected at the same time: Fly.io.

When did the GitHub issue start and end?

It started Nov 12, 14:54 UTC and was resolved Nov 12, 14:54 UTC, after <1 min.

How do I get alerts for GitHub?

Subscribe to the GitHub RSS feed for every new GitHub incident, or connect an AI assistant to WhatBrokeToday over MCP and ask whether GitHub is down. GitHub feed

Where does this information come from?

WhatBrokeToday collects public status pages, developer community reports and security advisories, groups the ones about the same problem, and links every report under Evidence on this page. This one has 1 report from 1 independent source.