{"id":4551,"date":"2017-06-01T19:46:57","date_gmt":"2017-06-01T11:46:57","guid":{"rendered":"https:\/\/www.darknet.org.uk\/?p=4551"},"modified":"2017-06-01T19:47:10","modified_gmt":"2017-06-01T11:47:10","slug":"windows-xp-unstable-spread-wannacry","status":"publish","type":"post","link":"https:\/\/www.darknet.org.uk\/2017\/06\/windows-xp-unstable-spread-wannacry\/","title":{"rendered":"Windows XP Too Unstable To Spread WannaCry"},"content":{"rendered":"

Not a super serious article this one, but I found it very entertaining – apparently, Windows XP has a BSOD (Blue Screen of Death) when faced with a WannaCry infection<\/a>.<\/p>\n

\"Windows<\/p>\n

There’s a very extension analysis of WannaCry here where this information comes from WannaCry: Two Weeks and 16 Million Averted Ransoms Later<\/a>.<\/p>\n

Yes, WannaCrypt can infect all those machines that still run Windows XP, but because XP is so flaky the zombie boxen are unlikely to have contributed much to the spread of the worm.<\/p>\n

That’s the conclusion of Kryptos Logic researchers after a couple of weeks trashing crash-test-dummy machines in the laboratory.<\/p>\n

The company notes that the infection rate probably got up to as many as 727,000 unique IPs at its height.<\/p>\n

Early in the infection, it was assumed \u2013 including by El Reg \u2013 that unpatched Windows XP systems were part of the problem, especially since it lives on in the systems of early victim, England’s National Health Service.<\/p>\n

Kryptos (whose roster includes celebrated sink-holer MalwareTech) has bumped its head on this for an almost-comical reason: yes, WannyCrypt could infect XP machines, but the underlying DOUBLEPULSAR payload kept crashing the targets.<\/p><\/blockquote>\n