Agent skill · security · davila7
Broken Authentication Testing
This skill should be used when the user asks to "test for broken authentication vulnerabilities", "assess session management security", "perform credential stuffing tests", "evaluate password policies", "test for session fixation", or "identify authentication bypass flaws". It provides comprehensive techniques for identifying authentication and session management weaknesses in web applications.
Why this skill is useful
Provides specific methodologies and commands for testing authentication vulnerabilities that the AI wouldn't reliably generate on its own.
What it needs
Requires burp suite, hydra installed locally. About 7k tokens when loaded. Last updated 2026-08-06. 30,138 stars on the source repository.
What this skill does
Broken Authentication Testing Purpose Identify and exploit authentication and session management vulnerabilities in web applications. Broken authentication consistently ranks in the OWASP Top 10 and can lead to account takeover, identity theft, and unauthorized access to sensitive systems. This skill covers testing methodologies for password policies, session handling, multi-factor authentication, and credential management. Prerequisites Required Knowledge HTTP protocol and session mechanisms Authentication types (SFA, 2FA, MFA) Cookie and token handling Common authentication frameworks Required Tools Burp Suite Professional or Community Hydra or similar brute-force tools Custom wordlists for credential testing Browser developer tools Required Access Target application URL Test account credentials Written authorization for testing Outputs and Deliverables 1. Authentication Assessment Report - Document all identified vulnerabilities 2. Credential Testing Results - Brute-force and dictionary attack outcomes 3. Session Security Analysis - Token randomness and timeout evaluation 4. Remediation Recommendations - Security hardening guidance Core Workflow Phase 1: Authentication Mechanism Analysis Understand the application's authentication architecture: Capture and analyze authentication requests: Phase 2: Password Policy Testing Evaluate password requirements and enforcement: Document policy gaps: Minimum length <8, no complexity, common passwords allowed, username as password. Phase 3: Credential Enumeration Test for username enumeration vulnerabilities: Password reset "Email sent if account exists" (secure) "No account with that email" (leaks info) API responses {"error": "usernotfound"} {"error": "invalidpassword"} bash Using Hydra for form-based auth hydra -l admin -P /usr/share/wordlists/rockyou.txt \ target.com http-post-form \ "/login:username=^USER^&password=^PASS^:Invalid credentials" Using Burp Intruder 1. Capture login request 2. Send to Intruder 3. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills davila7/broken-authentication