configured it to be fully exposed with no firewall and no anti-virus software
And I’m also assuming this was then exposed directly to the internet like a server, not behind a NAT or anything like that.
I mean you’re setting up a 20 yo unpatched consumer lever OS to fail for the giggles and you kneecap it on top of it - which is fine, but hardly surprising.
I bet they just threw it into the DMZ, turns out when you park your car in a bad part of town and leave all the windows open and the doors unlocked, bad stuff happens to it
There’s tons of botnets in countries that don’t care about cyber crime just waiting for this sort of thing to be put on the internet. They’d just autopwn as soon as it was discovered and don’t really give a shit since the cops can’t even touch them.
And I’m also assuming this was then exposed directly to the internet like a server, not behind a NAT or anything like that.
That’s how consumer PCs were often setup back in the early XP days though. There was a time when a household typically didn’t have more than one computer or internet connected device. So people didn’t have a NAT-ing router and instead connected their DSL or cable modem directly to their PC, and were completely exposed to the internet. To make matters worse, the firewall was disabled by default in early XP versions as well, until SP2.
This is how Sasser and the Blaster worm were able to wreak havoc, and until home routers started to become common, it was a genuine concern that on a new XP installation you’d be hacked before you had time to patch.
In the early days we learned a lot of things about security through trial-and-error, basically running head-on into the issues, and then going “oh…”.
This isn’t a test of the “early days” XP and internet. This is a test of current day, because clearly the implication is “look how bad it is to use XP in 2024”
Was it disabled? I thought that XP just didn’t have a firewall and got one added later on. I forget which virus it was but RPC would crash within seconds of a device being connected to the internet meaning you had to reboot.
According to Wikipedia, it used to be called Internet Connection Firewall in early versions of XP and then was rebranded to Windows Firewall and turned on automatically in SP2.
A bit clickbaity…
And I’m also assuming this was then exposed directly to the internet like a server, not behind a NAT or anything like that.
I mean you’re setting up a 20 yo unpatched consumer lever OS to fail for the giggles and you kneecap it on top of it - which is fine, but hardly surprising.
I bet they just threw it into the DMZ, turns out when you park your car in a bad part of town and leave all the windows open and the doors unlocked, bad stuff happens to it
And the keys in it, with a light on top flashing “look at me!”
Honestly, I’d be a little surprised if anyone actually did anything to it.
Not for lack of wanting to, but because they, like me, would probably just assume it’s a bait car and cops are 5 seconds away with a kill switch.
There’s tons of botnets in countries that don’t care about cyber crime just waiting for this sort of thing to be put on the internet. They’d just autopwn as soon as it was discovered and don’t really give a shit since the cops can’t even touch them.
That’s how consumer PCs were often setup back in the early XP days though. There was a time when a household typically didn’t have more than one computer or internet connected device. So people didn’t have a NAT-ing router and instead connected their DSL or cable modem directly to their PC, and were completely exposed to the internet. To make matters worse, the firewall was disabled by default in early XP versions as well, until SP2.
This is how Sasser and the Blaster worm were able to wreak havoc, and until home routers started to become common, it was a genuine concern that on a new XP installation you’d be hacked before you had time to patch.
In the early days we learned a lot of things about security through trial-and-error, basically running head-on into the issues, and then going “oh…”.
This isn’t a test of the “early days” XP and internet. This is a test of current day, because clearly the implication is “look how bad it is to use XP in 2024”
Was it disabled? I thought that XP just didn’t have a firewall and got one added later on. I forget which virus it was but RPC would crash within seconds of a device being connected to the internet meaning you had to reboot.
Edit
Apparently it was MSBlaster
According to Wikipedia, it used to be called Internet Connection Firewall in early versions of XP and then was rebranded to Windows Firewall and turned on automatically in SP2.