Never restored
As of 2026-11-17

All 66 cases

Documented case · 2026

nicoandmee (Nico Kokonas)

About Jan 2026

Never restoredNot stated; permanent banCode access lost / 404Reputation / visibility

Verified primary source

The account holder's own post, discussion or thread was opened and read in full for this entry.

Permanently banned without warning, losing an entire GitHub history that goes back to age fourteen; he has contributed to infosec open source since he was fourteen. If his inference about the cause is right, the mechanism is the bleakest in this explorer: a fraud victim reversed fraudulent charges, a legitimate Copilot charge was swept up in the reversal, and the system treated the chargeback as the fraud. There was no channel in which to explain the difference.

The record

Suspended or flagged
About January 2026
Posted
Hacker News, January 2026; corroborating note on his SourceHut page, January 2026
Ticket / discussion
None published
Suspected trigger
His inference, reached after fighting through tickets: a chargeback tied to GitHub Copilot during a fraud dispute. Fraudulent charges on his card were reversed, the Copilot charges were reversed with them, and the automated system read it as intentional fraud
Human reply from GitHub
No effective route: his post's summary is "No warning. No appeal process. No way to distinguish fraud victims from bad actors."
How it ended
Permanently banned, unresolved at posting. A note on his SourceHut page from January 2026 reads "currently banned from GitHub pending reinstatement"
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 post by Nico Kokonas, Hacker News item 46602838; read via search text on November 17, 2026.

Cause is the author's own stated inference, uncorroborated by GitHub.

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.