Documented case · 2022
Marak Squires (faker.js / colors.js)
Jan 2022
Verified primary source
The account holder's own post, discussion or thread was opened and read in full for this entry.
The clearest known-cause entry in the explorer. After Marak Squires deliberately sabotaged two of the most-downloaded packages in the JavaScript ecosystem, GitHub suspended his account and npm reverted the packages. Whatever one thinks of his protest, the suspension had a stated basis in his own admitted act. It is here as the control case: this is what an explained suspension looks like, and almost nothing else in this explorer resembles it.
GitHub, in its own words
"We remove the malicious packages and suspend the user account in accordance with npm's Acceptable Use Policy regarding malware."
The record
- Suspended or flagged
- January 2022
- Posted
- Hacker News and news reports, January 2022
- Ticket / discussion
- Not applicable
- Suspected trigger
- Known cause, not a false positive: he had intentionally corrupted his own libraries, faker.js (v6.6.6) and colors.js (v1.4.44-liberty-2, with an infinite loop)
- Human reply from GitHub
- GitHub issued a public statement (below)
- How it ended
- Account restored within days; npm reverted the corrupted packages
- 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
Hacker News item 29837473 and news reporting, January 2022; checked November 17, 2026.
Contrast entry: deliberate sabotage, not a false positive.
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.