Explore our new Cybersecurity Terms Glossary, explained by our experts.

View the Glossary View the Glossary
PRIVIA

Cybersecurity Terms Glossary

What Is Hydra?

Hydra is a parallelised online login cracker that tests username and password combinations against more than fifty network services, from SSH and RDP to web forms and databases.

Illustration for the cybersecurity term Hydra
Home / Blog / Cybersecurity Terms / What Is Hydra?
17 November 2026

What Is Hydra?

What Is Hydra?

Hydra, often written THC-Hydra after the group that produced it, is a tool for testing credentials against live network services. It is given a list of usernames, a list of passwords, a target, and a protocol, and it attempts logins in parallel until something succeeds or the lists are exhausted. It supports more than fifty services, including SSH, RDP, SMB, FTP, Telnet, LDAP, VNC, SMTP, POP3, IMAP, SNMP, MSSQL, MySQL, PostgreSQL, and HTTP forms.

It has been in use since 2000 and remains in the toolkit mainly because nothing about the underlying problem has changed. Services that accept passwords over the network will keep accepting attempts until something stops them.

Online Versus Offline

The distinction governs everything about how this attack behaves. An offline attack against captured hashes, as performed by Hashcat, is limited only by hardware and produces no evidence anywhere. An online attack is limited by the service and leaves evidence in every log the service writes.

Online attacks are therefore slow, noisy, and risky for the attacker, and the correct response is to make them more so. Every failed attempt should be recorded, every pattern should be visible, and the cost of each guess should be made to rise.

This also explains why competent attackers rarely use Hydra in the way beginners expect. Running a million passwords against one account triggers lockout in seconds and generates an obvious alert. The productive technique is the inverse: a small number of likely passwords tried against a large number of accounts, slowly, staying below the lockout threshold. That is password spraying, and it remains one of the most reliable routes into an organisation.

How It Is Used in Testing

In an authorised engagement, Hydra is typically pointed at a specific service after enumeration has produced a username list and the password policy is known. Default and vendor credentials are tested first, because they work far more often than anyone expects, particularly on network devices, management interfaces, databases, and industrial equipment. A small targeted list built from the organisation’s name, location, and season follows.

Web form support is the fiddliest part, because the tool has to be told how to recognise failure. Hydra needs the form fields, the submission path, and a string that appears in the response on an unsuccessful attempt. Applications that respond identically to a wrong username and a wrong password make this harder, which is precisely why they should.

Account lockout is a genuine hazard during testing. Locking out several hundred staff is a service disruption, so a professional engagement establishes the lockout threshold first, keeps attempts well below it, and agrees the approach in the rules of engagement.

Controls That Work

Detection

This is one of the easier things to detect, provided the logs are collected.

Tools such as fail2ban handle the response automatically on Linux hosts, and conditional access policies do the equivalent for cloud identity. The NCSC’s guidance on password administration recommends throttling and monitoring over aggressive lockout, for exactly the reasons above.

At Privia Security, our Penetration Test Services include controlled credential testing with lockout thresholds agreed in advance.

FAQ – Frequently Asked Questions

What Is the Difference Between Hydra and Hashcat?

Hydra attacks live services over the network, so it is limited by the service’s speed, rate limiting, and lockout policy, and it leaves log entries for every attempt. Hashcat attacks captured hashes offline at billions of guesses per second, limited only by hardware, and generates no logs anywhere. The two are used at different stages and defended against in entirely different ways.

Does Account Lockout Stop This Attack?

It stops naive attacks against single accounts and introduces a denial-of-service problem of its own, since an attacker can lock out an entire workforce deliberately. It does not stop password spraying, which stays below the threshold by design. Progressive delays, rate limiting, breached password screening, and multi-factor authentication are more effective and less disruptive.

Which Services Are Attacked Most Often?

Internet-exposed RDP and SSH lead by a wide margin, followed by VPN portals, webmail and Exchange, and management interfaces on network devices and hypervisors. Legacy protocols that bypass modern authentication, such as IMAP and SMTP basic authentication, are a persistent problem because they are often exempt from the multi-factor policy applied everywhere else.

Is Running Hydra Against Our Own Systems Risky?

It can be. Mass authentication failures lock out accounts, and locking out several hundred staff is a service disruption rather than a test finding. Establish the lockout threshold first, keep attempts well below it, agree the approach in the rules of engagement, and notify the service desk so that a wave of calls is not mistaken for an outage.

Related Terms

You May Be Interested In These

What Is an Indicator of Attack?

Cybersecurity Terms

17 November 2026

What Is an Indicator of Attack?

Read More
What Is Kerberos Armouring (FAST)?

Cybersecurity Terms

17 November 2026

What Is Kerberos Armouring (FAST)?

Read More
What Is the OSCP Certification?

Cybersecurity Terms

17 November 2026

What Is the OSCP Certification?

Read More