hardcoded-credential-hunt

Detect hardcoded passwords in HTML forms, JavaScript, and API responses.

1.1k|191|Updated Jun 24, 2026
One-click install
npx skills add https://github.com/uphiago/recon-skills --skill hardcoded-credential-hunt
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: hardcoded-credential-hunt
Source: https://github.com/uphiago/recon-skills/tree/main/recon/hardcoded-credential-hunt
Command: npx skills add https://github.com/uphiago/recon-skills --skill hardcoded-credential-hunt

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Manually hunting for hardcoded credentials across HTML forms, JavaScript bundles, and API endpoints is time-consuming and prone to human error, especially during time-sensitive penetration tests or large-scale reconnaissance.

Core Features & Use Cases

  • HTML Form Scanning: Identifies pre-filled or hidden password fields in web forms that expose static credentials.
  • Config Endpoint Probing: Checks common unauthenticated configuration endpoints for leaked credential keys and values.
  • Debug Page Analysis: Extracts exposed secrets from framework debug error pages (Werkzeug, Django, Express) and inline JavaScript.
  • Use Case: During a web application penetration test, use this skill to quickly locate exposed admin passwords in a target's public /api/config endpoint without manual code review.

Quick Start

Use the hardcoded-credential-hunt skill to scan the target domain https://your-target.com for any hardcoded passwords in HTML forms, API configuration endpoints, and inline JavaScript code.

Frequently Asked Questions about hardcoded-credential-hunt

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I find hardcoded passwords in HTML forms and JavaScript?

To find hardcoded passwords in HTML forms and JavaScript, scan client-side web assets to detect pre-filled or hidden password fields and inline JavaScript secrets. This process identifies static credential leaks without requiring manual code review or brute force attacks.

Can I extract exposed secrets from framework debug error pages?

Yes, you can extract exposed secrets from framework debug error pages like Werkzeug, Django, and Express. Scanning these debug pages targets public-facing web applications to locate embedded credentials leaked during application errors.

What is the best way to scan API configuration endpoints for leaked credentials?

The best way to scan API configuration endpoints for leaked credentials is to probe common unauthenticated configuration endpoints. This targets API response payloads to identify leaked credential keys and values during reconnaissance workflows.

Does web pentest reconnaissance work for finding authentication bypass vulnerabilities?

Web pentest reconnaissance works for finding authentication bypass vulnerabilities by detecting hardcoded credentials embedded in client-side assets. Identifying these static credential leaks bypasses authentication controls without brute force or manual code review.

How do I check unauthenticated configuration endpoints during a web penetration test?

To check unauthenticated configuration endpoints during a web penetration test, probe the target domain's public-facing endpoints. This locates exposed admin passwords and leaked credential keys in API response payloads and configuration files.