We must protect wikipedia, they’re our only safe place right now.
Ya tonight Im gonna start torrenting one of the backups. I don’t normally seed more than 2x ratio but I think this one will be set to trickle seed and stay on for at least 10x
please do if you have the storage space and bandwith
Oh, fuck, this is going to be interesting to read about. Just to clarify: it seems like this wasn’t just Wikipedia but Wikimedia generally. So that’s also e.g. Wiktionary, Wikimedia Commons, Wikidata, etc.
Edit: Decided to check Reddit, and someone posted an ostensibly good summary on /r/wikipedia.
Shameless copy/paste of the main info if anyone wants to catch a glimpse without going to reddit :
Summary of events:
On 5 March 2026, a Wikimedia Foundation employee accidentally imported a malicious script to his account on Meta-Wiki while testing global API limits for user scripts (see his global.js page history). The malicious script was created in 2023 to attack two Russian-language alternative wiki projects, Wikireality and Cyclopedia. In 2024, user Ololoshka562 created a page on the Russian Wikipedia containing the script used in these attacks. The script, which had been sitting dormant on ruwiki for 1.5 years, then spread to several accounts on Meta, including WMFOffice, and mass-deleted pages in namespaces 0–3, leaving behind an edit summary of “Закрываем проект”, Russian for “Closing the project”. The staff member, as a global interface administrator, has permission to edit meta:MediaWiki:Common.js, which allowed the script to infect any user who visited Meta-Wiki while it was active. To prevent the script from spreading further, all Wikimedia projects were set to read-only for about 2 hours, and all user JavaScript was temporarily disabled.
Post from WMF staff member on Discord:
Hey all - as some of you have seen, we (WMF) were doing a security review of the behavior of user scripts, and unintentionally activated one that turned out to be malicious. That is what caused the page deletions you saw on the Meta log, which are getting cleaned up. We have no reason to believe any third-party entity was actively attacking us today, or that any permanent damage occurred or any breach of personal information.
We were doing this security review as part of an effort to limit the risks of exactly this kind of attack. The irony of us triggering this script while doing so is not lost on us, and we are sorry about the disruption. But the risks in this system are real. We are going to continue working on security protections for user scripts – in close consultation with the community, of course – to make this sort of thing much harder to happen in the future.
Ironically it is comments like these that led to Reddit gold. But thank you kind stranger for saving me having to descend into The Depths for this.
To be fair I would assume that it’s better to trigger something like this during a security review when people are actively “online” and focused on security risks than at some other time.
Absolutely and it helped prove why they needed to do this security review to begin with as well as will teach them the nature of how this user script worked so they can put up guardrails for this specific type of attack. An unfortunate event but as long as they are using it to learn from and strengthen their security, overall it’s a good thing.
That’s hilarious, and I cannot imagine how stressed out that employee is.
After that kind of learning experience that employee needs a reprimand and a raise in that order. You can bet that shit won’t happen twice! 😆
You want even more Management?? 😨
Raise and promotion are not synonyms.
Danke. This should easily be fine for anyone who’s slightly-to-moderately interested; some of the nitty-gritty details like hyperlinks to the edit diffs are excluded from this copy–paste for those who really know their stuff and want to learn more.
“The malicious script was created in 2023 to attack two Russian-language alternative wiki projects, Wikireality and Cyclopedia.”
So this was a US/Ukrainian attack on Russia that backfired ?? Weird ‘friendly fire’ situation…
