PAGES
← all tools
◆ Password & Credential Cracking

hydra

v9.6 open-source

Network login brute-forcing cyber tool supporting parallelized attacks across 50+ protocols including SSH, FTP, HTTP, and RDPRDPA Microsoft protocol that lets a user view and control a remote Windows desktop over a network, giving cyber tools a standard channel to audit, attack-simulate, or monitor Windows systems remotely..

Summary

hydra is an open-source command-line tool for brute-forcing network login credentials, released under AGPLv3, and it runs parallelized attacks across more than 50 protocols including SSH, FTP, HTTP forms, SMBSMBA network file-sharing protocol developed by Microsoft that lets systems share files, printers, and named pipes over a network; cyber tools target or speak it because it is ubiquitous in Windows environments., RDP, and various database and mail services. It is aimed at penetration testers and security researchers who need to demonstrate weak or default credentials on a system rather than at defenders monitoring for such attempts. Its README describes it as filling a gap left by earlier login-attack tools that supported only a single protocol or lacked parallel connections, positioning it as a broader alternative to those single-purpose crackers. It can be pulled as a Docker image or built from source across Linux, Windows/Cygwin, BSD, and macOS. Development remains active, with 124 contributors, 71 commits in the past year, and a release roughly three months ago, most recently adding legacy SSH cipher support and updating its RDP module to freerdp v3.

Network login brute-forcing cyber tool supporting parallelized attacks across 50+ protocols including SSH, FTP, HTTP, and RDP.

How hydra helps

Which login on this service is actually using a default or weak password?

runs a wordlist or generated password set against the target with parallel connections and reports back the exact login and password pair that succeeded, with the attempt count and time taken

Can this old SSH server be tested with a modern client, or does it need legacy support?

negotiates deprecated ciphers and key-exchange algorithms such as arcfour or diffie-hellman-group1-sha1 so a server still requiring them can be attacked instead of rejected

Which of these credentials from a breach dump actually work against this system?

takes a colon-separated file of known logins and passwords and tries each pair against the target, reporting which combinations authenticate

Will this web login form actually reject bad credentials, or does it quietly accept them?

drives the HTTP form with generated or listed credentials, distinguishing failure responses including 403s from an actual authenticated session

Are the same weak credentials reused across different services on this host?

runs the same login/password lists against multiple protocol modules (FTP, SSH, IMAP, SMB, and others) against the same target so reused passwords surface across services

Does this SMB target's handling of expired credentials let an attack slip through undetected?

accounts for expired-credential responses from the SMB module so those replies are not misread as a valid or invalid login during a spray

all 4 features, with the evidence for each →

Languages

Not documented

Features

4 capabilities · 2 backed by code, an API document or a real run

Built from hydra's releases, docs, README and our own runs. “Seen” marks the month we first spotted a release the vendor didn't date. Group names and tags are our labels.

Compare with peers →

What hydra offers you

  • Command-line interface1
All capabilities 4 capabilities
Credential brute-force and spray attacks verified Attempts to authenticate against network services (FTP, SSH, HTTP login forms) using wordlists or generated credential pairs to find valid logins. 9 releases · 16 other sources · first seen May 2017

release 9 total

  • Improves SMB module handling of expired-credential responses. v9.6 · Sep 2025 · source · release history
  • Supports HTTP 403 responses, expanding coverage for web form attacks where targets return 403 on failure. v9.6 · Sep 2025 · source · release history
  • Supports SSH legacy ciphers, enabling brute-force against older SSH servers that require deprecated algorithms. v9.6 · Sep 2025 · source · release history
  • http-post-form module now supports the 2= optional parameter to treat HTTP 302 responses as successful credentials. v9.4 · Sep 2022 · source · release history
  • Enables -M flag to accept IPv6 addresses or ranges v9.3 · Feb 2022 · source · release history
  • Adds new cobaltstrike module for credential testing (contributed by ultimaiiii) v9.3 · Feb 2022 · source · release history

command line

  • -y — disable use of symbols in -x bruteforce, see above v8.5 · May 2017 · command-line history

we ran it

  • The tool tried 1 credential pair and found a valid match: login ftpuser with password ftppass on the target FTP server. Aug 2026 · the full run

example 14 total

  • Attack an older SSH server that requires legacy ciphers (e.g., arcfour, diffie-hellman-group1-sha1) that modern clients reject by default. hydra -l root -P /usr/share/wordlists/rockyou.txt ssh://<target> v9.6 · Sep 2025 · source
  • Force hydra to accept a redirect (302) from an API endpoint instead of logging it as a failed login attempt. hydra -l user -P wordlist.txt http-post-form "/login:username=^USER^&password=^PASS^:2=302" v9.4 · Sep 2022 · source
  • Target an IPv6 address or range using the -M flag hydra -l user -P pass.txt -M [2001:db8::]/64 ssh v9.3 · Feb 2022 · source
  • Add a new smb3 target to enumerate credentials over the SMB protocol. hydra -l user -P pass.txt -t 16 smb2://10.0.0.5 v9.1 · Jul 2020 · source
  • Match login success by verifying specific strings in the HTTP response body or status code. hydra -l admin -P wordlist.txt http-post-form "/login:user=^USER^&pass=^PASS^:F=Login succeeded:S=302" v9.1 · Jul 2020 · source
  • IMAP login with module option hydra -l test -p test imap://127.0.0.1/PLAIN
Scan performance tuning shipped Disables retry attempts on failed connections to optimize throughput for mass scanning workflows. 1 release · 1 other source · first seen Jul 2020

Also counts toward: Command-line interface

release

  • Adds -K command line switch to disable redo attempts for mass scanning workflows v9.1 · Jul 2020 · source · release history

example

  • Disable automatic retry on failed connections to speed up large-scale scans of many hosts. hydra -l admin -P passwords.txt -K ssh://192.168.1.1 v9.1 · Jul 2020 · source
SMB credential enumeration shipped Enumerates credentials over the SMB protocol, supporting versions 2 and 3. 1 release · 1 other source · first seen Jul 2020

release

  • Adds smb2 module supporting SMB3 protocol via libsmbclient-dev v9.1 · Jul 2020 · source · release history

example

  • Add a new smb3 target to enumerate credentials over the SMB protocol. hydra -l user -P pass.txt -t 16 smb2://10.0.0.5 v9.1 · Jul 2020 · source
Debug mode verified Enables debug output during a run to aid in diagnosing tool behaviour. 1 other source · first seen May 2017

command line

Lines in monospace are the tool's own words: help text parsed from its source, or an endpoint from its API document. Under release, a line is our summary of a dated release. Under docs, it is quoted from the tool's own documentation or website. Each links back to the source it came from.

Score card

  1. Shipping velocity releases a month, last 12 months
  2. Documentation quality release-notes rubric, 0–100
  3. Breaking-change discipline how rarely a release breaks users, and notice given
  4. Maintenance risk quiet time against its own cadence, maintainers
  5. Innovation & surface new capabilities, API and MCP surface
  6. Community health
  7. Contributor trend distinct committers, this year against last
  8. Maintainer concentration bus factor now against a year ago
  9. Issue backlog trend issues closed per issue opened, 12 months
  10. Responsiveness median time to a maintainer’s first reply

Nine scores for hydra, each built from the releases, notes and API history this site tracks — and, on Researcher and Business, where it stands among every measured tool in its category and how that has moved.

Score cards are part of every paid plan.

See plans →

Each score is 0–100 on a published rubric, derived from data this site already shows. A dimension we cannot measure says so — it is never scored 0 and never enters a rank.

How this is scored
  • Shipping velocity — releases a month over the last 12 months, on a log scale where 16 a month scores 100. Needs 3 releases in the window.
  • Documentation quality — the release-notes rubric published on the analytics page, unchanged.
  • Breaking-change discipline — the share of releases carrying a breaking change (none scores 100, half or more scores 0). Only projects that label breaking changes are measured: a clean record cannot be told from an unlabelled one.
  • Maintenance risk — quiet time measured against the tool's own release cadence (quiet longer than 90 days and three typical gaps scores 0), plus the number of active maintainers and whether contributors are growing, where known. Higher is lower risk.
  • Innovation & surface — new capabilities in the feature ledger this year, API and MCP operations added, and the share of commits that are features: the mean of whichever we hold.
  • Community health (open-source tools only) — each is a direction, not a size: contributors this year against last, the bus factor now against a year ago, and issues closed per issue opened, where steady scores 50, doubled 100 and halved 0; plus the median time to a maintainer's first reply (an hour scores about 100, a month or more 0). A commercial card has no repository and carries none of the four.
  • Documented delivery (commercial tools) — when a vendor's documented new capabilities have slowed against its own baseline, that counts against the overall standing as heavily as two low dimensions. Steady delivery, or too little history to judge, leaves the standing alone; it is never a sixth score.
  • Open-source tools are scored on repository signals; commercial tools on their published changelog. Ranks compare tools within one category and one profile and need at least five measured peers; the overall standing needs three ranked dimensions. Best-in-breed or consolidator is a shape, not a quality, and is never scored.

Release-note detail over time

See how much detail hydra puts in its release notes, quarter by quarter, and compare it with tracked tools in the same category. This history uses up to ten retained, reviewed notes per tool; sparse or blank older quarters may reflect that limit.

Checking release-note history…

Explore the full chart →

Releases

Show

5 entries

  1. September 20251
  2. September 20221
  3. February 20221
  4. March 20211
  5. July 20201
    Show

    5 entries

    Project health

    Issue, contributor and maintainer activity in vanhauser-thc/thc-hydra, 2023-10 – 2026-09, as of 2026-09-25. Twelve-month figures first; the trend lines run the whole window.

    1. Contributors 17 +5 vs prior 12 months
    2. Maintainers 4 +3 joined · −3 left, last 12 months
    3. Bus factor 2 committers behind half the commits
    4. Community-filed 100% of issues opened, last 12 months
    5. Median time to close 9.8 days first maintainer reply 20 hours
    6. Open backlog 47 of 810 issues ever filed
    1. Issues opened / month 0 · 0 communitymaintainers
    2. Open backlog 47
    3. Contributors / month 0
    4. Commits / month 0
    5. Stars 12,289
    Issue themes, last 12 months
    • features 3%
    • other 97%

    Counts from the project's public repository and git history; no individuals are identified. Maintainers are the committers covering 80% of the last year's commits. how we measure this

    Articles

    1 article · updated Nov 4, 2026

    Where hydra turns up in what others publish: how-tos, attack reports that name it, and incident write-ups. A row says why it is here and quotes where the article names it; the link goes to the publisher.

    Tutorials & guides 1

    • A Detailed Guide on Hydra Hacking Articles
      Pentesters, this article is about a brute-forcing tool Hydra.
      2 more quotes
      Hydra is one of the favourite tools of security researchers and consultants.
      In this article, I have discussed each option available in hydra to make brute force attacks in various scenarios.

    Libraries its release ships

    What its latest release locks, checked against known advisories.

    None of its release's images build from a lockfile we can read.

    Add the badge to your README

    Maintain this project? The badge links readers straight to this page, so they can follow every release here.

    Tracked by Cyber Toolchain Choose a badge style and copy the code →
    browse all tools → score card for your toolchain →