Documented case · 2026
izaa (also @iirokulku / @interqueoy)
Suspended Apr 2026; restored Sep 7, 2026
Verified primary source
The account holder's own post, discussion or thread was opened and read in full for this entry.
Suspended in April 2026 without warning. GitHub said the account had been "taking part in activity which goes against our Terms of Service," specifically Actions used for third-party interactions and general-purpose computing. What had actually happened, on his account and corroborated by the public GhostAction reporting, was a compromise: his token was stolen and used to inject a secret-stealing workflow, which he found, revoked, and cleaned up himself before the suspension. His GDPR request of April 25, 2026 (Articles 15, 20, 22) got a templated reply after 25 days pointing at sign-in-required self-service. He complained to the Finnish Data Protection Ombudsman under Article 77. The authority's first two inquiries were ignored. On the third contact, in early September 2026, GitHub replied in writing, admitting a bug in its support intake system had prevented requests from reaching staff (fixed May 1, 2026), and an internal routing error at its privacy address meant correspondence was received but not escalated. The account was restored on September 7, about five months in.
GitHub, in its own words
"The complainant's experience did not meet our standard of service or our established process for handling data subject rights requests" (GitHub to the Finnish Ombudsman, as quoted in his post).
The record
- Suspended or flagged
- April 2026
- Posted
- GitHub Community discussion #170974, 2026
- Ticket / discussion
- Three Support tickets under "Account restrictions," plus the reinstatement form; then a GDPR request and a regulator complaint
- Suspected trigger
- A compromised personal access token. An attacker injected a credential-exfiltration workflow sending secrets to *.oast.fun, part of the GhostAction campaign (GitGuardian, September 5, 2025: 327 users, 817 repos, 3,325 secrets). He detected it, revoked the token, removed the code, and contacted Support, and then the whole account was suspended. GitHub later told the regulator the account had been flagged as part of a wider account-takeover campaign
- Human reply from GitHub
- Only via the regulator. Three tickets and the reinstatement form drew identical word-for-word automated responses, then were closed as "cannot be reopened"; replying by email was blocked
- How it ended
- Restored September 7, 2026, after the Finnish Data Protection Ombudsman escalated and a staff member actually reviewed the account
- Duration
- Over 3 months
Suspected triggers are the account holder’s inference, never GitHub-confirmed, unless the record above says GitHub stated or confirmed it. A suspension does not by itself prove GitHub made a mistake.
Sources
First-hand GitHub Community discussion #170974 by izaa; opened and checked November 17, 2026.
GitHub admitted a support-intake bug and a privacy routing error in this case, in writing, to a regulator.
This entry is one of 66 in What Kind of Life Does a Flag Preserve?, a documented account of GitHub suspending a fourteen-year-old developer account and the same pattern repeating across the industry. If the same thing has happened to you, the article’s eight-step playbook is built from what actually moved these cases.