Re:We Got Phished
by arkitaip on Monday October 24, 2016 @03:04PM
(#12781797)
Google needs to add some optional intelligence to Chrome so that when it comes across a site with suspiciously similar design as key google urls by on a unrenognized url, it should warn the user.
[ Parent
| on HN ]
Re:We Got Phished
by davidpatrick on Monday October 24, 2016 @03:16PM
(#12781897)
You can use Google's AMP that is hosted on their domain, to host a redirect, effectively using their domain to host the phishing attempt. Check the screenshots on http://motherboard.vice.com/read/how-hackers-broke-into-john...
Re:We Got Phished
by moduspwnens14 on Monday October 24, 2016 @03:38PM
(#12782089)
Don't those screenshots just show domains crafted deceptively to look like Google domains? I don't see any legitimate Google ones.
> “We are approaching the point in this case where there are only two reasons for why people say there’s no good evidence,” Rid told me. “The first reason is because they don’t understand the evidence—because the don’t have the necessary technical knowledge. The second reason is they don’t want to understand the evidence.”
Is there anywhere we can see this evidence? Objectively I'm curious how an attack which consisted of basic phishing was determined to be definitively supported by the Russian government.
If they broke SHA-256 or coerced a Russian CA to generate a Google certificate, I'd agree... but using bitly and decades-old "click this link to reset your password" links? Come on.
Notice in one of the last screenshots, the link actually points to a real Google.com domain, but in the /amp/ destination, under which a tiny(cc) link was hidden and therefore fetched the content that "seemed like" it came from Google when Google merely acted as a CDN.
Re:We Got Phished
by moduspwnens14 on Monday October 24, 2016 @04:01PM
(#12782318)
Ahh. I see it now. Pretty sneaky.