Log-in Brute Forcing

Login Brute Forcing

Login brute-forcing is a systematic approach to discovering valid credentials by attempting numerous combinations against authentication systems. This technique uses computational power to test many possible username and password variations.

Mathematical Complexity

The total possible combinations in a brute force attack can be calculated as:

Possible Combinations = Character Set Size^Password Length

For example:

  • Lowercase letters only (26 characters): 26^8 = 208,827,064,576 combinations for an 8-character password

  • Lowercase + uppercase (52 characters): 52^8 = 53,459,728,531,456 combinations

  • Alphanumeric (62 characters): 62^8 = 218,340,105,584,896 combinations

  • Full ASCII printable (95 characters): 95^8 = 6,634,204,312,890,625 combinations

Attack Types

Dictionary Attack

Uses predefined lists of common usernames and passwords instead of generating all possibilities.

Hybrid Attack

Combines dictionary words with patterns, numbers, or special characters (e.g., password123, Password123!).

Rule-Based Attack

Applies transformation rules to dictionary words (capitalization, character substitution, etc.).

Credential Stuffing

Uses leaked credentials from other breaches to attempt access to different services.

Tools

Hydra

Hydra is a parallelized login cracker that supports numerous protocols.

Basic Syntax

HTTP POST Form

HTTP GET Form

SSH Brute Force

FTP Brute Force

SMB Brute Force

RDP Brute Force

Additional Options

Medusa

Ncrack

Defense Evasion

Rate Limiting

Space out login attempts to avoid triggering lockout policies:

Targeted Usernames

Use validated usernames instead of large lists:

Custom User Agents

Use realistic user agents to avoid detection:

Best Practices

  1. Always obtain proper authorization before performing brute force attacks

  2. Document all testing activities

  3. Use incremental approaches starting with targeted attempts before wider brute forcing

  4. Monitor for account lockouts to prevent denial of service

  5. Consider timing attacks to minimize impact on production systems

Last updated