Re:Practical waterholing through DNS typosquatting
by YouKnowBetter on Friday June 23, 2017 @06:52AM
(#14618223)
The original idea has a better name: Bitsquatting[0]
"Experiment
To determine whether bit7errors can redirect connections to attacker controlled sites, the bitsquat domains in Table 3 were registered, and all HTTP requests to the domains were logged. The domains, such as li6e.com, mic2osoft.com, and fjcdn.net are very unlikely to be typos or keyboard errors."
Re:Practical waterholing through DNS typosquatting
by Bartweiss on Friday June 23, 2017 @04:01PM
(#14622288)
Thinking about high-profile domains: there are no close attacks on .gov (.gop is closest), but .mil is subject to both .mit (not so close) and .ml (Mali, quite close) attacks.
I.e. Register a domain where the ASCII representaton is 1 bit off.
"Experiment To determine whether bit7errors can redirect connections to attacker controlled sites, the bitsquat domains in Table 3 were registered, and all HTTP requests to the domains were logged. The domains, such as li6e.com, mic2osoft.com, and fjcdn.net are very unlikely to be typos or keyboard errors."
[0] https://media.blackhat.com/bh-us-11/Dinaburg/BH_US_11_Dinabu...
Typosquatting = human error
Bitsquatting = machine error (bitflip)