Passwords being stored as hashes doesn't necessarily mean a breach can't expose them.
This is a dev post classified by Jev as Security (a tutorial), kept by the Dev Radar because it carries real work, not commentary.
Passwords being stored as hashes doesn't necessarily mean a breach can't expose them. It just means the attacker doesn't immediately get the original password. For example If you're password is (MyPassword123) it's usually hashed , then store in the database When hackers steal that database, they get the hash, not "MyPassword123". But now they can try to crack it offline. Tools like Hashcat and John the Ripper can take millions or even billions of password guesses, hash them using the same algorithm, and compare the results against the stolen hashes. If someone used a weak password li
Posted by 𝐇𝐚𝐦𝐳𝐚 | Networking Guy (13.1k followers) 4 days ago · 82 likes · 4.1k views · view the original post on X. Kept by the Dev Radar as Security.
More dev work like this
- Security teams shouldn't have to wait for a critical vulnerability to trigger an… — @thenewstack
- Cloudflare just turned AI agents into SECURITY AUDITORS. — @tonysimons_
- Wow, these slides are fantastic to just read through and contemplate. 😍… — @zooko
- How hackers use SQL Injection to compromise a website — @Hamzaonchain
- Dostlar selamlar, globaldeki en büyük Cybersecurity SFT finetuning datasetlerinden olan… — @AlicanKiraz0
- Cloudflare 团队把其内部找漏洞的那套方法做成了一个 Skill，叫 security-audit，并开源了。 — @GitHub_Daily
- Practical Social Engineering: A Primer for the Ethical Hacker! #BigData #Analytics… — @gp_pulipaka
- Scans emails and usernames across 715+ platforms to map digital footprints and verify… — @tom_doerr
Every post is read and classified by Jev (TypeSafe): what it is, which market it belongs to, and whether the link is a real tool. 14.4k posts from 4.7k X accounts over the last 21 days, 1.6k tools, 12 markets. Collected every 5 minutes, fully re-ranked every hour — last update 2026-09-19 21:10 UTC. Full method.