Google to notify 500,000 DNSChanger victims today

Infected home routers means all mobile devices at risk too
  • Liam Tung (CSO Online (Australia))
  • — 23 May, 2012 10:48

Half a million people may receive a warning from Google today that their computer or router is showing signs of infection by the infamous DNSChanger malware.

Google will attempt to succeed where a variety of organisations have failed by employing users’ local language to convey the message that from July 9, “you might not be able to connect to the internet in the future” because of the infection.

The Australian Media and Communications Authority this March warned via a press statement that around 10,000 potential Australian victims that their PCs could be affected by the July 9.

Its not clear how effective the ACMA’s campaign was but it was the first authority in the world to announce the impending cut off date.

The number of victims observed per day since November 2011 has hovered around the 500,000 mark, but hundreds of thousands remain infected despite global efforts to warn consumers they may be experience difficulties connecting to the web come July 9.

The risk for users, besides the malware itself, stems from the expiration of an order giving control over ‘rogue’ DNS servers to the Internet Systems Consortium (ISC).

The consortium was granted temporary control over the rogue servers following the FBI’s November 2011 arrest of six Estonian nationals suspected to be behind the DNSChanger malware and the Estihost botnet. The servers were based in the US.

Paul Vixie, ISC’s chairman and chief scientist at last week’s AusCERT conference said that around 300,000 computers are expected to still be infected by the July 9 cut off.

The malware was behind a massive click fraud and fake antivirus scheme and was estimated at its height to have infected between 4 million and 8 million PCs worldwide, including some Macs.

The malware manipulates the computer’s domain name service settings, which are used to translate a domain name to the correct corresponding IP address.

Google security engineer, Damian Menscher pointed out that home routers may be affected as well, “meaning other computers and mobile devices may also be affected.”

“[V]arious ISPs and other groups have attempted to alert victims. However, many of these campaigns have had limited success because they could not target the affected users, or did not appear in the user’s preferred language (only half the affected users speak English as their primary language),” Menscher wrote.

Follow @CSO_Australia and sign up to the CSO Australia newsletter.

Comments are now closed.
CSO Corporate Partners
  • Webroot
  • Trend Micro
  • NetIQ
rhs_login_lockGet exclusive access to CSO, invitation only events, reports & analysis.
CSO Directory

Security Risk Management Solutions

Protect resources and ensure security compliance through incident detection, response, and remediation.

Security Awareness Tip

Incident handling is a vast topic, but here are a few tips for you to consider in your incident response. I hope you never have to use them, but the odds are at some point you will and I hope being ready saves you pain (or your job!).


  1. Have an incident response plan.

  2. Pre-define your incident response team 

  3. Define your approach: watch and learn or contain and recover.

  4. Pre-distribute call cards.

  5. Forensic and incident response data capture.

  6. Get your users on-side.

  7. Know how to report crimes and engage law enforcement. 

  8. Practice makes perfect.

For the full breakdown on this article

Security ABC Guides

Warning: Tips for secure mobile holiday shopping

I’m dating myself, but I remember when holiday shopping involved pouring through ads in the Sunday paper, placing actual phone calls from tethered land lines to research product stock and availability, and actually driving places to pick things up. Now, holiday shoppers can do all of that from a smartphone or tablet in a few seconds, but there are some security pitfalls to be aware of.