Here's a Microsoft writeup:
https://blogs.technet.microsoft.com...-ransomware-worm-targets-out-of-date-systems/
https://blogs.technet.microsoft.com...-ransomware-worm-targets-out-of-date-systems/
If anybody needs to be blamed it is the NSA.
Nate
Here is a great blog post from the 22 year old dude that discovered the domain sinkhole ability, great work that has no doubt saved people £$£$ and valuable data! Someone buy that fella a pint
https://www.malwaretech.com/2017/05/how-to-accidentally-stop-a-global-cyber-attacks.html
SorryMy bad, didn't realise it had been posted already.
Here's a Microsoft writeup:
https://blogs.technet.microsoft.com...-ransomware-worm-targets-out-of-date-systems/
That is just one aspect of how it works though - the overall package seems to have been crafted with the end goal of getting inside larger networks.
I'll repost Caged's link from before for those that might have missed it and still catching up:
NHS says only 4.7% of systems are xp.
https://digital.nhs.uk/article/1493/UPDATED-Statement-on-reported-NHS-cyber-attack-13-May-
Seems to be the reasoning - but anyone analysing it in a sandbox would quickly discover that and deactivate so seems more like just a way for them to run it for testing but kind of elaborate compared to a simple if statement.
EDIT: These kind of killswitches and controller domains aren't unusual in themselves but this implementation seems a bit odd - not sure if its just amateur work from script kiddies packaging it up or whether there is something more behind it.
Thinking about this... what would have happened if the NHS files were all deleted?
Don't be obtuse... If the systems were funded to be secure/at least updated to something beyond the now ancient WinXP, this would have been incredibly unlikely to have occurred.
They removed funding for XP security, so yes it is THEIR fault.
http://www.mirror.co.uk/news/uk-news/tories-cut-security-support-outdated-10413160
The least they could to do was to keep funding it and force the NHS to update, rather than just leaving it completely undefended and asking a massive organisation to change within 3 years.
Ooft.
So win7 also vulnerable. And firewalling it off the internet only makes the spread worse..
The exploit code used by WannaCrypt was designed to work only against unpatched Windows 7 and Windows Server 2008 (or earlier OS) systems, so Windows 10 PCs are not affected by this attack.
Would suggest it was aimed as reasonably modern machines, forgoing the xp and older vulnerable machines.
Just if you didnt oatch since march you were in trouble.
Only if unpatchedOoft.
So win7 also vulnerable. And firewalling it off the internet only makes the spread worse..
Only if unpatched
Client OS from XP to windows 10 are vulnerable if using SMB v1
Server OS from 2003 to 2012R2 are vulnerable if using SMB v1
Basically anyone who has any form of file share using SMB v1.0 can be impacted by this.
Yet to see whats happening with 2000, I'm hoping we can just shut them down
The exploit code used by WannaCrypt was designed to work only against unpatched Windows 7 and Windows Server 2008 (or earlier OS) systems, so Windows 10 PCs are not affected by this attack.
from Microsoft
for a start you first quoted me when I said unpatched, which nothing you have said backs you up. secondly just because its been patched doesn't mean the worm targeted these systems.Patch in question that resolves the exploit https://technet.microsoft.com/en-us/library/security/ms17-010.aspx
more than just 2008 and earlier
for a start you first quoted me when I said unpatched, which nothing you have said backs you up. secondly just because its been patched doesn't mean the worm targeted these systems.
its already been posted but you can have a nice in depth read here
https://blogs.technet.microsoft.com...-ransomware-worm-targets-out-of-date-systems/