flarexes/check-breach

Checks If Password Ever Been Breached Via HaveIBeenPwned APIv3 Without Sending Original Password

check-breach

Checks If Password Ever Been Breached Via HaveIBeenPwned APIv3 Without Sending Original Password. Use Any One Of The Above check-breach Script.

Why This?

1. It's Easiar Then Web Inferface. CLI Is Always Better
2. I Don't Need To Share My Password With HaveIBeenPwned Site
3. It Usage K-Anonymity Model Which Allow Leaked Password Searching Without Disclosing The Real Password
4. Make You Realize That You Need A Password Manager Right Now!

Example

With Python

wget https://raw.githubusercontent.com/FlareXes/check-breach/main/check-breach.py     # No need to clone the repo

python check-breach.py <YOUR_PASSWORD>

python check-breach.py P@$$Od123

With Bash

wget https://raw.githubusercontent.com/FlareXes/check-breach/main/check-breach        # Don't need to clone the repo

chmod +x check-breach

./check-breach P@$$Od123

Note: check-breach Now Supports Password Breach Checks Without Echo By Not Pass Any Args. Just Run The Script Without Any Argument Then You'll Be Prompted With An Non Echo Input Field.

Password Input Without Echo

python check-breach.py
Password: ............

License

MIT License Copyright (c) 2022 FlareXes Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:

The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.

THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.