Common Types of Password Attacks and How to Prevent Them
Common password attacks include brute force (trying every combination), dictionary attacks (trying common words and passwords), password spraying (one common password against many accounts), credential stuffing (reusing leaked username and password pairs), offline cracking of stolen password hashes, phishing, keyloggers and infostealer malware, and MFA fatigue.
Topic: Active Directory & Identity Security in Cybersecurity & Ethical Hacking · Tutorial
Also covers: Ethical Hacking
Quick answer: Common password attacks include brute force (trying every combination), dictionary attacks (trying common words and passwords), password spraying (one common password against many accounts), credential stuffing (reusing leaked username and password pairs), offline cracking of stolen password hashes, phishing, keyloggers and infostealer malware, and MFA fatigue. Prevent them with long unique passwords stored in a password manager, multi-factor authentication (ideally passkeys or security keys), checks against breached passwords, login rate limiting and lockout, and strong password hashing such as Argon2id or bcrypt on the server side.
Key takeaways
- Reused passwords make credential stuffing easy; use a unique password per site.
- Length beats complexity rules; NIST favours long passphrases.
- MFA stops most password-only attacks; phishing-resistant MFA stops even more.
- Servers must hash passwords with slow algorithms and salts.
- Monitor for spraying and stuffing patterns across many accounts.
Table of Contents
- What Are the Main Password Attacks?
- What Is Offline Password Cracking?
- How Can Individuals Protect Their Passwords?
- How Should Organisations Defend Logins?
- How Should Passwords Be Stored?
- How Do You Detect Password Attacks?
- References
What Are the Main Password Attacks?
| Attack | How it works | MITRE ATT&CK |
|---|---|---|
| Brute force | Tries many combinations against one account | T1110.001 |
| Dictionary | Uses lists of common passwords and words | T1110.001 |
| Password spraying | Tries a few common passwords across many accounts | T1110.003 |
| Credential stuffing | Reuses leaked credentials from other breaches | T1110.004 |
| Offline cracking | Guesses against stolen password hashes | T1110.002 |
| Phishing | Tricks users into entering passwords on fake sites | T1566 |
| Infostealers and keyloggers | Malware steals saved or typed passwords | T1555 |
| MFA fatigue | Floods users with push prompts after stealing a password | T1621 |
| Default credentials | Uses factory passwords on devices | T1078.001 |
What Is Offline Password Cracking?
When attackers steal a database of password hashes, they can guess passwords on their own hardware without any lockout. Fast, unsalted hashes such as MD5 or SHA-1 make this easy; slow, salted algorithms make each guess expensive. That is why the OWASP Password Storage Cheat Sheet recommends Argon2id, scrypt or bcrypt.
How Can Individuals Protect Their Passwords?
- Use a password manager to create long, unique passwords for every account.
- Turn on MFA everywhere; prefer passkeys or security keys.
- Check whether your passwords appear in breaches with Pwned Passwords.
- Never enter passwords from links in messages; go to the site directly.
- Reject unexpected MFA prompts and report them.
How Should Organisations Defend Logins?
| Control | Stops |
|---|---|
| Phishing-resistant MFA (CISA) | Phishing, stuffing, spraying |
| Breached and common password blocking | Dictionary and stuffing |
| Rate limiting and smart lockout | Brute force and spraying |
| Number matching for push MFA | MFA fatigue |
| Changing default credentials | Device takeover |
| EDR and browser password policies | Infostealers |
NIST SP 800-63B Rev. 4 recommends allowing long passwords, checking them against compromised lists, and not forcing periodic changes. The OWASP Authentication Cheat Sheet covers implementation.
How Should Passwords Be Stored?
# Python: hash and verify with Argon2id (argon2-cffi library)
from argon2 import PasswordHasher
ph = PasswordHasher()
stored = ph.hash("correct horse battery staple")
ph.verify(stored, "correct horse battery staple") # raises an error if wrong
Never store passwords in plain text or with fast unsalted hashes.
How Do You Detect Password Attacks?
- Many failed logins from one IP across many accounts (spraying).
- Logins with valid passwords from unusual locations or devices (stuffing).
- Bursts of MFA prompts for one user.
- Windows event IDs 4625 (failed logon) and 4771 (Kerberos pre-authentication failed) in the SIEM.
Related: modern authentication methods and passkeys. WebAsha offers ethical hacking and identity security training.
References
Frequently Asked Questions
What's Your Reaction?
Like
0
Dislike
0
Love
0
Funny
0
Wow
0
Sad
0
Angry
0