Overview
THC-Hydra tests online logins — SSH, FTP, web forms, databases — against password lists, on services you own or are explicitly authorized to assess. Where Hashcat cracks stolen hashes offline, Hydra knocks on the front door, which makes it the right tool for answering: would a password-guessing attack against our login actually succeed?
It is loud by design: every attempt is a real login, so rate-limit it, warn your defenders, and prefer it against staging. Pair every cracked credential with the same remediation — lockout policy, MFA, and breached-password screening at registration.
Key features
- Dozens of protocols: SSH, FTP, HTTP(S), SMB, databases
- Parallel tasks with tunable aggression
- Username and password list combinators
- HTTP form brute force with success/failure matching
- Resume files for long assessments
- Free and open source (AGPL)
Install & first run
# Debian / Ubuntu / Kali
sudo apt install hydra
## Audit SSH on your lab host (4 parallel tasks)
hydra -l admin -P words.txt -t 4 ssh://192.168.1.10
## Audit a web login form on your staging app
hydra -l user@example.com -P words.txt 192.168.1.20 http-post-form "/login:email=^USER^&pass=^PASS^:Invalid credentials"
Real-world example
Your staging environment mirrors production logins. With approval, run Hydra with a small known-bad list against the staging SSH: two service accounts fall immediately. Those accounts get rotated, MFA-enforced, and added to the deploy checklist so production never ships them.
Common questions
Is Hydra free?
Yes. It is free and open source.
Why do I keep getting 'target refused'?
Wrong service module or port. Point -s at the real port and confirm the protocol with nmap first; hydra guesses the module, it does not detect it.
Is account lockout a risk?
Always. Hydra will happily lock every account on a real system. On authorized tests set -t low, -W between attempts, and agree a lockout threshold with the owner.
SSH keeps failing - why?
Modern OpenSSH limits auth attempts per connection (MaxAuthTries). Use -t 4 and expect slow progress; brute forcing SSH is usually the wrong approach.
Related tools
Hashcat
The fastest password recovery and auditing tool: measure hash-cracking resistance on your own hashes. Free, open source.
John the Ripper
Classic password auditing suite, best at slow hashes and encrypted files you own. Free, open source.
Related reading: Hydra Cheat Sheet: SSH, HTTP Form & Service Brute-Force Commands
Keep exploring: browse every assessment phase in the Pentest Hub.
Authorized testing only — only ever test systems you own or have explicit written permission to assess.
