DNSChanger
Template:Short description Script error: No such module "For".
Page Module:Infobox/styles.css has no content.
| DNSChanger | |
|---|---|
| Malware details | |
| Classification | Trojan horse |
| Family | DNSChanger |
| Isolation date | November 8, 2011 |
| Origin | Estonia |
| AuthorTemplate:Pluralize from text | Rove Digital |
| Technical details | |
| PlatformTemplate:Pluralize from text | Windows, OSX |
DNSChanger is a DNS-hijacking trojan horse.[1][2] The work of an Estonian company known as Rove Digital, the malware infected computers by modifying a computer's DNS entries to point toward its own rogue name servers, which then injected its own advertising into Web pages. At its peak, DNSChanger was estimated to have infected over four million computers, bringing in at least US$14 million in profits to its operator from fraudulent advertising revenue.[3]
Both Windows and Mac OS X variants of DNSChanger were circulated, the latter taking the form of a related trojan known as RSPlug. The FBI raided the malicious servers on November 8, 2011,[4] but they kept the servers up until July 9, 2012 to avoid affected users from losing Internet access.
Operation
DNSChanger was distributed as a drive-by download claiming to be a video codec needed to view content on a Web site, particularly appearing on rogue pornography sites. Once installed, the malware then modified the system's Domain Name System (DNS) configuration, pointing them to rogue name servers operated through affiliates of Rove Digital.[3] These rogue name servers primarily substituted advertising on Web pages with advertising sold by Rove. Additionally, the rogue DNS server redirected links to certain Web sites to those of advertisers, such as, for example, redirecting the IRS Web site to that of a tax preparation company.[5] The effects of DNSChanger could also spread itself to other computers within a LAN by mimicking a DHCP server, pointing other computers toward the rogue DNS servers.[5] In its indictment against Rove, the United States Department of Justice also reported that the rogue servers had blocked access to update servers for antivirus software.[6]
Shutdown and interim DNS servers
On October 1, 2011, as part of Operation Ghost Click (a collaborative investigation into the operation), the United States Attorney for the Southern District of New York announced charges against six Estonian nationals and one Russian national connected to DNSChanger and Rove Digital for wire fraud, computer intrusion, and conspiracy.[6] Estonian authorities made arrests, and the FBI seized servers connected to the malware located in the United States.[3]
Due to concerns by FBI agents that users still infected by DNSChanger could lose Internet access if the rogue DNS servers were shut down entirely, a temporary court order was obtained to allow the Internet Systems Consortium to operate replacement servers, which would serve DNS requests from those who had not yet removed the infection, and to collect information on those still infected in order to promptly notify them about the presence of the malware.[7] While the court order was set to expire on March 8, 2012, an extension was granted until July 9, 2012, due to concerns that there were still many infected computers.[5] F-Secure estimated on July 4, 2012, that at least 300,000 computers were still infected with the DNSChanger malware, 70,000 of which were located in the United States.[8] The interim DNS servers were officially shut down by the FBI on July 9, 2012.[9]
Impact from the shutdown was considered to be minimal, due in part to major Internet service providers providing temporary DNS services of their own and support to customers affected by DNSChanger. and informational campaigns surrounding the malware and the impending shutdown. These included online tools that could check for the presence of DNSChanger, while Google and Facebook provided notifications to visitors of their respective services who were still affected by the malware.[8] By July 9, 2012, F-Secure estimated that the number of remaining DNSChanger infections in the U.S. had dropped from 70,000 to 42,000.[9]
References
Page Template:Reflist/styles.css has no content.
- ^ Trojan:Win32/Dnschanger.O – Microsoft
- ^ Page Module:Citation/CS1/styles.css has no content."Antivirus scan for fdde13872caa1a0e1b9331188ca93b8fc424fed43d86d5cf53f6965f6a77184e] at 2017-01-30 04:47:37 UTC – VirusTotal". www.virustotal.com.
- ^ a b c Page Module:Citation/CS1/styles.css has no content."How the most massive botnet scam ever made millions for Estonian hackers". Ars Technica. 10 November 2011. Retrieved 6 July 2012.
- ^ Page Module:Citation/CS1/styles.css has no content."Esthost Taken Down – Biggest Cybercriminal Takedown in History – TrendLabs Security Intelligence Blog". 9 November 2011.
- ^ a b c Page Module:Citation/CS1/styles.css has no content."Don't Lose the Internet in July! FBI Repeats DNSChanger Warning". PC World. Retrieved 6 July 2012.
- ^ a b Page Module:Citation/CS1/styles.css has no content."Seven charged in malware-driven click fraud case". Ars Technica. 9 November 2011. Retrieved 6 July 2012.
- ^ Page Module:Citation/CS1/styles.css has no content.Zetter, Kim. "'DNSChanger' Malware Could Strand Thousands When Domains Go Dark on Monday". Wired. Retrieved 6 July 2012.
- ^ a b Page Module:Citation/CS1/styles.css has no content."Are You Infected With DNSChanger Malware?". PC World. Retrieved 6 July 2012.
- ^ a b Page Module:Citation/CS1/styles.css has no content."ISPs Report Minimal DNSChanger Impact". PC World. Retrieved 13 July 2012.
External links
- www.dcwg.org — DNS Changer Working Group; tools and information for diagnosing DNSChanger infections
Lua error in package.lua at line 80: module 'Module:Navbox/configuration' not found.
