Domain hijacking

Domain hijacking or domain theft is the act of changing the registration of a domain name without the permission of its original registrant, or by abuse of privileges on domain hosting and registrar software systems.

Not to be confused with Domain hack.

This can be devastating to the original domain name holder, not only financially as they may have derived commercial income from a website hosted at the domain or conducted business through that domain's e-mail accounts,[1] but also in terms of readership and/or audience for non-profit or artistic web addresses. After a successful hijacking, the hijacker can use the domain name to facilitate other illegal activity such as phishing, where a website is replaced by an identical website that records private information such as log-in passwords, spam, or even distribution of malware, causing additional damage to third-parties to the wrongful loss and wrongful gain of the domain[2]

Description

Domain hijacking can be done in several ways, generally by unauthorized access to, or exploiting a vulnerability in the domain name registrar's system, through social engineering, or getting into the domain owner's email account that is associated with the domain name registration.[3]

A frequent tactic used by domain hijackers is to use acquired personal information about the actual domain owner to impersonate them and persuade the domain registrar to modify the registration information and/or transfer the domain to another registrar, a form of identity theft. Once this has been done, the hijacker has full control of the domain and can use it or sell it to a third party.

Other methods include email vulnerability, vulnerability at the domain-registration level, keyloggers, and phishing sites.[4]

Responses to discovered hijackings vary; sometimes the registration information can be returned to its original state by the current registrar, but this may be more difficult if the domain name was transferred to another registrar, particularly if that registrar resides in another country. If the stolen domain name has been transferred to another registrar, the losing registrar may invoke ICANN’s Registrar Transfer Dispute Resolution Policy to seek the return of the domain.[5]

In some cases the losing registrar for the domain name is not able to regain control over the domain, and the domain name owner may need to pursue legal action to obtain the court ordered return of the domain.[6] In some jurisdictions, police may arrest cybercriminals involved, or prosecutors may file indict.[7]

Although the legal status of domain hijacking was formerly thought to be unclear,[8] certain U.S. federal courts in particular have begun to accept causes of action seeking the return of stolen domain names.[9] Domain hijacking is analogous with theft, in that the original owner is deprived of the benefits of the domain, but theft traditionally relates to concrete goods such as jewelry and electronics, whereas domain name ownership is stored only in the digital state of the domain name registry, a network of computers. For this reason, court actions seeking the recovery of stolen domain names are most frequently filed in the location of the relevant domain registry.[10] In some cases, victims have pursued recovery of stolen domain names through ICANN's (Uniform Domain Name Dispute Resolution Policy (UDRP), but a number of UDRP panels have ruled that the policy is not appropriate for cases involving domain theft. Additionally, police may arrest cybercriminals involved.[7][11][12][13][14]

Notable cases
  • During the original "dot com boom", there was extensive media coverage of the hijacking of "sex.com".[15]
  • Basketball superstar Mark Madsen unknowingly bought a "stolen" (or hijacked) URL by way of eBay auctions rather than the more common auction sites such as Snapnames.[16]
  • In 2015 Lenovo’s website and Google’s main search page for Vietnam were briefly hijacked.[17]

Prevention

ICANN imposes a 60-day waiting period between a change in registration information and a transfer to another registrar. This is intended to make domain hijacking more difficult, since a transferred domain is much more difficult to reclaim, and it is more likely that the original registrant will discover the change in that period and alert the registrar. Extensible Provisioning Protocol is used for many TLD registries, and uses an authorization code issued exclusively to the domain registrant as a security measure to prevent unauthorized transfers.[18]

There are certain steps that a domain-name owner can take to reduce the exposure to domain name hijacking.[19] The following suggestions may prevent an unwanted domain transfer:

  • Use strong email passwords and enable two-factor authentication if available.
  • Disable POP if your email provider is able to use a different protocol.
  • Tick the setting "always use https" under email options.
  • Frequently check the "unusual activity" flag if provided by your email service.
  • Use a two-step (two-factor) authentication if available.
  • Make sure to renew your domain registration in a timely manner—with timely payments and register them for at least five (5) years.
  • Use a domain-name registrar that offers enhanced transfer protection, i.e., “domain locking” and even consider paying for registry locking.
  • Makes sure your WHOIS information is up-to-date and really points to you and you only.
  • If you have 2500 or more domain names consider buying your own registrar.
  • Relief via the Inter-Registrar Dispute Process[4]

RFC’s

RFC 3375 - Generic Registry-Registrar Protocol Requirements RFC 3735 - Guidelines for Extending EPP RFC 3915 - Domain Registry Grace Period Mapping (e.g. Add Grace Period, Redemption Grace Period) RFC 4114 - Using EPP for ENUM addresses

  • RFC 5910 - Domain Name System (DNS) Security Extensions Mapping for the Extensible Provisioning Protocol (EPP) (obsoletes RFC 4310, DNSSEC)
  • RFC 5730 - Extensible Provisioning Protocol (EPP) (obsoletes RFC 4930, which obsoleted RFC 3730)
  • RFC 5731 - Extensible Provisioning Protocol (EPP) Domain Name Mapping (obsoletes RFC 4931)
  • RFC 5732 - Extensible Provisioning Protocol (EPP) Host Mapping (obsoletes RFC 4932)
  • RFC 5733 - Extensible Provisioning Protocol (EPP) Contact Mapping (obsoletes RFC 4933)
  • RFC 5734 - Extensible Provisioning Protocol (EPP) Transport over TCP (obsoletes RFC 4934)
gollark: An otatop?
gollark: You can make a P2P system where messages are just sent from computer to computer.
gollark: Ah. A binary image format. Cool.
gollark: As in, put that before the API is unloaded.
gollark: Also, I'd like to note that if you do```lualocal API_name = API_name -- (or _G.API_name maybe?)```it should work.

See also

References
  1. Simon, Ruth. "Cybercriminals Are Misappropriating Businesses' Web Addresses As a Result, Customers Can't Find the Real Companies on the Web". The Wall Street Journal. The Wall Street Journal. Retrieved 12 September 2016.
  2. Weslow, David. "Dealing with cybersquatting: the wisdom of thinking ahead". TBO: Trademarks & Brands Online. Retrieved 12 September 2016.
  3. "CLBR Featured Segment: David Weslow on Domain Theft". Cyber Law Radio. Retrieved 12 September 2016.
  4. "Domain Name Hijacking". 31 December 2014.
  5. "Registrar Transfer Dispute Resolution Policy". ICANN. Retrieved 12 September 2016.
  6. "Domain name theft: Knowing where to turn". TBO: Trademarks & Brands Online. Retrieved 12 September 2016.
  7. Mike Masnick (4 August 2009). "Criminal Prosecution For Domain Hijacking". Techdirt. Retrieved 19 June 2019.
  8. Smith, Gerry (29 September 2014). "When Hackers Steal A Web Address, Few Owners Ever Get It Back". The Huffington Post.
  9. Berkens, Michael. "Wiley Rein Files Suit Over 14 Stolen Domain Names: 9 Are 3 Letter .com's". The Domains.
  10. Allemann, Andrew (23 October 2014). "Lawsuit filed to recover stolen three letter domain names". Domain Name Wire. Retrieved 13 September 2016.
  11. "WIPO Arbitration and Mediation Center". Retrieved 12 September 2016.
  12. "WIPO Arbitration and Mediation Center". WIPO: World Intellectual Property Organization.
  13. "Mascot Media Circle, LLC dba OnlineMBA v. WhoIsGuard, Inc. / Ahmed Guettouche Case No. D2015-1209". WIPO: World Intellectual Property Organization. Retrieved 12 September 2016.
  14. "DECISION Donald Williams v. wangyan hong". Forum: Arbitration, Mediation, International. Retrieved 23 April 2017.
  15. Dawn Kawamoto. "Sex.com domain hijacker captured". CNET. Retrieved 19 June 2019.
  16. "Man Who Sold Web Domain to Mark Madsen Going to Jail | SLAM". Slamonline.com. 26 July 2011. Retrieved 19 June 2019.
  17. Kirk, Jeremy (26 February 2015). "Lenovo, Google websites hijacked by DNS attacks". PC World. Retrieved 12 October 2018.
  18. Internet Corporation For Assigned Names and Numbers (15 July 2005). "DOMAIN NAME HIJACKING: INCIDENTS, THREATS, RISKS, AND REMEDIAL ACTIONS" (PDF). Retrieved 17 October 2014.
  19. Cyger, Michael. "Help! My Domain Name Was Stolen (And 3 Ways to Recover It) – With David Weslow". Domain Sherpa. Retrieved 12 September 2016.
This article is issued from Wikipedia. The text is licensed under Creative Commons - Attribution - Sharealike. Additional terms may apply for the media files.