Documented case · 2025
Cantue35
2025
Verified primary source
The account holder's own post, discussion or thread was opened and read in full for this entry.
His security log showed the same IP and the same device; he found no infostealer malware on his Mac; two-factor authentication had been enabled for years. After the forced password reset he could log in again, but the account remained invisible to the public, the flag without the suspension. He maintains a public blocklist repo, and for about 29 days it and he were simply not there. His update in the discussion records the reinstatement; nothing in it names a cause.
The record
- Suspended or flagged
- 2025, the day after a push to a fork and a new token
- Posted
- GitHub Community discussion #162607, 2025
- Ticket / discussion
- Discussion #162607; no ticket number published
- Suspected trigger
- Not stated. The sequence he reports: he pushed to a fork to resolve a merge conflict shortly after creating a new personal access token, and then an email arrived: "Password reset notification due to suspicious activity"
- Human reply from GitHub
- Yes, eventually: after about 29 days the ticket was reviewed and the account reinstated. The discussion itself had been hidden while he was suspended
- How it ended
- Reinstated after about 29 days
- Duration
- Under 1 month
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 #162607 by Cantue35; opened and checked 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.