Google-images poisoning stats
I think most of you have probably heard about Google-images poisoning, but what is it?
More thorough technical information about this attack could be found on the Unmask Parasites blog or the ISC site. In this blog, we only tried to focus on the data from the avast! Community IQ database to show how big this attack was, and to look at how many domains are still infected -- with their admins either unknowing or not paying much attention to their websites.
The first poisoning url we blocked 8 March, 2011. The first day, we counted only 4 infected domains. Until now, we've received reports from 11,039 infected domains visited by avast! users. The following graph shows how the number of affected domains reported to our systems have grown.
Currently, we are tracking 8 sites used for this poisoning. This graph shows traffic on these blocked sites. The steep slope at the end of the graph is most probably caused by the blocking of the sites in the Google Safe Browsing.
We've tried to verify how many of the referring domains still carry the 'infected' iframe/img tag, and it's 3,609 -- or, in other words, almost a third of them!
Although visiting these sites is not a direct threat to the user (they're only poisoned baits for Google crawlers), this still illustrates the fact that the bad guys have access to many 'legitimate' sites and are able to do anything with them. No 'common sense' approach can help you to decide if you're visiting a clean page or one that's been hacked.
Our Aposemat Team has been testing the capabilities of IPv6 and how malware could take advantage of it. One of the topics explored was exfiltration of data via the IPv6 protocol, which we discuss in this post.
Popular banking services, including PayPal, Revolut and Venmo, allow users to request money from others with a few easy steps. Although simple, this functionality could increase the likelihood of related spearphishing attacks.