Robots Atlas>ROBOTS ATLAS
Safety

Typosquatting

1999ActivePublished: 29 November 1999Updated: 13 July 2026Published
Key innovation
Weaponises users' typos and spelling mistakes — the attacker registers domains, packages, or identifiers deceptively similar to real ones and captures traffic that was never meant to reach them.
Category
Safety
Abstraction level
Pattern
Operation level
RetrievalApplicationToolingData
Use cases
Attack: phishing (cloning bank / login portal sites)Attack: malware/ransomware distribution (Magniber via typo domains)Attack: credential theft (Diesel Vortex 2026, 1,600+ cases in logistics)Attack: cryptocurrency theft (blockchain naming systems, ENS/Unstoppable Domains)Attack: harvesting emails misaddressed to a companyAttack: base technique for HalluSquatting (AI-native evolution)Monetisation: ad parking on typo domains (~USD 500M/year estimated for the Google ecosystem, 2010)Law/defence: UDRP proceedings at WIPO (Lego spent ~USD 500k on 309 cases)Satire/protest: John Oliver's equifacks.com, experianne.com, tramsonion.com (2016)

How it works

1. Target selection: the attacker identifies a popular domain / package / blockchain handle (the victim needs high traffic for good ROI). 2. Variant generation: typos (transposition, insertion, deletion, substitution), alternate TLDs, plurals, ccTLD abuse (.cm/.co/.om), Unicode homoglyphs, foreign-language spellings. Tools like 'dnstwist' automate generating thousands of variants. 3. Registration: the attacker mass-buys/registers variants in a cheap registry (~USD 8-15 per domain per year, effectively free for PyPI/npm/GitHub packages, a few USD per ENS name). 4. Setup: (a) ad-parking — passive monetisation; (b) phishing page — clone of the real site to harvest passwords; (c) malware drop — drive-by download; (d) redirect to an affiliate link or competitor; (e) email catcher — collecting messages sent to a corporate typo domain. 5. Victim: the user makes a typo, clicks a spam link, or a script/app/AI assistant itself runs pip install typo-name. 6. Scaling: the attacker does not need to 'hit' a specific victim — a fraction of a percent of the domain's/package's users is enough. For a popular target (Google.com: millions of hits per day), 0.01% error rate yields hundreds of visits.

Problem solved

Typosquatting does NOT solve a problem — it IS an attack/exploitation of typing mistakes. It solves the ATTACKER'S problem: how to intercept traffic, transactions, or credentials without breaching the victim's infrastructure. Answer: seize a name the victim does not control that users will type by mistake.

Components

Target nameImitation target

The real, popular name the attacker will imitate: google.com, react (npm), vitalik.eth (ENS), amazonaws.com. Selection criterion: traffic volume × typo probability.

Official

Variant generatorScale automation

An algorithm / tool that produces potential typos: dnstwist, urlcrazy, custom scripts. Takes into account keyboard adjacency, common errors (transposition, insertion, deletion), Unicode homoglyphs, plurals, TLD swaps.

Typographical variantSwap/insert/omit/transpose letters (gogle.com, goggl.com, googlle.com, ggoogle.com).
TLD variantDifferent TLD: google.org, google.co, google.om.
Homoglyph variantVisually identical characters from Cyrillic/Greek alphabets (g0ogle.com with zero instead of o).
CombosquattingAppending a plausible word: google-support.com, google-login.com.
Doppelganger domainMissing or added period: googlecom.com, w.google.com as w.googlecom.

Official

Registration channelAttack infrastructure

The system where the attacker registers the name: DNS registrar (GoDaddy, Namecheap), package registry (PyPI, npm, RubyGems, crates.io), blockchain naming system (ENS, Unstoppable Domains, ADAHandles), certificate registry.

Official

Deception payloadExecution

What the user sees/executes after reaching the squatted name: site clone (phishing), advertising (parking), drive-by malware, affiliate redirect, email catcher, malicious package post-install script.

Official

Implementation

Implementation pitfalls
Brand owner failing to preemptively register variantsHigh

The company registers only google.com; goggle.com, gogle.com, google.co, google.om are left available to attackers. Lego spent ~USD 500k on UDRP AFTER the fact.

Fix:Preemptively register popular variants (top-20 from dnstwist) and TLD variants (.org/.net/.co/.io). Cost of a few hundred dollars per year versus UDRP costs and reputational damage.
Relying on 'the user will notice the mistake'Critical

Unicode homoglyphs (Cyrillic, Greek) are visually indistinguishable to the user. A doppelganger domain missing a period is often noticed only after login.

Fix:Deploy EV/OV certificates with clear organisation labelling, train users on phishing, roll out U2F/passkeys (phishing-resistant by design).
Package registry without package-signature moderationHigh

For years, PyPI/npm/RubyGems did not enforce maintainer identity verification; typosquatting a package (requests → requsts, python-dateutil → python-datetutil) was trivial.

Fix:Inside the organisation: proxy with a whitelist (Artifactory, Nexus), pre-install package scanning, Sigstore signatures / attestations, monitoring for new package uploads with the brand prefix.
Irreversibility of blockchain transactionsCritical

On ENS/Unstoppable Domains, cryptocurrency sent to the wrong address is irreversible. The victim has no UDRP or chargeback — the funds are gone.

Fix:Address verification via ENS reverse resolution + a whitelisted address book; hardware wallet with on-device confirmation; social recovery.

Evolution

Original paper · 1999 · US federal law amending 15 USC 1117 (sub-section (d)(2)(B)(ii)); the first formal legal recognition of typosquatting as an actionable offense · 106th United States Congress (S. 1255)
Anticybersquatting Consumer Protection Act (ACPA)
106th United States Congress (S. 1255)
1999
Anticybersquatting Consumer Protection Act (ACPA)
Inflection point

The US Congress passes ACPA — the first formal recognition of typosquatting as an actionable offense. Section 3(a) extends 15 USC 1117 with sub-section (d)(2)(B)(ii). Complements UDRP at WIPO (active since 1999).

2006
McAfee — the Goggle.com campaign as public proof of harm

McAfee documents the amount of malware installed via drive-by download on goggle.com — a typo of google.com. SpySheriff, a rogue anti-spyware, becomes the emblematic payload.

2010
Edelman & Moore — the first quantitative market analysis

Ben Edelman and Tyler Moore publish 'Measuring Typosquatting Perpetrators and Funders', showing that typosquatting generates ~USD 500M/year from Google typo domains alone (New Scientist 2010).

2016
John Oliver — satire as an educational tool

John Oliver, on 'Last Week Tonight', registers equifacks.com, experianne.com, tramsonion.com to demonstrate how trivial typosquatting is.

2019
US 2020 presidential election — 550+ typosquats

Digital Shadows reports detecting more than 550 typosquats related to the US 2020 presidential election (candidates, campaign committees).

2022
Magniber ransomware via typosquatting

malware.news documents Magniber ransomware distribution via Chrome/Edge typo domains — the first major malware family using typosquatting as its main vector.

2024
Typosquatting 3.0 — blockchain naming systems
Inflection point

Muzammil et al. (APWG eCrime 2024) publish the first large-scale measurement of typosquatting in ENS, Unstoppable Domains, ADAHandles. Thousands of cryptocurrency transactions sent to squatted addresses. IEEE doi:10.1109/eCrime60373.2024.10896082.

2026
Diesel Vortex — 1,600+ credentials in logistics

Have I Been Squatted + Ctrl-Alt-Intel report (February 2026) the 'Diesel Vortex' phishing campaign by a Russian-Armenian cybercrime group. Targets: freight and logistics companies in the US and Europe. Outcome: >1,600 unique credentials stolen from logistics platforms. CERT-EU issues Cyber Brief 26-03.

2026
HalluSquatting — AI-native evolution of typosquatting
Inflection point

July 2026: a Tel Aviv University + Technion + Intuit team publishes HalluSquatting. Instead of guessing user typos, the attacker determines which names LLMs hallucinate in code recommendations and pre-registers exactly those. A fundamental vector shift: from user typos to AI hallucinations.

Hyperparameters (configurable axes)

Name variant typeCritical

Which generation mechanism is used: classic typo, TLD swap, homoglyphs, combosquatting, doppelganger domain, ccTLD abuse.

typographicalSimplest, most effective for mass market.
homoglyphHard to spot visually; requires Unicode-aware detection.
combosquattingRequires no user typo — enough that the user does not know the real domain.
Target registry typeHigh

DNS (domain names), package registry (npm/pypi/rubygems/crates.io), blockchain naming (ENS/UD/ADAHandles), social handles (X, Instagram, GitHub org).

dnsClassic. ~USD 8-15/year/domain, legal recourse via UDRP.
package_registryNearly free, weaker moderation, high ROI (Magniber, HalluSquatting).
blockchainIrreversible transactions = high impact (Typosquatting 3.0, 2024).
Monetisation modeHigh

How the attacker profits: ad parking, credential phishing, malware distribution, affiliate marketing, cryptocurrency theft, selling the domain to the brand.

ad_parkingLowest legal risk, lowest per-user profit.
phishingHigh profit, high legal and takedown risk.

Execution paradigm

Primary mode
Conditional

The trigger is external (a human error, an LLM hallucination, IDE autocompletion), not in the attack code.

Activation pattern
Input dependent
Routing mechanism

Activation depends on what the victim types or what the name resolver picks (DNS, a package-registry resolver, a model search, or an LLM agent tool selector).

Parallelism

Parallelism level
Fully parallel

Hundreds or thousands of variants can be maintained in parallel; each one operates independently and only triggers when a victim mistakes it.

Scope
Inference
Constraints
!Scale is bounded only by the attacker's budget and the registry's own limits (DNS, PyPI, npm, ENS) — not by the technique itself.

Hardware requirements

Primary

Typosquatting is a social-engineering + registry attack — it does not depend on the CPU, GPU, TPU or accelerator. It appears wherever there is a namespace with name registration.