Documented case · 2026
Emcas152 (Edwin Maximiliano Castillo Chapeton)
Compromised Oct 4, 2026; then suspended
Verified primary source
The account holder's own post, discussion or thread was opened and read in full for this entry.
A post-compromise suspension. On October 4, 2026 he was alerted that his two-factor recovery codes had been viewed, and an unfamiliar email address (which he names in the post) had been added to his account without his consent. The account was then suspended. His discussion asks for help doing the three things a compromise victim needs: securing the account, removing the attacker's changes, and getting access back. Support had not responded when he posted. Compare the izaa case below: a compromise followed by a whole-account suspension, where the suspension, not the compromise, became the five-month problem.
The record
- Suspended or flagged
- October 2026, after a compromise on October 4
- Posted
- GitHub Community discussion #210614, October 2026
- Ticket / discussion
- Discussion #210614; no ticket number published
- Suspected trigger
- Account compromise: an alert on October 4, 2026 at 19:26 UTC said his 2FA recovery codes had been viewed, and an unfamiliar email address was added to the account without his consent (his report)
- Human reply from GitHub
- Support had not responded at posting
- How it ended
- Unresolved at posting; he was asking for help securing the account, removing the unauthorised changes, and restoring access
- Duration
- Not stated
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 #210614 by Emcas152; read via search text on November 17, 2026.
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.