This is a enhanced version of Dropbox's zxcvbn library.
zxcvbn
is a password strength estimator inspired by password crackers. Through pattern matching and conservative estimation, it recognizes and weighs 30k common passwords, common names and surnames according to US census data, popular English words from Wikipedia and US television and movies, and other common patterns like dates, repeats (aaa
), sequences (abcd
), keyboard patterns (qwertyuiop
), l33t speak, and also "strong" passwords that satisfy many website's rules for passwords, but still leaked.
Consider using zxcvbn as an algorithmic alternative to password composition policy — it is more secure, flexible, and usable when sites require a minimal complexity score in place of annoying rules like "passwords must contain three of {lower, upper, numbers, symbols}".
- More secure: policies often fail both ways, allowing weak passwords (
P@ssword1
) and disallowing strong passwords. - More flexible: zxcvbn allows many password styles to flourish so long as it detects sufficient complexity — passphrases are rated highly given enough uncommon words, keyboard patterns are ranked based on length and number of turns, and capitalization adds more complexity when it's unpredictaBle.
- More usable: zxcvbn is designed to power simple, rule-free interfaces that give instant feedback. In addition to strength estimation, zxcvbn includes minimal, targeted verbal feedback that can help guide users towards less guessable passwords.
For further detail and motivation, please refer to the USENIX Security '16 paper and presentation.
try zxcvbn interactively to see these docs in action.
zxcvbn(password, (user_inputs = []));
zxcvbn()
takes one required argument, a password, and returns a result object with several properties:
{
guesses : number, // estimated guesses needed to crack password
guesses_log10 : number, // order of magnitude of guesses
crack_times_seconds : // dictionary of back-of-the-envelope crack time estimations, in seconds, based on a few scenarios:
{
// online attack on a service that ratelimits password auth attempts.
online_throttling_100_per_hour : number,
// online attack on a service that doesn't ratelimit, or where an attacker has outsmarted ratelimiting.
online_no_throttling_10_per_second : number,
// offline attack. assumes multiple attackers, proper user-unique salting, and a slow hash function
// w/ moderate work factor, such as bcrypt, scrypt, PBKDF2.
offline_slow_hashing_1e4_per_second : number,
// offline attack with user-unique salting but a fast hash function like SHA-1, SHA-256 or MD5. A wide range of
// reasonable numbers anywhere from one billion - one trillion guesses per second, depending on number of cores
// and machines. ballparking at 10B/sec.
offline_fast_hashing_1e10_per_second : number,
},
crack_times_display, // same keys as result.crack_times_seconds, with friendlier display string values: "less than a second", "3 hours", "centuries", etc.
score : number, // Integer from 0-4 (useful for implementing a strength bar)
// 0 - too guessable: risky password. (guesses < 10^3)
// 1 - very guessable: protection from throttled online attacks. (guesses < 10^6)
// 2 - somewhat guessable: protection from unthrottled online attacks. (guesses < 10^8)
// 3 - safely unguessable: moderate protection from offline slow-hash scenario. (guesses < 10^10)
// 4 - very unguessable: strong protection from offline slow-hash scenario. (guesses >= 10^10)
feedback : // verbal feedback to help choose better passwords. set when score <= 2.
{
warning : string, // explains what's wrong, eg. 'this is a top-10 common password'. Not always set -- sometimes an empty string
suggestions : string[], // a possibly-empty list of suggestions to help choose a less guessable password. eg. 'Add another word or two'
},
sequence : [], // the list of patterns that zxcvbn-typescript based the guess calculation on.
calc_time : number // how long it took zxcvbn-typescript to calculate an answer in milliseconds.
}
The optional user_inputs
argument is an array of strings that zxcvbn-typescript will treat as an extra dictionary. This can be whatever list of strings you like, but is meant for user inputs from other fields of the form, like name and email. That way a password that includes a user's personal information can be heavily penalized. This list is also good for site-specific vocabulary — Acme Brick Co. might want to include ['acme', 'brick', 'acmebrick', etc].
zxcvbn operates below human perception of delay for most input: ~5-20ms for ~25 char passwords on modern browsers/CPUs, ~100ms for passwords around 100 characters. To bound runtime latency for really long passwords, consider sending zxcvbn()
only the first 100 characters or so of user input.
Dan Wheeler for the initial zxcvbn project. Dropbox for supporting open source!
Tony Richards for the Typescript version.
Mark Burnett for releasing his 10M password corpus and for his 2005 book, Perfect Passwords: Selection, Protection, Authentication.
Wiktionary contributors for building a frequency list of English words as used in television and movies.
Researchers at Concordia University for studying password estimation rigorously and recommending zxcvbn.
And xkcd for the inspiration 👍🐴🔋❤️