News for hackers. Stuff that matters.
Re:Wikipedia in read-only mode following mass admin account ... by tux3 on Thursday March 05, 2026 @01:24PM (#47265243)
See the public phab ticket: https://phabricator.wikimedia.org/T419143

In short, a Wikimedia Foundation account was doing some sort of test which involved loading a large number of user scripts. They decided to just start loading random user scripts, instead of creating some just for this test.

The user who ran this test is a Staff Security Engineer at WMF, and naturally they decided to do this test under their highly-privileged Wikimedia Foundation staff account, which has permissions to edit the global CSS and JS that runs on every page.

One of those random scripts was a 2 year old malicious script from ruwiki. This script injects itself in the global Javascript on every page, and then in the userscripts of any user that runs into it, so it started spreading and doing damage really fast. This triggered tons of alerts, until the decision was made to turn the Wiki read-only.

Re:Wikipedia in read-only mode following mass admin account ... by londons_explore on Thursday March 05, 2026 @01:41PM (#47265461)
Didn't realise this was some historic evil script and not some active attacker who could change tack at any moment.

That makes the fix pretty easy. Write a regex to detect the evil script, and revert every page to a historic version without the script.

Re:Wikipedia in read-only mode following mass admin account ... by jl6 on Thursday March 05, 2026 @04:12PM (#47267353)
Letting ancient evil code run? Have we learned nothing from A Fire Upon the Deep?!
Re:Wikipedia in read-only mode following mass admin account ... by edoceo on Thursday March 05, 2026 @04:48PM (#47267763)
I've only just heard of it. But, I already knew to not run random scripts under a privileged account. And thank you for the book suggestion - I'm into those kinds of tales.
Re:Wikipedia in read-only mode following mass admin account ... by HoldOnAMinute on Thursday March 05, 2026 @04:58PM (#47267877)
"It was really just humans playing with an old library. It should be safe, using their own automation, clean and benign.

This library wasn't a living creature, or even possessed of automation (which here might mean something more, far more, than human)."

Re:Wikipedia in read-only mode following mass admin account ... by varenc on Thursday March 05, 2026 @05:04PM (#47267941)
Link to the Prologue of Fire Upon the Deep: https://www.baen.com/Chapters/-0812515285/A_Fire_Upon_the_De...

It's very short and from one of my favorite books. Increasingly relevant.

Re:Wikipedia in read-only mode following mass admin account ... by iugtmkbdfil834 on Thursday March 05, 2026 @09:29PM (#47270093)
I swear, I respect Vinge more and more based on how well he seems to understand human tendencies to plot some plausible trajectories for our civilization.
Re:Wikipedia in read-only mode following mass admin account ... by Nition on Thursday March 05, 2026 @09:52PM (#47270254)
There's a little throwaway thing in the book (or maybe it was in the prequel) that I always liked, re understanding human tendencies. They're still using Unix time, starting in Jan 1st 1970, but given that their culture is so space-travel-focused they assume the early humans set it to coincide with man's first trip to the moon.
Re:Wikipedia in read-only mode following mass admin account ... by duskwuff on Friday March 06, 2026 @12:25AM (#47271209)
That's from the prequel, A Deepness in the Sky. (Which is also excellent.)
Re:Wikipedia in read-only mode following mass admin account ... by hinkley on Friday March 06, 2026 @01:57AM (#47271819)
Deepness in the Sky is probably the first Sci Fi alien I read who didn't feel like a human wearing an alien suit.

Fantasy sometimes does this better but usually with specific tropes.

Re:Wikipedia in read-only mode following mass admin account ... by aerique on Friday March 06, 2026 @11:36AM (#47277235)
If you liked that and you haven't read it yet, give "Dragon's Egg" by Robert L. Forward a read.
Re:Wikipedia in read-only mode following mass admin account ... by HoldOnAMinute on Saturday March 07, 2026 @10:53AM (#47288706)
I wish he could have seen the current state of GenAI. Several times in the book he talks about how the ship understands context clues and sarcasm, and that effective natural language translation requires near-sentience.
Re:Wikipedia in read-only mode following mass admin account ... by xeromal on Thursday March 05, 2026 @05:15PM (#47268050)
I love that book
Re:Wikipedia in read-only mode following mass admin account ... by NBJack on Thursday March 05, 2026 @07:37PM (#47269239)
Legitimately listening to this book for the first time after a coworker recommended it. It's rapidly becoming one of my favorite books that balances the truly alien with the familiar just right.

Not so ironically, it came up when we were discussing "software archeology".

Re:Wikipedia in read-only mode following mass admin account ... by 12_throw_away on Thursday March 05, 2026 @07:52PM (#47269363)
\(^O^)/ zones of thought mentioned \(^O^)/
Re:Wikipedia in read-only mode following mass admin account ... by HoldOnAMinute on Saturday March 07, 2026 @10:55AM (#47288724)
Do you remember the part where they built a machine in the Transcend that had to work at the Bottom of the Beyond?

The other day I was using Claude for a task, but it occurred to me, what if Claude is unreachable.

So, I told it to "encode your wisdom into this script in case you are not available"

That was my own version of that

Re:Wikipedia in read-only mode following mass admin account ... by hinkley on Friday March 06, 2026 @01:55AM (#47271804)
Army of Darkness?

The Mummy?

Re:Wikipedia in read-only mode following mass admin account ... by monista on Friday March 06, 2026 @06:59AM (#47273898)
Learning from fiction? Let's learn from the Dune then and start Butlerian jihad already.
Re:Wikipedia in read-only mode following mass admin account ... by jacquesm on Thursday March 05, 2026 @02:23PM (#47266059)
True but it does say something that such a script was able to lie dormant for so long.
Re:Wikipedia in read-only mode following mass admin account ... by outofpaper on Thursday March 05, 2026 @03:48PM (#47267072)
Why would anyone test in production???!!!
Re:Wikipedia in read-only mode following mass admin account ... by fifilura on Thursday March 05, 2026 @03:53PM (#47267129)
I have never heard of this kind of insane behaviour before.
Re:Wikipedia in read-only mode following mass admin account ... by ninth_ant on Thursday March 05, 2026 @04:34PM (#47267611)
Selecting the wrong environment in your test setup by mistake?

I refuse to believe that someone on the security team intentionally tested random user scripts in production on purpose.

Re:Wikipedia in read-only mode following mass admin account ... by withinboredom on Thursday March 05, 2026 @05:45PM (#47268305)
Once you get big enough… there comes a point where you need to run some code and learn what happens when 100 million people hitting it at once looks like. At that scale, “1 in a million class bugs/race conditions” literally happen every day. You can’t do that on every PR, so you ship it and prepare to roll back if anything even starts to look fishy. Maybe even just roll it out gradually.

At least, that’s how it worked at literally every big company I worked at so far. The only reason to hold it back is during testing/review. Once enough humans look at it, you release and watch metrics like a hawk.

And yeah, many features were released this way, often gated behind feature flags to control roll out. When I refactored our email system that sent over a billion notifications a month, it was nerve wracking. You can’t unsend an email and it would likely be hundreds of millions sent before we noticed a problem at scale.

Re:Wikipedia in read-only mode following mass admin account ... by ghxst on Thursday March 05, 2026 @06:28PM (#47268677)
I would say you can get to this point far below 100 million people, especially on web. Some people are truly special and have some kind of setup you just can't easily reproduce. But I agree, you do really have to be confident in your ability to control rollout / blast radius, monitor and revert if needed.
Re:Wikipedia in read-only mode following mass admin account ... by ninth_ant on Friday March 06, 2026 @12:25PM (#47278090)
Yes this is a common release practice.

However this is a different situation as we’re talking about running arbitrarily found third-party scripts. I can’t imagine that was ever intended to be done in production.

Fun story, when I worked at Facebook in the earlier days someone accidentally made a change that effectively set the release flags for every single feature to be live on production. That was a day… we had to completely wipe out memcached to stop the broken features and then the database was hammered to all hell.

Re:Wikipedia in read-only mode following mass admin account ... by irishcoffee on Thursday March 05, 2026 @04:54PM (#47267836)
> I refuse to believe that someone on the security team intentionally tested random user scripts in production on purpose.

Do I have a bridge to sell you, oh boy

Re:Wikipedia in read-only mode following mass admin account ... by HoldOnAMinute on Thursday March 05, 2026 @04:59PM (#47267889)
There are plenty of ways to safely test in production. For one thing you need to limit the scope of your changes.
Re:Wikipedia in read-only mode following mass admin account ... by kQq9oHeAz6wLLS on Thursday March 05, 2026 @07:50PM (#47269340)
"Everyone has a test environment. Some are lucky enough to have a separate production environment."
Re:Wikipedia in read-only mode following mass admin account ... by observationist on Thursday March 05, 2026 @04:55PM (#47267851)
Are you sure? Are you $150 million ARR sure? Are you $150 million ARR, you'd really like to keep your job, you're not going to accidentally leave a hole or blow up something else, sure?

I agree, mostly, but I'm also really glad I don't have to put out this fire. Cheering them on from the sidelines, though!

Re:Wikipedia in read-only mode following mass admin account ... by hinkley on Friday March 06, 2026 @02:03AM (#47271872)
Honestly, since I'm never really in a position to see much of that money, at this point I'd be more concerned about my coworkers. And while that typically correlates with the amount of money you either have or receive, they're often out of balance one way or the other.
Re:Wikipedia in read-only mode following mass admin account ... by Melatonic on Thursday March 05, 2026 @05:17PM (#47268082)
Or just restore from backup across the board. Assuming they do their backups well this shouldn't be too hard (especially since its currently in Read Only mode which means no new updates)
Re:Wikipedia in read-only mode following mass admin account ... by karel-3d on Thursday March 05, 2026 @03:07PM (#47266608)
wait as a wikipedia user you can just put random JS to some settings and it will just... run? privileged?

this is both really cool and really really insane

Re:Wikipedia in read-only mode following mass admin account ... by kemayo on Thursday March 05, 2026 @03:15PM (#47266710)
It's a mediawiki feature: there's a set of pages that get treated as JS/CSS and shown for either all users or specifically you. You do need to be an admin to edit the ones that get shown to all users.

https://www.mediawiki.org/wiki/Manual:Interface/JavaScript

Re:Wikipedia in read-only mode following mass admin account ... by hk__2 on Thursday March 05, 2026 @03:09PM (#47266638)
Yes, you can have your own JS/CSS that’s injected in every page. This is pretty useful for widgets, editing tools, or to customize the website’s apparence.
Re:Wikipedia in read-only mode following mass admin account ... by karel-3d on Thursday March 05, 2026 @03:32PM (#47266898)
It sounds very dangerous to me but who am I to judge.
Re:Wikipedia in read-only mode following mass admin account ... by Brian_K_White on Thursday March 05, 2026 @03:56PM (#47267164)
It's nothing.

For the global ones that need admin permissions to edit, it's no different from all the other code of mediawiki itself like the php.

For the user scripts, it's no worse than the fact that you can run tampermonkey in your browser and have it modify every page from evry site in whatever way your want.

Re:Wikipedia in read-only mode following mass admin account ... by karel-3d on Friday March 06, 2026 @01:21AM (#47271573)
Well it has just been shown it's not nothing
Re:Wikipedia in read-only mode following mass admin account ... by Brian_K_White on Friday March 06, 2026 @07:29AM (#47274169)
No it hasn't.
Re:Wikipedia in read-only mode following mass admin account ... by corndoge on Thursday March 05, 2026 @03:42PM (#47267011)
That is how Mediawiki works. Everything is a page, including CSS and JS. It is not really different than including JS in a webpage anywhere else.
Re:Wikipedia in read-only mode following mass admin account ... by bawolff on Thursday March 05, 2026 @05:16PM (#47268065)
It is kind of risky - you now have an entire, mostly unreviewed, ecosystem of javascript code, that users can experiment with.

However its been really useful to allow power users to customize the interface to their needs. It also is sort of a pressure release for when official devs are too slow for meeting needs. At this point wikipedia has become very dependent on it.

Re:Wikipedia in read-only mode following mass admin account ... by hk__2 on Friday March 06, 2026 @05:42AM (#47273300)
It only affects your user; it’s just like adding random extensions to your browser.
Re:Wikipedia in read-only mode following mass admin account ... by Ekaros on Friday March 06, 2026 @03:02AM (#47272276)
Fundamentally I feel whole "web" as in anything running in browser is insane an broken security wise. When you allow mostly arbitrary code to run when you load a page... Well it can do mostly arbitrary things and everyone else needs to protect against it.

And when you have enough rights, you get to add arbitrary code to everywhere on your site.

Re:Wikipedia in read-only mode following mass admin account ... by Ferret7446 on Thursday March 05, 2026 @04:31PM (#47267579)
This is a pretty egregious failure for a staff security engineer
Re:Wikipedia in read-only mode following mass admin account ... by ljm on Thursday March 05, 2026 @07:33PM (#47269204)
It's a pretty egregious failure for the org because it controlled the conditions for it to happen.

The security guy is just the patsy because he actioned it.

They have obviously done this a million times before and now they got burned.

Re:Wikipedia in read-only mode following mass admin account ... by sonofhans on Thursday March 05, 2026 @07:55PM (#47269380)
Yes, this. That same engineer shouldn’t have a pocket nuclear trigger shaped just like their key fob, either. Humans are predictable.
Re:Wikipedia in read-only mode following mass admin account ... by throwaway894345 on Thursday March 05, 2026 @10:44PM (#47270597)
Aren’t staff part of engineering leadership?
Re:Wikipedia in read-only mode following mass admin account ... by wmichelin on Friday March 06, 2026 @09:05AM (#47275042)
At my job, I would just say they are in the ear of engineering leadership, but are not part of it.
Re:Wikipedia in read-only mode following mass admin account ... by throwaway894345 on Saturday March 07, 2026 @07:16AM (#47286971)
That makes sense. I guess I usually think of developing policies for this kind of thing to be pretty much what staff would do. I don’t usually expect the CTO to make decisions about how to do testing. To the extent the engineering leadership are to blame, it’s that they were the ones who hired/retained this guy. The buck ultimately stops with them to be sure, but making these kinds of policies seems within the remit of a staff eng.
Re:Wikipedia in read-only mode following mass admin account ... by mcmcmc on Thursday March 05, 2026 @04:48PM (#47267765)
Pretty much the definition of a “career limiting event”
Re:Wikipedia in read-only mode following mass admin account ... by modderation on Thursday March 05, 2026 @05:31PM (#47268192)
It's either a a Career Limiting Event, or a Career Learning event.

In the case of a Learning event, you keep your job, and take the time to make the environment more resilient to this kind of issue.

In the case of a Limiting event, you lose your job, and get hired somewhere else for significantly better pay, and make the new environment more resilient to this kind of issue.

Hopefully the Wikimedia foundation is the former.

Re:Wikipedia in read-only mode following mass admin account ... by the_af on Thursday March 05, 2026 @06:18PM (#47268591)
In the average real world, the staff engineer learns nothing, regardless of whether they get to lose or keep their job. Some time down the line, they make other careless mistakes. Eventually they retire, having learned nothing.

This is more common than you'd think.

Re:Wikipedia in read-only mode following mass admin account ... by cjbgkagh on Thursday March 05, 2026 @09:09PM (#47269957)
I was able to run some stats at scale on this and people who make mistakes are more likely to make more mistakes, not less. Essentially sampling from a distribution of a propensity for mistakes and this dominated any sign of learning from mistakes. Someone who repeatedly makes mistakes is not repeatedly learning, they are accident prone.
Re:Wikipedia in read-only mode following mass admin account ... by Dibby053 on Thursday March 05, 2026 @11:22PM (#47270844)
Can you elaborate? What scale? What kind of mistakes? This sounds quite interesting.
Re:Wikipedia in read-only mode following mass admin account ... by cjbgkagh on Friday March 06, 2026 @09:43AM (#47275494)
A decade of data from many hundreds of people, help desk type roll where all communication was kept, mostly chat logs and emails. Machine learning with manual validation. The goal was to put a dollar figure on mistakes made since the customers were much more likely to quit and never come back if it was our fault, but also many customers are nothing but a constant pain in the ass so it was important to distinguish who was right whenever there was a conflict.

Mistakes made per call, like many things, were on a Pareto distribution, so 90% of the mistakes are made by 10% of the people. Identifying and firing those 10% made a huge difference. Some of the ‘mistakes’ were actually a result of corruption and they had management backing as management was enriching themselves at the cost of the company (a pretty common problem) so the initiative was killed after the first round.

Re:Wikipedia in read-only mode following mass admin account ... by schuyler2d on Friday March 06, 2026 @04:10PM (#47281109)
This sounds really interesting but possibly qualitatively different than programming/engineering where automated improvements/iterations are part of the job (and what's rewarded)
Re:Wikipedia in read-only mode following mass admin account ... by lolive on Thursday March 05, 2026 @10:13PM (#47270392)
What if you define a hard rule from this statistics that « you must fire anyone on error one »? Won’t your company be empty in a rather short timeframe? [or will be composed only of doingNothing people?]
Re:Wikipedia in read-only mode following mass admin account ... by cjbgkagh on Thursday March 05, 2026 @10:23PM (#47270458)
Why would you do that? You’re sampling from a distribution, a single sample only carries a small amount of information, repeat samples compound though.
Re:Wikipedia in read-only mode following mass admin account ... by jstanley on Friday March 06, 2026 @03:47AM (#47272568)
My impression of mistakes was that they were an indicator of someone who was doing a lot of work. They're not necessarily making mistakes at a higher rate per unit of work, they just do more of both per unit of time.

From that perspective, it makes sense that the people who made the most mistakes in the past will also make the most mistakes in the future, but it's only because the people who did the most work in the past will do the most work in the future.

If you fire everyone who makes mistakes you'll be left only with the people who never make anything at all.

Re:Wikipedia in read-only mode following mass admin account ... by cjbgkagh on Friday March 06, 2026 @10:00AM (#47275684)
In this case it was trivial to normalize for work done.

It’s very human to want to be forgiving of mistakes, after all who has not made any mistakes, but there are different classes of mistakes made by all different types of people. If you make a mistake you are the same type of person, but if you are pulling from a distribution by sampling by those who have made mistakes you are biasing your sample in favor of those prone to making such mistakes. In my experience any effect of learning is much smaller than this initial bias.

Re:Wikipedia in read-only mode following mass admin account ... by Angostura on Friday March 06, 2026 @06:47AM (#47273815)
Or they are working in a very badly designed system which consistently encourages them to make mistakes
Re:Wikipedia in read-only mode following mass admin account ... by gorgoiler on Friday March 06, 2026 @01:04AM (#47271456)
Realistically, there’s a third option which it would be glib to not consider: you lose your job, get hired somewhere else, and screw up in some novel and highly avoidable way because deep down you aren’t as diligent or detail-oriented as you think you are.
Re:Wikipedia in read-only mode following mass admin account ... by mock-possum on Friday March 06, 2026 @03:55AM (#47272630)
This is the most likely outcome
Re:Wikipedia in read-only mode following mass admin account ... by xvector on Thursday March 05, 2026 @05:02PM (#47267922)
They'll be fine, recruiters don't look this stuff up and generally background checks only care about illegal shit.
Re:Wikipedia in read-only mode following mass admin account ... by radicaldreamer on Thursday March 05, 2026 @05:13PM (#47268031)
Nobody is going to know who did this, so probably not career limiting in any major way.
Re:Wikipedia in read-only mode following mass admin account ... by xeromal on Thursday March 05, 2026 @05:20PM (#47268097)
They named him in the support ticket linked here somewhere.

> sbassett

[dead]
Re:Wikipedia in read-only mode following mass admin account ... by adxl on Thursday March 05, 2026 @04:55PM (#47267842)
Is ok, the AI was going to replace them in a few weeks anyway.
Re:Wikipedia in read-only mode following mass admin account ... by type0 on Friday March 06, 2026 @12:41AM (#47271303)
With all their donation begging, nothing will change, they will still spend money on useless seminars and continue to underfund security by hiring low paid web amateurs to do the important work
Re:Wikipedia in read-only mode following mass admin account ... by greatgib on Friday March 06, 2026 @05:30AM (#47273223)
As a staff, you don't even imagine what his salary is for screwing up like that.

That being said, interesting to see how salaries skyrocketed over the years: https://meta.wikimedia.org/wiki/Wikimedia_Foundation_salarie... but not that much for engineering.

Re:Wikipedia in read-only mode following mass admin account ... by BorisMelnik on Friday March 06, 2026 @09:24AM (#47275254)
that's insane...I am not donating anymore (not that I gave that much.)
Re:Wikipedia in read-only mode following mass admin account ... by sehansen on Tuesday March 10, 2026 @09:50AM (#47323232)
The highest non-severance number is $512,179 for the CEO in 2022. That's not particularly extreme. It's ~1/10 of what the Mozilla Foundation CEO makes.
Re:Wikipedia in read-only mode following mass admin account ... by AlienRobot on Thursday March 05, 2026 @04:35PM (#47267619)
On one hand, I was about to get irrationally angry someone was attacking Wikipedia, so I'm a bit relieved

On the other hand,

>a Staff Security Engineer at WMF, and naturally they decided to do this test under their highly-privileged Wikimedia Foundation staff account

seriously?

Re:Wikipedia in read-only mode following mass admin account ... by streetfighter64 on Thursday March 05, 2026 @07:00PM (#47268932)
To paraphrase Bush,

> our enemies are innovative and resourceful, and so are we. They never stop thinking about new ways to harm our site and our users, and neither do we.

Re:Wikipedia in read-only mode following mass admin account ... by davidd_1004 on Thursday March 05, 2026 @04:48PM (#47267771)
300 million dollar organization btw
Re:Wikipedia in read-only mode following mass admin account ... by aiiane on Thursday March 05, 2026 @08:08PM (#47269485)
aka tiny, relatively speaking, compared to similar sites with the same user base
Re:Wikipedia in read-only mode following mass admin account ... by Fokamul on Thursday March 05, 2026 @04:54PM (#47267831)
I'm guessing, "1> Hey Claude, your script ran this malicious script!"

"Claude> Yes, you're absolutely right! I'm sorry!"

Re:Wikipedia in read-only mode following mass admin account ... by cesarb on Thursday March 05, 2026 @05:51PM (#47268360)
> One of those random scripts was a 2 year old malicious script from ruwiki. This script injects itself in the global Javascript on every page, and then in the userscripts of any user that runs into it, so it started spreading and doing damage really fast.

So, like the Samy worm? (https://en.wikipedia.org/wiki/Samy_%28computer_worm%29)

Re:Wikipedia in read-only mode following mass admin account ... by amai on Friday March 06, 2026 @08:11AM (#47274521)
Why am I not surprised that the malicious script was from ruwiki?
Re:Wikipedia in read-only mode following mass admin account ... by cc-d on Friday March 06, 2026 @09:21AM (#47275217)
this was us. we pumpin hard. we literall run, as in literally run the organisms of, senior wikimedia staff as well as employees

this is just us playing on the computer, we got b0mbz

Re:Wikipedia in read-only mode following mass admin account ... by chuckreynolds on Friday March 06, 2026 @10:41AM (#47276362)
...wow.
Re:Wikipedia in read-only mode following mass admin account ... by mos87 on Saturday March 07, 2026 @02:34AM (#47285389)
>they decided to do this test under their

what language is this?