Credential stuffing/washing is taking a dump from a previous breach, such as those listed on 'haveibeenpwned.com', and trying them against a whole host of websites. This often works wonders as people re-use the same password elsewhere.
This is different to what people refer to as 'brute forcing' an account, where they would target one specific account and try multiple passwords. This is easy to pick up and block. However credential stuffing on an individual user level is less obvious. You could look at login attempts per IP, but they often utilise open proxies or Tor to help being detected.
Was your password unique to your Amazon account? And by unique I mean no re-used terms and tweaking just the numbers at the end etc. e.g. hunter2, hunter2017
>This often works wonders as people re-use the same password elsewhere. Was your password unique to your Amazon account?
I really doubt it. The way password managed and password used on this Amazon account is HackerNews approved.
As I mentioned in #1107: we will not be
removing analytics support entirely. It
is extremely useful to us and we have
already weighed the cost/benefit of
using tracking.
“The Party seeks power entirely for its own sake. We are not interested in the good of others; we are interested solely in power, pure power.”Mozilla Developer also mentioned:
Actually, @muffinresearch pointed out we could probably just observe Do Not Track here,
because this pane is actually a web page loaded in an iFrame inside the browser page.
That might be faster to ship. Just thinking aloud :smile:
I'm definitely for giving users the option to disable this.
“Power is in tearing human minds to pieces and putting them together again in new shapes of your own choosing.”- 1984, George Orwell.
https://www.facebook.com/l.php?u=https://www.wsj.com/article...