domains / families / security / hunt-brute-force

hunt-brute-force

combined

Hunt Missing/Weak Rate Limiting Hunt Missing/Weak Rate Limiting — login brute force, OTP/2FA brute force (10^6 keyspace), password-reset-token brute, credential stuffing, username/email enumeration via error-string / status-code / timing differences, weak password policy, missing CAPTCHA, IP-based rate-limit bypass via X-Forwarded-For and friends, ReDoS. Distinguishes hard lockout vs soft IP-throttle vs CAPTCHA-injection vs silent shadow-throttling (avoids false-negative 'no rate limit' conclusions). Medium to Critical depending on what the brute reaches (OTP→ATO = Critical).

When to use

• You have explicit, written authorization to assess the target in scope, and the task matches this skill's vulnerability class or technique within a bug-bounty or penetration-test engagement.
• You need the recon, exploitation, or validation workflow described below — executed strictly inside the approved scope.

When not to use

• Authorized scope only: the confirmation gate above is mandatory before any probing, exploitation, or credential-access command.
• Docs-only import: upstream helper scripts, commands, engine, and research assets are not bundled; reinstall tooling from the source repo when needed.
• Validate every finding (see `triage-validation`) before reporting; report via `report-writing`. Prefer a sandbox, disposable VM, or controlled lab.

Skill page

Conflict

The two copies share the same core methodology (four rate-limit states, shadow-throttle detector, crown-jewel targets), but each contains material steps the other lacks. The uphiago copy provides a detailed, step-by-step hunting methodology with specific bash loops for login rate-limit testing and OTP brute-force probing (including a 101-code PoC probe and a full 10^6 keyspace discussion). The sickn33 copy adds an 'Autonomous Testing Priority' section that prioritizes credential spraying and rate-limit detection within a turn budget, and includes a mandatory authorization confirmation gate. Crowning one copy would hide the other's unique operational constraints and procedural steps.