Anyone know someone at the Tor Project? Based on a breakdown I read, it downloads the Tor client from
<a href="https://dist.torproject.org/torbrowser/6.5.1/tor-win32-0.2.9.10.zip" rel="nofollow">https://dist.torproject.org/torbrowser/6.5.1/tor-win32-0.2.9...</a><p>It would be simple to rename this link (or perform a referer check or something else to stop automated downloads), at least temporarily.<p>Yes, the malware authors will release an update with the different URL (or another hosting site entirely, or embedded), but at least it would provide time for vulnerable users to install patches. Especially now that Microsoft has released a patch for XP.<p>(I'm basing this URL info on the breakdown found at <a href="https://www.bleepingcomputer.com/news/security/wannacry-wana-decryptor-wanacrypt0r-technical-nose-dive/" rel="nofollow">https://www.bleepingcomputer.com/news/security/wannacry-wana...</a>)
What's special about WannaCry that has made this such a widespread thing? I presume there's has been plenty of malware for a while that can propagate itself around a network of unpatched old Windows machines and people have been trying to get users to clicks on emails to infect themselves for years.<p>So why now? What's so special now?
I don't get it: why are the using using many fake but valid domains? Wouldn't a non-existing TLD do exactly the same thing while being impossible to register by anyone trying to stop the malware?
I really am a bit puzzeled by the killswitches. Why does WannaCry have this functionality in the first place? It sounds almost ironically like a hollywood villain mistake.
> A new variant with no kill-switch recovered by Kaspersky as a virustotal.com upload — not detected in the Wild.<p>Uploaded to virustotal MEANS found in the wild. That's what admins do when they discover things.
Could a grey hat create a self propagating but non-ransoming variant that inoculated target machines against its more malicious brethren? Seems like something a state actor might want to do.
These systems would be better of security wise if they would use the latest open source operating system including the embedded code. The damage this will cause to embedded systems is distasteful.
Could the 51% "bug" in bitcoin actually be used to an advantage here? A 51% vote to invalidate all these transactions? I assume it doesn't work like that but figured I would ask.
I think it's hilarious how these "kill switches" are supposedly meant to detect sandboxes, to make it harder for security researchers to analyze the malware. While actually making it easy for security researchers to completely disable all installations around the entire world.<p>That's just what I heard, but it makes sense. There are far more sane ways to implement a kill switch without using unregistered domains. (For instance, using a registered domain.)
Two researchers said they found a variant with a kill switch.<p><a href="https://motherboard.vice.com/en_us/article/round-two-wannacry-ransomware-that-struck-the-globe-is-back" rel="nofollow">https://motherboard.vice.com/en_us/article/round-two-wannacr...</a>
Why would they keep releasing it, and release it in the first place, with such a simple kill-switch. Doesn't make much sense.<p>Reminds me of the Archer episode where Cyril plants the computer virus and was going to be the hero by "fixing" it.
I am trying to understand impact of crypto currency. Sorry for my ignorance, and or impertinence.
1. Is it possible to run such large scale ransom demands without cryptocurrency?
2. Do we know if the attacker is using a single BTC wallet, or if ransoms are being collected in a distributed fashion.
3. Is it possible for BTC n/w to hijack BTCs going to the ransom wallet(s). That is to say collectively overwrite/override the transactions and may be reroute the coins to some non-profit wallet? I know it will be a very bad precedent, but I am trying to understand if it is technically possible.
This makes me think of a different kind of a kill-switch. What if the OS itself is required to have a kill-switch that triggers once it goes out of support, and it prevents regular use unless the admin goes through some serious hoops to override. It at least squarely puts the blame on 1) Orgs that willfully override v/s passively ignoring to update 2) OS vendors who have really short support cycles (~1 year for most android phones)
We were warned this would happen but it's interesting to me that we have detected new variants that include the same type of naive kill switch. I'm not well versed in information security, so my question is whether this means attackers tried another wave by simply changing the kill switch domain or were there several variants used for the initial attack?
Is there analysis on what encryption algorithm was being used? And how the payment confirmation switch works on the malware.<p>Is it possible instead of patching the OS, to release a patch which patches the malware binary to no-op the payment switch?
I would like to know whether the decrypted data can be trusted again in case the contents have been somewhat changed. Then again it is much better than not having any data at all in some cases...
Just wait until this hits the files of a Russian mob who then take some Americans hostage and fly to China and end up entangled in an islamic terrorist plot. 'Cause then we're in for a very long and drawn out story involving MI6, the CIA, Canadian smuggling routes, and Christian Isolationist 2nd Amendment fanatics.
Who is doing this knowing fully well that GHCQ , FBI and possibly even the NSA are hard at work trying to get them ?<p>These people are going down . No doubt about it.