Attacks/Breaches
5/23/2012
12:04 PM
Connect Directly
RSS
E-Mail
50%
50%

Google Spreads Word On DNSChanger Malware

After taking down the botnet, the FBI is still trying to alert 500,000 people that their PCs are infected with the malware. Some Google search users are now getting direct warnings.

"Your computer appears to be infected."

Google began displaying that message Tuesday to anyone using one of its search engine sites with a PC that appears to be infected with the DNSChanger malware.

"After successfully alerting a million users last summer to a different type of malware, we've replicated this method and have started showing warnings via a special message that will appear at the top of the Google search results page for users with affected devices," said Google security engineer Damian Menscher in a blog post. The previous effort targeted a fake antivirus software campaign.

[ Read about some real-world examples of mobile malware and the challenges of thwarting them. See 6 Findings That Prove Mobile Malware's Mettle. ]

"Our goal with this notification is to raise awareness of DNSChanger among affected users," Menscher said. Furthermore, since about half of infected PCs appear to be located in non-English-speaking countries, "we believe directly messaging affected users on a trusted site and in their preferred language will produce the best possible results."

Why the proactivity with respect to this particular piece of malware? Because any PC infected by DNSChanger stands to lose Internet access on July 9, 2012. That's the court-ordered date for the FBI and the Internet Systems Consortium to disconnect the domain name system (DNS) servers they're currently using to resolve Internet addresses for PCs infected by DNSChanger. The FBI commissioned the servers after "Operation Ghost Click," in which the bureau and Estonian police worked together to bust six Estonians for using the malware to conduct a four-year click fraud campaign that raked in an estimated $14 million.

To perpetrate the click fraud--forcing a Web browser to "click" on certain advertisements, thus generating revenue from pay-per-impression advertising networks or referral fees--the criminals used their malware to alter the DNS settings on infected PCs to their own rogue DNS servers. Even after the botnet operators were arrested, however, the infected PCs were still relying on the rogue DNS servers to resolve domain names into IP addresses.

For anyone left with a PC infected by DNSChanger come July 9, when the temporary DNS server gets disconnected, the resulting loss of connectivity may not be easy to diagnose. "In the simplest terms, connectivity will not be severed for DNSChanger-infected systems, but Internet communications will not function for infected systems that have not been cleaned up," explained Kurt Baumgartner, senior security researcher for the global research and analysis team at Kaspersky Lab, via Threatpost. "In the U.S., government agencies, home users, and other organizations still infected with the malware will have systems that effectively can't get online, can't send email, etc. It will look like they are connected to their network, but they just won't communicate with anything."

Google's outreach effort alone, of course, won't solve this malware-infection problem. "While we expect to notify over 500,000 users within a week, we realize we won't reach every affected user," said Menscher. Still, reducing the number of infections by any amount will help. "If more devices are cleaned and steps are taken to better secure the machines against further abuse, the notification effort will be well worth it," he said.

Since the botnet takedown, numerous service providers--including AT&T, Bell Canada, CenturyLink, Comcast, COX, Time Warner, and Verizon--have also begun notifying customers whose PCs that appear to be infected. Meanwhile, for anyone else who suspects their PC may have been infected, the DNSChanger Working Group (DCWG) also maintains a list of websites that will identify if your PC is carrying the malware.

When it comes to regulatory compliance, auditors consider more than how you protect your company's covered assets from external attackers. In the Compliance From The Inside Out report, we show you how to create and implement a security program that will defend against malicious and inadvertent internal incidents and satisfy government and industry mandates. (Free registration required.)

Comment  | 
Print  | 
More Insights
Register for Dark Reading Newsletters
White Papers
Flash Poll
Current Issue
Cartoon
Video
Slideshows
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2013-6117
Published: 2014-07-11
Dahua DVR 2.608.0000.0 and 2.608.GV00.0 allows remote attackers to bypass authentication and obtain sensitive information including user credentials, change user passwords, clear log files, and perform other actions via a request to TCP port 37777.

CVE-2014-0174
Published: 2014-07-11
Cumin (aka MRG Management Console), as used in Red Hat Enterprise MRG 2.5, does not include the HTTPOnly flag in a Set-Cookie header for the session cookie, which makes it easier for remote attackers to obtain potentially sensitive information via script access to this cookie.

CVE-2014-3485
Published: 2014-07-11
The REST API in the ovirt-engine in oVirt, as used in Red Hat Enterprise Virtualization (rhevm) 3.4, allows remote authenticated users to read arbitrary files and have other unspecified impact via unknown vectors, related to an XML External Entity (XXE) issue.

CVE-2014-3499
Published: 2014-07-11
Docker 1.0.0 uses world-readable and world-writable permissions on the management socket, which allows local users to gain privileges via unspecified vectors.

CVE-2014-3503
Published: 2014-07-11
Apache Syncope 1.1.x before 1.1.8 uses weak random values to generate passwords, which makes it easier for remote attackers to guess the password via a brute force attack.

Best of the Web
Dark Reading Radio
Archived Dark Reading Radio
Marilyn Cohodas and her guests look at the evolving nature of the relationship between CIO and CSO.