
A Wikipedia security engineer accidentally wakes a dormant JavaScript worm that hadn’t stirred since 2024 – and within minutes, giant woodpecker images are plastered across the internet’s favourite encyclopaedia.
Meanwhile, a crypto contractor hired to help the US Marshals manage seized digital assets allegedly decides to help himself to $46 million of it – and then brags about it on a recorded Telegram call.
Plus: Graham champions Asterix, Trisha discovers the fantasy novels of Robin Hobb, and someone called “Lick” ends up in the nick.
All this, and much more, in episode 458 of the “Smashing Security” podcast with cybersecurity veteran and keynote speaker Graham Cluley, and special guest Tricia Howard.
Show full transcript ▼
This transcript was generated automatically, probably contains mistakes, and has not been manually verified.
Hello and welcome to Smashing Security episode 458. My name's Graham Cluley.
And so when I do have, you know, minutes, so to speak, of that, I have been enjoying very much playing GTA 5 with my partner, starting from the beginning and going through the whole story.
And there is a fair amount of driving involved in that game. But I have to say, they are extraordinarily immersive games, aren't they?
Let me just say that.
This week on Smashing Security, we won't be talking about how Leakbase, a cybercrime forum with over 100,000 members, has been seized by law enforcement.
You'll hear no discussion of how Ericsson is blaming a leak of more than 15,000 people's details on a service provider that was sweet-talked via the telephone.
And we won't even mention how hackers bypassed multifactor authentication with a $120 phishing kit until multinational law enforcement shut them down.
So Tricia, what are you going to be talking about this week?
Now, most cyberattacks don't start with sophisticated malware. They start with a misconfigured setting, a drifted policy, or an exposed endpoint that nobody noticed.
And when you've got hundreds of endpoints, keeping track of all that manually, basically impossible.
They scan operating system settings, application settings, and your ThreatLocker policies like allowlisting, ring-fencing, and more.
You know, often I'll be thinking, oh, is Alan Alda dead or is he still alive? I'm not sure. You know, and you'll go to Wikipedia to find out.
Or if you're unsure how old somebody is, you'll go there instantly.
And it's also, let's be honest, a place where significant percentage of students have been plagiarising their essays about, oh, I don't know, all kinds of crazy topics like the South Sea Bubble for the past two decades.
So it's an incredible resource, I kind of like Wikipedia. I know we can't completely trust it, but I kind of like Wikipedia.
They happily spend hours arguing about the correct capitalisation of a fictional spacecraft in some sci-fi TV series.
It is a genuine marvel of the internet age and something which we should be grateful for because it's not monetized. You don't get ads on it. It is purely supported by donations.
So it was with some alarm that on the 5th of March this year, projects at Wikimedia— that's the foundation which operates Wikipedia— some of their projects started misbehaving a little.
So pages were being vandalised and deleted. And when they got messed around with, there'd be a final Russian edit summary.
So someone left a little bit of a summary as to why has this edit occurred? Well, here it is in Russian. It translated rather ominously to closing the project.
And at the same time, enormous, and I do mean enormous, I'm talking 5,000 pixels wide, which is probably wider than every screen here.
5,000-pixel-wide images of woodpeckers were being embedded across random articles on Wikipedia.
You know, you have good cartoon characters like Danger Mouse and Bugs Bunny and Daffy Duck, and then you have the rubbish ones. Mickey Mouse and there goes the Disney sponsorship.
Foghorn Leghorn. I liked him, you know.
Was it a rogue insider? Was it a disgruntled editor with a grudge against Woody Woodpecker? But no, the person who triggered the worm outbreak was a Wikimedia security engineer.
So if you are one of these administrators, one of these people who's really, really keen on Wikipedia, you can create yourself an account for editing pages.
And you can also, if you don't like the standard editor which is built into Wikipedia, you can have a little user script to set it up exactly as you want it, right?
Which makes sense. So you can upload a script to it.
And what it seems happened is that while this Wikimedia security engineer was reviewing some of the user-written scripts on the platform, they accidentally executed a piece of dormant malicious code that had been sitting silently on a user's test page since 2024.
And so this script in question had been sitting there under the username. Now I'm going to probably make a little mistake here. Ololoshka562 was a user on Russian Wikipedia.
So it's just sat there a coiled spring in a dusty old filing cabinet no one had opened in years. They open it up. And it sprang out.
And what made it much worse is that the account that it was executed under was a staff account, a highly privileged Wikimedia Foundation staff account, which had low-level editing access.
So someone with permissions to edit the global JavaScript that runs across all Wikimedia projects on every page for every single user.
I mean, there's been a lot of diplomatic vagueness in the world in recent weeks, but this was also diplomatically vague about the exact sequence of events.
So they said staff had been conducting a security review of user-authored code and had inadvertently activated this dormant code.
And I think the inadvertently is doing a lot of the heavy lifting there. We don't know precisely what happened, whether it was a slip up or a misclick.
You know, it's they thought they were clicking on one thing and they opened another. We don't know what it was, but the result was significant because the script woke up.
It was activated, immediately got to work. It injected itself into the common.js file on MediaWiki.
That is the global JavaScript file that runs in the browser of every logged-in user across the entire Wikimedia ecosystem, including Wikimedia Commons, including Wiktionary, which is a dictionary for witches, I believe, including Wikidata, all of them.
In other words, this worm didn't just vandalize pages. It managed to plant code in the one place that could potentially execute in every editor's browser across the platform.
What could possibly go wrong with that, Tricia?
You know, it's astounding too, because this is an unfortunate reality that we deal with in security a lot, is that so, so many things are actually just caused by accidents.
We love to talk about, you know, the big scary stuff, and we should be, of course, they're interesting stories if nothing else.
But the truth of the matter is, this is the reality of security people every day.
They're dealing with somebody who accidentally clicks on something and sends Woody the Woodpecker across the Wikipedia.
So it's a backup, if you like, in case someone found and cleaned up the global file.
So thousands of pages were vandalized. They were plastered with that 5,000-pixel-wide woodpecker image and hidden script tags, spreading itself to other users.
It also tried to phone home to a remote Russian web server, danger, danger, presumably to try and fetch further instructions.
Now, I don't know if that domain was live or defunct or simply abandoned by whoever created it.
Thankfully, it looks like the callback didn't appear to cause any additional harm, but in theory, that could have grabbed more malicious code or instructions, which could have caused an even bigger problem.
You can imagine how something like this could have become a much, much bigger threat, maybe stealing data from users as well, or maybe trying to run something else malicious on their actual computers.
Suddenly everything is locked down. It then took them a couple of hours to investigate and contain the infection. They began scrubbing the code from thousands of files.
By the end of the day, all the affected pages had been restored and no personal data, as far as we know, has been breached in any way. So that's good.
So most of the visible vandalism, by the way, that landed on MetaWiki, which isn't the encyclopedia that you use every day online, but it's rather like the back office of Wikimedia.
It's where the volunteer community hangs out and debates policy and gets very pedantic with each other. Highly political, I expect.
Most members of the public have never heard of it, but potentially, you know, that injected JavaScript ran across the entire ecosystem, including Wikipedia itself.
So while your average reader looking up the history of the Roman Empire probably noticed nothing, any logged-in editor active during those 23 minutes was potentially exposed.
I'm trying to remember in the Terminator movies, don't they plug in the chip or give it autonomy and it only takes about 23 minutes or something to become self-aware and decide we don't need the humans anymore?
I can't remember what the actual figure is, but, you know, 23 minutes can sometimes in this day and age be long enough to cause an awful lot of damage.
When we're dealing with something like that, it's not just the initial infection that you have to deal with.
It's the repercussions that come after it and the collateral damage, frankly, like these additional editors.
So all of us need to be careful about how we are actually logged in, what rights we have.
If we don't need them for a particular thing that we are doing, then maybe you shouldn't be logged into them.
And certainly you probably shouldn't be clicking on other people's scripts if you're inside something which had that much power.
Also, if you're on a platform which has scripts or has user-generated content, maybe you need to audit it from time to time for dormant malicious scripts, because it turns out something can sit undetected for the better part of a couple of years before roaring back to life.
And maybe just use a test environment as well, where the damage can be limited as to what you can do. So there's good news. Everything's now been cleaned up, it seems.
Nothing was permanently lost. That's great. Wikimedia says it is working on further security mitigations as well.
So hopefully they'll be better protected against this kind of problem in the future.
Right, before we crack on any further, Joe and I want to take a moment to tell you about one of today's sponsors, Vanta.
Or is it the truly soul-destroying one: why on earth are we still running our entire security program out of a spreadsheet?
Vanta takes all that tedious manual security grind, chasing down evidence, wrestling with questionnaires, updating the same cells for the thousandth time, and automates the whole thing.
Yes, it uses AI, but the genuinely useful kind, flagging risks, streamlining evidence collection, and slotting into the tools your team already relies on.
The upshot of this is you move faster, scale without the usual headaches, and maybe, just maybe, actually get a decent night's sleep.
So I'm going to start my story with a little bit of backstory, if for literally no other reason than to show off what I learned, because I apparently have no idea what the US Marshals do or who they are.
This could be money, houses, cars, anything in GTA, actually. What a nice little callback that is.
Okay, so they are the go-between between the initial "we caught you" to "all right, we're going to put you in prison now and here's why," right?
So shocker, a big portion of these assets that they obtain are crypto. I mean, who knew that crypto was used for sketchy stuff?
It's probably different now, but that came directly from them that at one point they were managing $3.4 billion just in crypto assets alone that were obtained.
So with crypto, now I'm not part of the crypto scene, so this may be old news to everybody. It was news to me.
There's a lot of technical stuff in the backend that has to happen to make sure that these transitions between the illegal means to legal means happen above board, right?
So the US Marshals Service is shockingly not a crypto expert first and foremost.
So when they bust these things and get these assets, they will bring in third-party contractors who are experts in crypto. I'm sure you can see where this is going.
And that's all well and good until it gets stolen.
If Law & Order: SVU is to be used as a trusted source of how law enforcement works, and I'm very willing to believe that that's true, when they don't have a named perpetrator, they call them John or Jane Doe.
So I literally laughed almost out of my chair because the alleged perpetrator is literally named John D. Okay. So it was a John Degida. I'm not sure if I'm pronouncing that correctly.
He allegedly has stolen $46 million worth of crypto directly from wallets managed by the US Marshals.
Now, there were some mixed reporting on this that John himself had an active contract.
Nothing that I saw actually implicated the father in this in any other way other than owning the company. But first off, John goes by Lick online. Gross. I need a shower.
While he was recently arrested, this actually all started back in January when a blockchain investigator who apparently got wrecked before and then decided to become an investigator as a result of that, which is pretty cool.
His Twitter handle is @Zackxbt.
So back in January of this year, he noticed about $23 million in shady transactions that were directly tied to these wallets that were known to be associated with the U.S.
Marshals Service. And some of the funds in these wallets, by the way, were connected to the infamous Bitfinex attack in 2016, the largest crypto scam of all time. Yeah.
So naturally, when things this happen, you have to ask, how did not only the initial thing occur, but how did they get caught?
But whenever they're less than savory individuals, which if the transcripts of this person is to be believed, I would argue he's very less than savory.
It's just kind of funny, especially when they do it to themselves. All right. So there was the initial thing that Zach found, and then Zach started reporting on it he does.
To say, yep, this is me, because it's, you know, anonymized and all that stuff. So John started sending them to Zach's wallets.
And what is problematic about that is, because this was associated with illegal activity, theoretically Zach's wallets could be affected negatively. He could—
It's not really good opsec to start trolling the person who's investigating you.
I don't know, maybe not the strongest one, but a worse opsec strategy than that is getting on a recorded call and telling on yourself.
So not only was he a thief, he was a braggart and got on a Telegram call with another known threat actor who was calling John out and saying that John didn't actually have access, that his claims were false.
And so he proved that he had access to these wallets, and that was recorded. You can actually watch the recordings on Zach's Twitter thread where he talks about this.
Language warning, by the way, if you watch them.
You have tens of millions of dollars in seized crypto assets sitting in a government-managed wallet. Those wallets are handled by outside contractors.
This guy's dad is one of those contractors, and he himself may have had direct access.
He steals those funds, then trolls the investigator who calls him out for it, and then brags about it online, proving that he did all of this. How 2026 is that?
I mean, in some ways we're grateful because it makes it easier to catch— I mean, this guy, these are allegations at this point.
But it also leaves you with your head in your hands thinking, oh, for goodness' sake, couldn't you have done a bit better than that?
When I worked at Akamai in the research organization, we actually saw this a fair amount where the threat actors would be proud of what they were doing, not unlike we are proud of things that we do at work.
And they would get called out and said, no, you don't actually have this. And they would prove it themselves.
It's an interesting tactic, I guess, make them tell on themselves by playing to their ego. Huh, who knew that would work?
Suddenly you're juggling ISPs, floor plans, hardware configuration. Oh, what a headache. It's basically a second job.
They sort out the ISP, they design the network, they show up on site, they rack their own hardware, not reselling someone else's kit, and they get the whole thing running.
Full visibility and control. None of the tedious legwork.
Could be a funny story, a book that they've read, a TV show, a movie, a record, a podcast, a website, or an app, whatever they wish.
It doesn't have to be security-related necessarily. Well, my Pick of the Week this week is not security-related. My Pick of the Week this week is a blast back to my childhood.
Yes, I remember the 1870s when all we had to enjoy was a hoop and a stick. We had fun in those days. That's all we needed. Occasionally, we know we'd go out into the garden.
We might find a pebble and a rock to bash together as well and try and make some sparks. Not quite that old, for goodness' sake. No, more recent than that. Asterix. Asterix the Gaul.
Are you familiar with Asterix the Gaul, Tricia?
So Asterix is a plucky little Gaul in the— I think it's 50 AD is when he's living. And was it 50 BC? It doesn't matter. It's 2,000 years ago.
And he lives in a village which is holding out against the Roman Empire. It's the final bit of what would later become France. Everywhere else has been conquered.
And he's living in this little village, and it's a small, stubborn place. They're holding out against the Roman Empire.
They are armed with nothing more than their wits and magic potion, which gives them super strength.
These were originally in French. They've been translated around the world. They are very, very funny.
I think they had Gérard Depardieu as Obélix, the one who carries the menhir everywhere. There's even a theme park, I think, in France as well. But forget all of those.
I'm talking about the classic Asterix books made from about 1960 until about 1977. By Goscinny and Uderzo. They're still making the books today.
Well, not those two because they're dead. But the books are still being cranked out. And here's some of the reasons. I can't believe you've never heard of Asterix.
So the translators who have translated Asterix from the original French into other languages, they are absolute unsung heroes.
There's even a village postman called Postaldistrix. There's slapstick.
There are Asterix books which are probably thinly veiled discussions as to whether Britain should become members of the European Union. Look what happened there.
So you can see how old some of these books are. They are genuinely a joy, however old you are. There's some gentle mocking of national stereotypes.
So when Asterix goes to Britain, for instance, to meet a tribe over there, there's warm British beer and there's boiled food, there's Roman bureaucracy.
When he goes to Switzerland, there's lots of fondue, things like this.
The artwork is fantastic. You've got to Google image Asterix the Gaul right now to see some of this. Magnificent battle scenes, dozens of Romans flying through the air.
If you need an excuse, buy the Asterix books for your kids. But I'm sure you will love them too. You can use the kids as an excuse, but they're really, really great.
And as I said, it's much better than Tintin. So Asterix is my Pick of the Week.
And I was going to choose a specific trilogy of hers to be my pick of the week, but I could not decide between them because they are all so good.
So for reference on how amazing Robin Hobb is, she has been publicly praised by none other than the god of fantasy himself, George R.R. Martin. Don't know if you've heard of him.
The two that I'm in the middle of right now are the Liveship Traders and the Farseer trilogy. Farseer came first, and then the Liveship Traders came afterward. They are thick books.
It's certainly a commitment. But oh, my goodness. I am somebody who loves to get swept away in the story. And she has an unbelievable way of not only telling these stories.
I mean, she's got an incredible mind, but the way that she paints pictures, I mean, you can tell she's lived, all right?
She's been through some stuff, and it comes through very, very clearly.
We're not talking that kind of fantasy.
And he's the bastard child of the prince who is going to become the king. And the kid gets dumped at the palace, and he becomes an assassin, or what is known as a Kingsman.
And it is— my goodness, Graham, it's really astounding. I will say, though, you need to dedicate time to read them because you cannot put it down after a certain amount of time.
The pages fly through. Really, really lovely.
I would— I started with The Liveship Traders, and I think that's a strong one to start with because it introduces her world because both of them take place in the same world, just completely different times.
So start with that because it's a standalone. The Farseer trilogy has a couple of other offshoots of it.
So if you're just looking for a quick, quote unquote, trilogy to get introduced to her and her style, I would say The Liveship Traders is the one to go with.
It follows a family of sailors that have been traders for many, many years. And bad stuff happens to them.
I'm sure lots of our listeners would love to find out what you're up to and follow you online. What's the best way to do that?
And don't forget to ensure that you never miss another episode, follow Smashing Security on your favorite podcast apps such as Apple Podcasts, Pocket Casts, and Spotify.
For episode show notes, sponsorship info, guest lists, and the entire back catalog of 458-odd episodes with the emphasis on odd, check out smashingsecurity.com.
Until next time, cheerio, bye-bye.
We're going to grab a few names out of the hat. Give it up for JBSK, who we can only assume is too cool to have a full name.
Bashora, the nerd who named themselves after a shell terminal. William Reddick, the very soft and breathable Matt Cotton. The positively electric Bobby Hendrix.
Matt H, presumably because the username Matt was already taken, perhaps by Matt Cotton. Frankie Guzikowski. Mansui Dijon.
Alexander Huy Guiz, which sounds less like a person and more like a very grand Dutch country estate. And finally, Dmitry, just Dmitry, no last name, very mysterious.
We respect you, Dmitry, and all the rest of you as well.
If you fancy having your name read out at the end of the show and you fancy having ad-free episodes of Smashing Security, all you have to do is support us at smashingsecurity.com.
Smashingsecurity.com/plus. That will take you to the page where you can sign up, and maybe you'll get thanked in a future episode as well.
Of course, not everyone can stretch to supporting the show financially. That's absolutely fine. I get it. There's absolutely no pressure to do that.
Instead, what you can do is you can go and tell your friends. There's lots of pressure on you to do that.
Go and tell your friends about Smashing Security and encourage them to tune in to some of our past episodes as well as the future ones too.
Thank you everybody who supports the show, leaves 5-star reviews, likes, subscribes, and spreads the word. I really do appreciate it. And until our next episode, I will now sign off.
So toodle-oo from me. Bye-bye.
Host:
Graham Cluley:
Guest:
Tricia Howard:
Episode links:
- Major data leak forum dismantled in global action against cybercrime forum – Europol.
- Ericsson blames vendor vishing slip-up for breach exposing thousands of records – The Register.
- How hackers bypassed MFA with a $120 phishing kit – until law enforcement shut them down – Hot for Security.
- Wikipedia hit by self-propagating JavaScript worm that vandalized pages – Bleeping Computer.
- FBI arrests crypto thief accused of stealing $46 million from seized government wallet – Tom’s Hardware.
- Twitter thread by ZachXBT about John Daghita’s arrest – Twitter.
- Asterix – Wikipedia.
- Robin Hobb.
- The Complete Farseer trilogy – Harper Collins.
- Smashing Security merchandise (t-shirts, mugs, stickers and stuff)
Sponsored by:
- Vanta – Expand the scope of your security program with market-leading compliance automation… while saving time and money. Smashing Security listeners get $1000 off!
- ThreatLocker – Start your free trial and book a demo of ThreatLocker today to see how you can implement Zero Trust in your environment.
- Meter – Network infrastructure for the enterprise. Get a free personalised demo.
Support the show:
You can help the podcast by telling your friends and colleagues about “Smashing Security”, and leaving us a review on Apple Podcasts or Podchaser.
Join Smashing Security PLUS for ad-free episodes and our early-release feed!
Follow us:
Follow the show on Bluesky, or join us on the Smashing Security subreddit, or visit our website for more episodes.
Thanks:
Theme tune: “Vinyl Memories” by Mikael Manvelyan.
Assorted sound effects: AudioBlocks.
