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 установки+3 за 7 дней★ 27 ЗвездыMITсинхронизировано 22 часа назад
Установка
Ещё нет NotHoly CLI? Сначала установите её.
$ curl -fsSL https://notholy.com/install.sh | sh
$ notholy skills install noorqureshi/tools-hydra
Пишет в ~/.notholy/skills после проверки подписи и SHA-256.
ПодписьПодписано, ed25519
jwzIlQrnD6…YqC4tZCQ==CLI проверяет SHA-256 и подпись, прежде чем записать хоть один файл.
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.
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.
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.
hydra basics:bash
hydra -l user -P wordlist.txt ssh://target_ip # one user, password listhydra -L users.txt -P passwords.txt ftp://target_ip # user list + password listhydra -l administrator -P wordlist.txt rdp://target_iphydra -l root -P wordlist.txt mysql://target_iphydra -t 4 -l user -P wordlist.txt ssh://target_ip # -t = parallel tasks, keep lowhydra -R # resume an interrupted run
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.
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.
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.