Slashdot Mirror

← Back to Stories (view on slashdot.org)

Poisoned Google Image Searches Becoming a Problem

Posted by Soulskill on from the quick-search-for-the-antidote dept.

Orome1 writes "If you are a regular user of Google's image search, you might have noticed that poisoned search results have practically become a common occurrence. Google has, of course, noticed this and does its best to mark the offending links as such, but they still have trouble when it comes to cleaning up its image search results."

4 of 262 comments (clear)

  1. screenshots by cobbaut · · Score: 5, Informative

    Two weeks ago I put some screenshots of what it looks like on my blog:
    http://cobbaut.blogspot.com/

    --
    European Linux user, living in Antwerp
  2. Re:im glad im not the only one by Nimey · · Score: 5, Informative

    lynx + zgv was how I used to view images on the Web about ten years ago. It worked surprisingly well, back before AJAX or Flash were used for navigation.

    --
    Hail Eris, full of mischief...

    E pluribus sanguinem
  3. Re:web 101: don't run unknown javascripts by Anonymous Coward · · Score: 5, Informative

    This is not going to happen. Many major websites, many of the highest traffic websites involve hundreds of JS scripts to make a single page function. Web 2.0 and all...

    Ironic, given that Google recently (this month) just changed its behavior to practically require Javashit.

    Old hotness: (1) Google "foo". (2) Click "Images" tab at top of screen for a GIS for "foo".

    New and busted: (1) Google "foo". (2) Click "Images" tab at top of screen for... "Your search - foo - did not match any documents." (3) curse, click "Images" tab again - to go to http://www.google.com/imghp?hl=en&tab=ii, and (4) have to type "foo" again in order to GIS "foo". (Or remember to start at images.google.com, which is an issue when you might not be sure which terms to use when searching for the image in the first place)

    Turn Javashit on, and clicking the tab works just fine... but whatever Google changed broke the non-Javashit version of GIS.

    Sorta like last month - maps.google.com is an AJAX app, so it's reasonable for it to require Javascript. But it used to work fine without cookies enabled. Now, it requires both Javascript and cookies. Interesting.

    Just tested/confirmed both of these on Firefox 3.6.16.

    What Facebook does overtly, Google does by benign neglect and failure to regression-test. What's next? Google services simply stop working for Firefox and require Chrome?

  4. Mac is vulnerable too by Teckla · · Score: 5, Informative

    My wife got bitten by this just today.

    She navigated to a web page from a Google search result, and Safari automatically downloaded some malware and executed it.

    I didn't believe my wife's story at first, so I tried it. Sure enough, automatic download and execution on Mac/Safari.

    What the fuck, Apple and Safari?

    The only question that remains is whether I'll be moving her to Firefox or Chrome...