You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Till now, tldr wiki has been open to edits from the community where anyone with a GitHub account can make changes like adding their client, etc. We had a spam edit in the past, which led to me integrating the wiki's Atom feed with Element's Feeds add-on to notify maintainers in our chatroom about the Wiki edits. While this worked as intended most of the time, it missed a few edits, and it's easy to miss in the active chatroom (like it occurred in the current case).
Incident
Coming back, on Saturday 26th of April 2025, a user edited our wiki, replacing its Home page with Crypto spam text.
This edit was discovered by @Managor (16 hours later) on 27th April, via the Feeds bot in the Chatroom, who brought it to my attention in the Chatroom.
Incident Response
I immediately restricted Wiki edits to collaborators only (something we have been discussing for a while across issues and in the chatroom) and reported the user to GitHub Trust & Safety team via a detailed write-up in GitHub support (and as of 28th the user's account has been taken down, will attach the email down below).
Then I cloned the repository and reverted the spam commit (along with Managor's test commit to see if collaborators can edit wiki) and force pushed it bringing it to the older state (since GitHub commit hashes are immutable the commit contents are still available at https://github.com/tldr-pages/tldr/wiki/Home/_compare/0636e7a65e6a598d5dfc7d67ef94d5aad1a9a1c9, even if the user got banned [Note: I have attached it here for reference purposes only, don't navigate to any links present there]).
Post-Remediation
Now that the Wiki edits are restricted to collaborators, I came back to discuss #12300 in the chatroom but using it will cause issues (if a collaborator edits the Wiki but not the file in repo and bidirectional actions aren't ideal from a security standpoint).
So for Wiki edits, I would like to propose creating an issue template and adding it to the header of Wiki pages to redirect client authors and users to the relevant place. What do you guys think of this?
Incident Report
Context
Till now, tldr wiki has been open to edits from the community where anyone with a GitHub account can make changes like adding their client, etc. We had a spam edit in the past, which led to me integrating the wiki's Atom feed with Element's Feeds add-on to notify maintainers in our chatroom about the Wiki edits. While this worked as intended most of the time, it missed a few edits, and it's easy to miss in the active chatroom (like it occurred in the current case).
Incident
Coming back, on Saturday 26th of April 2025, a user edited our wiki, replacing its Home page with Crypto spam text.
This edit was discovered by @Managor (16 hours later) on 27th April, via the Feeds bot in the Chatroom, who brought it to my attention in the Chatroom.
Incident Response
I immediately restricted Wiki edits to collaborators only (something we have been discussing for a while across issues and in the chatroom) and reported the user to GitHub Trust & Safety team via a detailed write-up in GitHub support (and as of 28th the user's account has been taken down, will attach the email down below).
tldr-wiki-spam-report.pdf
Remediation
Then I cloned the repository and reverted the spam commit (along with Managor's test commit to see if collaborators can edit wiki) and force pushed it bringing it to the older state (since GitHub commit hashes are immutable the commit contents are still available at https://github.com/tldr-pages/tldr/wiki/Home/_compare/0636e7a65e6a598d5dfc7d67ef94d5aad1a9a1c9, even if the user got banned [Note: I have attached it here for reference purposes only, don't navigate to any links present there]).
Post-Remediation
Now that the Wiki edits are restricted to collaborators, I came back to discuss #12300 in the chatroom but using it will cause issues (if a collaborator edits the Wiki but not the file in repo and bidirectional actions aren't ideal from a security standpoint).
So for Wiki edits, I would like to propose creating an issue template and adding it to the header of Wiki pages to redirect client authors and users to the relevant place. What do you guys think of this?
Related Issues
Closes #12300
The text was updated successfully, but these errors were encountered: