News for hackers. Stuff that matters.
Re:Wikipedia in read-only mode following mass admin account ... by epicprogrammer on Thursday March 05, 2026 @12:10PM (#47264249)
This is basically a weaponized, highly destructive version of the old MySpace Samy worm. Hitting MediaWiki:Common.js is the absolute nightmare scenario for MediaWiki deployments because that script gets executed by literally every single visitor and editor across the entire site, creating a massive, instant propagation loop. The fact that it specifically targets admins and then uses jQuery to blind them by hiding the UI elements while it silently triggers Special:Nuke in the background is incredibly insidious. It really exposes the foundational danger of legacy web architectures that still allow executable JavaScript to be stored and served directly from user-editable namespaces. Cleaning this up is going to be an absolute forensic nightmare for the Wikimedia team since the database history itself is the active distribution vector.
Re:Wikipedia in read-only mode following mass admin account ... by devmor on Thursday March 05, 2026 @12:15PM (#47264322)
In the early 2010’s I worked for a company whose primary income was subscriptions to site protection services - one of which included cleaning up malware-infected Wordpress installations. I worked on the team that did this job.

This exact type of database-stored executable javascript was one of the most annoying types of infections to clean up.

Re:Wikipedia in read-only mode following mass admin account ... by 0xWTF on Thursday March 05, 2026 @12:22PM (#47264442)
Ok, so there are tons of mediawiki installations all over the internet. What do these operators do? Set their wikis to read-only mode, hang tight, and wait for a security patch?

Also, does this worm have a name?

Re:Wikipedia in read-only mode following mass admin account ... by bawolff on Thursday March 05, 2026 @12:27PM (#47264526)
There is nothing to do, the incident was not caused by a vulnerability in mediawiki.

Basically someone who had permissions to alter site js, accidentally added malicious js. The main solution is to be very careful about giving user accounts permission to edit js.

[There are of course other hardening things that maybe should be done based on lessons learned]

Re:Wikipedia in read-only mode following mass admin account ... by dboreham on Thursday March 05, 2026 @01:05PM (#47265020)
There are already tools and techniques to validate served JS is as-intended, and these techniques could be beefed up by adding browser checks. I've been surprised these haven't been widely adopted given the spate of recent JS-poisoning attacks.
Re:Wikipedia in read-only mode following mass admin account ... by bawolff on Thursday March 05, 2026 @06:32PM (#47268722)
You mean like SRI? That's not really what happened here, so its not really relavent.
Re:Wikipedia in read-only mode following mass admin account ... by streetfighter64 on Thursday March 05, 2026 @12:48PM (#47264800)
Well, admins (or anybody other than the developers / deployment pipeline) having permissions to alter the JS sounds like a significant vulnerability. Maybe it wasn't in the early 2000s, but unencrypted HTTP was also normal then.
Re:Wikipedia in read-only mode following mass admin account ... by bawolff on Thursday March 05, 2026 @03:37PM (#47266962)
That's a fair point, but keep in mind normal admin is not sufficient. For local users (the account in question wasn't local) you need to be an "interface admin", of which there are only 15 on english wikipedia.

The account in question had "staff" rights which gave him basically all rights on all wikis.

Re:Wikipedia in read-only mode following mass admin account ... by cesarb on Thursday March 05, 2026 @06:14PM (#47268557)
> For local users (the account in question wasn't local) you need to be an "interface admin", of which there are only 15 on english wikipedia.

It used to be all "admin" accounts, of which there were many more. Restricting it to "interface admin" only is a fairly recent change.

Re:Wikipedia in read-only mode following mass admin account ... by bawolff on Thursday March 05, 2026 @08:07PM (#47269481)
> Restricting it to "interface admin" only is a fairly recent change.

Its been 8 years!

Re:Wikipedia in read-only mode following mass admin account ... by LaGrange on Thursday March 05, 2026 @01:03PM (#47264984)
> Well, admins (or anybody other than the developers / deployment pipeline) having permissions to alter the JS sounds like a significant vulnerability.

It's a common feature of CMS'es and "tag management systems." Its presence is a massive PITA to developers even _besides_ the security, but PMs _love them_, in my experience.

Re:Wikipedia in read-only mode following mass admin account ... by quantum_magpie on Thursday March 05, 2026 @12:48PM (#47264806)
Could you point to where you found the details of the exploit? It’s not in the linked page. Really interested. Especially the part about modifying it and the other users propagating it?
Re:Wikipedia in read-only mode following mass admin account ... by homebrewer on Thursday March 05, 2026 @01:14PM (#47265127)
The fact of this obvious LLM slop being at the top of this discussion is incredibly insidious. The "facts" it mentions are made up. Has this vapid style finally become so normalized that nobody is seeing it anymore?
Re:Wikipedia in read-only mode following mass admin account ... by 256_ on Thursday March 05, 2026 @01:29PM (#47265311)
I didn't even notice it until you pointed it out, but I checked that account's comment history and it uses em dashes. Also, "the database history itself is the active distribution vector" Is just semantic nonsense.

I still have a basic assumption that if something I'm reading doesn't make much sense to me, I probably just don't understand it. Over the last few years I've had to get used to the new assumption that it's because I'm reading LLM output.

Re:Wikipedia in read-only mode following mass admin account ... by homebrewer on Thursday March 05, 2026 @01:34PM (#47265362)
I've also always used em-dashes, it's not a very reliable indicator. That style is a dead giveaway, though. Some of its comments seem to be written by a human, but several definitely aren't.

I've been spending less and less time here, the moderation is obviously overwhelmed and is losing the battle.

https://aphyr.com/posts/389-the-future-of-forums-is-lies-i-g...

Re:Wikipedia in read-only mode following mass admin account ... by jddj on Thursday March 05, 2026 @02:21PM (#47266031)
The dead internet arrived slowly, then all at once
Re:Wikipedia in read-only mode following mass admin account ... by jibal on Thursday March 05, 2026 @04:08PM (#47267316)
It's not semantic nonsense, it's the truth per the incident reports ... go read the links that have been added up top.
Re:Wikipedia in read-only mode following mass admin account ... by infinitewars on Thursday March 05, 2026 @01:25PM (#47265273)
That user, epicprogrammer's comment history suggests alignment with the Musk/Thiel/Anduril/DoW/anti-Anthropic crowd who are incessantly trying to damage Wikipedia's reputation to push a "Grokipedia" where they can define the narrative.

I wouldn't be surprised if that group were the origin of this attack too.

Re:Wikipedia in read-only mode following mass admin account ... by jibal on Thursday March 05, 2026 @04:06PM (#47267303)
The facts are not made up--check the incident reports.

Most claims of LLM authorship are erroneous.

Re:Wikipedia in read-only mode following mass admin account ... by JKCalhoun on Thursday March 05, 2026 @01:23PM (#47265240)
Perhaps we're at last watching the internet die.
Re:Wikipedia in read-only mode following mass admin account ... by NoMoreNicksLeft on Thursday March 05, 2026 @01:42PM (#47265501)
Yes, but we did that over the last 15 years. We just never realized that's what we were seeing.

It only clicked for me a few weeks ago, in one thread or another here when I realized that no one could ever do what Google did once: Cloudflare and other antibot technologies have closed off traditional search-as-the-result-of-web-crawling permanently. It's not that no one will do it because they think there's no money in it, or that no one will do it because the upfront costs are gigantic... literally it can no longer be done.

The internet died.

Re:Wikipedia in read-only mode following mass admin account ... by Imustaskforhelp on Thursday March 05, 2026 @01:56PM (#47265693)
There are still a few options. I recently had the idea of doing search engine queries on 9 search engines.

Mojeek is a good independent search browser, it isn't the best but at that Hackernews comment/analysis I was doing I found it to be the only one which worked for that case.

Brave exists too.

I know the situation is very critical/dire tho but there is still some chance. All be it quite small.

Mojeek IIRC, is operated by one single guy for 15 years.

Re:Wikipedia in read-only mode following mass admin account ... by marginalia_nu on Thursday March 05, 2026 @01:58PM (#47265716)
> [...] is incredibly insidious. It really exposes the foundational danger of [...]

My LLM sense is tingling.

Re:Wikipedia in read-only mode following mass admin account ... by sefrost on Thursday March 05, 2026 @02:01PM (#47265758)
Yeah, it's like the really high-energy way it's written or something? Can't quite put my finger on it.
Re:Wikipedia in read-only mode following mass admin account ... by amenhotep on Thursday March 05, 2026 @04:23PM (#47267475)
I opened his post history and scrolled down a bit and literally the first thing I saw was a comment starting with "You're absolutely right" lol