3 ms·
> Technical teams from CloudFlare, OpenDNS and Google jumped on a conference call and discovered what appeared to be malware on the site to which the NYTimes.co
by WestCoastJustin 13y ago
> Technical teams from CloudFlare, OpenDNS and Google jumped on a conference call and discovered what appeared to be malware on the site to which the NYTimes.com site was redirected.
On the HN post "Google.ps domain was hacked (google.ps)" [1], HN user biot predicted this exact scenario, although not a zero day most likely. He talked about submitting hacked sites to HN "... and thousands of HN readers get infected by a zero-day exploit. Maybe. If you're thinking of submitting a known compromised site to HN, consider instead submitting a third-party site which explains/documents the compromise. Ideally from a respected security research company". [2]
[1] https://news.ycombinator.com/item?id=6278737 https://news.ycombinator.com/item?id=6278737
[2] https://news.ycombinator.com/item?id=6279253 https://news.ycombinator.com/item?id=6279253
- Cyranix 13y agoI'd suggest extending the idea to non-responsive sites as well. Instead of submitting a link to a company's homepage when they're being DDOSed or are otherwise unavailable, submit a link to their status page if they have one or, failing that, use a third-party indicator. Off the top of my head I can't think of a third-party indicator that would capture point-in-time availability, but a manually crafted URL like http://isup.me/example.com?1970-01-01T00:00:00Z http://isup.me/example.com?1970-01-01T00:00:00Z would get the point across just fine.
- joshschreuder 13y agoMaybe something like Zapier's API Status Board, though I'm not sure how realtime and whether it only applies to site's APIs rather than their general websites. https://zapier.com/status/ https://zapier.com/status/
- bryanh 13y agoIt applies to their APIs specifically. It is realtime within ~5 minutes.