Jump to content

Botnet Attacks: Difference between revisions

From ICANNWiki
Elise (talk | contribs)
No edit summary
Elise (talk | contribs)
No edit summary
Line 52: Line 52:
==References==
==References==
<references/>
<references/>
[[Category:Bad Practice]]

Revision as of 21:54, 14 April 2015

This information is brought to you by
DNS Seal, a best practices wiki for DNS

Botnet Attacks involve networks of infected computers controlled by a hacker or "botherder"[1] without the consent of the computers' owners.[2][3] These infected computers can be used in complex cyberattacks, including but not limited to Fast Flux attacks where the controller uses the botnet to hide his or her location, Spam attacks, DDOS attacks, and Phishing attacks, all without the knowledge of the computer's owner.[1][3]

The term botnet comes from the combination of robot and network.[2] Sometimes botnets are referred to as zombie computers or zombie networks because they infect other computers.[1][4] They can also be hard to detect and shut down once they are established, especially when the average user may not realize they are part of one.[5] For example, when part of the Kelihos botnet was taken down, it reappeared within 4 months.[6]

Public Perception[edit | edit source]

Botnets are considered by the Internet security community to be a major threat to general security and personal information.[1][7] Individuals, however, may not be aware that their computers are infected, making botnets an insidious threat.

Outcome[edit | edit source]

Botnet attacks negatively affect the Internet community and many personal users though identity theft, poor computer performance, spam, and malware.

Historical Use[edit | edit source]

  • Botherders or controllers frequently target PCs without adequate security protection such as personal computers with Internet access.[8] Botherders can also create botnets by getting an Internet user to unintentionally download malware.[4] According to the GNSO's Registration Abuse Polices Working Group (RAPWG) report, botnet controllers can use registered or unregistered domains to give infected computers instructions or updates.[9] If the botnet had been communicating via a certain domain name and the name expires, the botnet may disappear temporarily but become active again when the domain is re-registered.[5]
  • According to a BBC news report, 5-10% of all computers are infected and act as part of a botnet.[5] Estimates about the relative sizes of botnets vary, starting with botnets as small as a few hundred computers leading up to botnets that exceed 50,000 compromised computers.[10] Some extensive botnets may have more than half a million infected computers.[7]
  • As stated in previous sections, botnets can be used in multiple ways that threaten Internet users. For example, botnets can relay information from individual computers back to the botherder by using keylogging software. This information, including passwords, credit cards, or bank account numbers, can then be used by the network controller.[8] Botnets can also be used in Distributed Denial of Service (DDoS) attacks, [8] fast flux attacks, phishing attacks, spam campaigns,[2] identity theft, clickfraud, and distributing malware.[1][11] Botnets can also affect mobile devices and phones, and a Symantec report stated that a botnet infected mobile app has generated anywhere from $1,600 to $9,000 per day.[6]
  • In 2014, the FBI in collaboration with law enforcement officials from multiple countries "disrupted" the Gameover Zeus botnet, which has allegedly been responsible for $100 million in losses.[12] This botnet is believed to comprise anywhere from 500,000 to 1 million computers.[12] The operator of this botnet could face bank fraud, wire fraud, conspiracy, and computer hacking charges.[12]

ICANN Policy[edit | edit source]

  • The GNSO's RAPWG looked at the issue of malware and botnet attacks as they may utilize registered or unregistered domain names.[9] However, some view botnets as outside the scope of ICANN policy.[9]
  • The 2013 Registry Agreement (RA), which all new gTLD applicants were required to sign, states that registries must require their registrars to include policies that prohibit registrants from activities like creating botnets.[13] Additionally, registries are required to "periodically conduct a technical analysis to assess whether domains in the TLD are being used to perpetrate security threats" and to keep security files on threats and the remedial actions taken by the registries.[13]

Legislation[edit | edit source]

  • The proposed Internet Spyware (I-Spy) Prevention Act and Cybersecurity Enhancement Act, neither of which passed the Senate, could have potentially create harsher punishments for cyber crimes.[16] In 2013, the EU approved new cyber-legislation that increases the culpability of botnet creators and sellers in addition to those that use them for criminal activities.[17]
  • Internet crimes, such as botnet attacks, are investigated by the Federal Trade Commission (FTC) and the FBI's cyber task force divisions.[4] In 2007, the FBI working in conjunction with New Zealand authorities and the U.S. Secret Service caught and prosecuted 8 people involved in botnet attacks.[18] The FBI's "Bot Roast" operations have "uncovered more than $20 million in economic loss and more than one million victim computers."[18]

Additional Resources[edit | edit source]

Related Articles[edit | edit source]

References[edit | edit source]

  1. 1.0 1.1 1.2 1.3 1.4 Bots and Botnets—A Growing Threat, Symantec Corporation
  2. 2.0 2.1 2.2 Botnet Attack Information, Kaspersky Lab
  3. 3.0 3.1 Botnets, Shadowserver.org
  4. 4.0 4.1 4.2 Botnets 101: What They Are and How to Avoid Them (June 5, 2013), Federal Bureau of Investigation
  5. 5.0 5.1 5.2 Zombie botnets: Why some crime networks refuse to die by Mark Ward (January 20, 2014), BBC
  6. 6.0 6.1 2013 Internet Security Report, Vol. 18 (PDF), Symantec Corporation
  7. 7.0 7.1 Security Threat Report 2014 (PDF), Sophos
  8. 8.0 8.1 8.2 botnet (zombie army) by Margaret Rouse (February 2012), SearchSecurity.com
  9. 9.0 9.1 9.2 Working Group Final Report; Submitted on May 29, 2010 (PDF), Internet Corporation for Assigned Names and Numbers (ICANN)
  10. Lessons Learned (August 10, 2008), The Honeynet Project
  11. Uses of botnets (August 10, 2008), The Honeynet Project
  12. 12.0 12.1 12.2 http://www.pcworld.com/article/2357820/law-enforcement-agencies-disrupt-gamover-zeus-botnet.html by Grant Gross (June 2, 2014) PCWorld
  13. 13.0 13.1 View the Updated Registry Agreement (PDF), Internet Corporation for Assigned Names and Numbers (ICANN)
  14. Botnet Bandit Sentenced In Federal Malware Case by Bill Singer (September 6, 2012), Forbes
  15. Computer Fraud and Abuse Act (CFAA), Thomson Reuters
  16. http://www.wired.com/politics/law/news/2007/06/bot_law
  17. EU approves stricter laws for punishing cyber crooks and botnet creators by Alastair Stevenson (July 5, 2013), v3.co.uk
  18. 18.0 18.1 'Bot Roast II' Nets 8 Individuals (November 29, 2007), Federal Bureau of Investigation