mikehenken/writing/github-account-suspended/cases/emu-scim-deprovisioning-bug
Partially restored
As of 2026-11-17

All 66 cases

Documented case · 2026

EMU SCIM deprovisioning bug, about 12,285 enterprise accounts

Jun 1 to 13, 2026; records restored Oct 2026

Partially restoredAbout 4 months to record restorationCode access lost / 404

Secondary source

The details here rest on another site's summary of the case, not on the account holder's own post.

Included separately because the mechanism is different and the scale is not. For thirteen days in June 2026, some enterprise accounts that should have been suspended through SCIM deprovisioning were deleted outright, about 12,285 of them across multiple enterprises, leaving ghost users and broken audit trails. GitHub's changelog acknowledged it, and the records were put back in October 2026, restored to the state they should have been in, which for a deprovisioned account means suspended, not active. It is the largest single incident in this explorer by two orders of magnitude, and it is here as a scale marker, not as another abuse-detection case.

The record

Suspended or flagged
June 1 to 13, 2026
Posted
GitHub changelog, summarised October 23, 2026
Ticket / discussion
Not applicable: a platform bug, not individual tickets
Suspected trigger
A provisioning bug, not abuse detection: Enterprise Managed User accounts deprovisioned through SCIM were deleted instead of being suspended and obfuscated as designed
Human reply from GitHub
Not applicable at the individual level
How it ended
The roughly 12,285 affected account records were restored in October 2026 to their expected suspended or obfuscated state. They were not reactivated
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

Secondary summary (Windows Forum, October 23, 2026) of GitHub's own changelog notice; the changelog itself was not opened in research.

Different mechanism: a provisioning bug, not an abuse-detection flag. Secondary summary of GitHub's changelog.

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.