Well, no shit.

This would likely happen to any machine directly exposed to the internet that hosts any kind of service intended for local networks only... (which is the network stack on Windows, and has been so since 1990 with NetBEUI/NetBIOS), and has been intentionally left insecured to boot.

Hell, in the 90's we put windows desktops directly on the internet just to see what would happen (yea, our bosses would yell at us when they caught it). They didn't get hacked much or very fast then, which shows how much automated intrusion scripting is happening today.

Bunch of clickbait nonsense.

Local machines aren't servers. And servers aren't directly exposed to the internet without routers/firewalls/IPS/IDS, etc. The only devices that should be directly connected to the internet are edge routers. And even they should have very secure, layered setups to ensure malicious traffic can't transit to the LAN.

I wonder how many people still directly connect to the internet without a gateway. It seems sensational to say "INSTANTLY INFECTED" and then tiny print (in a way that nobody connects to the internet since 1999). But maybe I'm just ignorant to how large a market still use direct connection.

It's nothing new. I remember doing this for fun about 16 years ago, putting a WinXP machine on the internet with no firewall and waiting. Even back then, it was immediately hammered by traffic and quickly started doing dubious things.