I think it would, from Microsoft's technet article [1] -- the reason they went this route seems to be because they're having detecting these two worms (they're polymorphic) -- so they went for decapitation: kill the C&C.
Besides, knocking out no-ip still doesn't "fix" anything - there're a billion and one easy ways around it - C&C lists in alternate dyndns providers, 3rd party namespaces,Tor based C&C, pastebins, public/anonymous forums, hidden in bit-torrent blockchain etc etc etc
Heck, pushing an update to every Windows machine that simply resolved *.no-ip.org to 127.0.0.1 would be better than this. At least then folks that wanted to use it would have an easy recourse.
Comments
I think it would, from Microsoft's technet article [1] -- the reason they went this route seems to be because they're having detecting these two worms (they're polymorphic) -- so they went for decapitation: kill the C&C.
Besides, knocking out no-ip still doesn't "fix" anything - there're a billion and one easy ways around it - C&C lists in alternate dyndns providers, 3rd party namespaces,Tor based C&C, pastebins, public/anonymous forums, hidden in bit-torrent blockchain etc etc etc
Heck, pushing an update to every Windows machine that simply resolved *.no-ip.org to 127.0.0.1 would be better than this. At least then folks that wanted to use it would have an easy recourse.
[1] http://blogs.technet.com/b/mmpc/archive/2014/02/11/msrt-febr...
...I don't know if you're joking or not, but that would've been far worse.
At least in this case, Microsoft is attempting to make an effort to preserve all non-malicious domains.