hunt-source-leak

Extract sensitive information from exposed source maps and configuration files.

3|1|Updated Jul 2, 2026
One-click install
npx skills add https://github.com/EntroVyx/hermes-agent-offsec --skill hunt-source-leak-entrovyx
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: hunt-source-leak
Source: https://github.com/EntroVyx/hermes-agent-offsec/tree/main/skills/offsec/redteam/hunt-source-leak
Command: npx skills add https://github.com/EntroVyx/hermes-agent-offsec --skill hunt-source-leak-entrovyx

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires git-dumper, ds_store, and includes references (resource) components.

What problem does it solve?

This skill identifies critical security vulnerabilities caused by accidentally exposed source code, build artifacts, and configuration files that often lead to full system compromise.

Core Features & Use Cases

  • Source Map Analysis: Reconstructs TypeScript/ES6 source code from .js.map files to find hardcoded secrets and internal logic.
  • Endpoint Discovery: Scans for exposed Swagger/OpenAPI definitions, .env files, and .git directories to map the entire attack surface.
  • Secret Scanning: Greps through extracted bundles and git history for API keys, database credentials, and internal hostnames.

Quick Start

Use the hunt-source-leak skill to scan the target domain for exposed source maps and configuration files.

Frequently Asked Questions about hunt-source-leak

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

FAQPage Schema
How do I find exposed secrets and internal API routes from source maps?

Exposed source maps allow reconstruction of TypeScript and ES6 source code from .js.map files. This reveals hardcoded credentials and internal API specifications left in build artifacts during web application recon.

How do I reconstruct source code from .js.map files during a pentest?

Reconstructing source code from .js.map files involves extracting bundled JavaScript mappings to recover original TypeScript and ES6 logic. This uncovers hardcoded secrets and internal hostnames for penetration testing reconnaissance.

Do I need git-dumper to scan for leaked configuration files and .git directories?

Git-dumper is required to dump exposed .git directories and reconstruct leaked assets. Curl and python3 are also needed to perform automated discovery of configuration files like .env and Swagger definitions.

What is the best way to discover internal API endpoints from exposed Swagger and OpenAPI definitions?

Scanning the target domain for exposed Swagger and OpenAPI definitions is the best way to discover internal API endpoints. This maps the attack surface by identifying configuration files and leaked API specifications.

Can I grep extracted git history for API keys and database credentials?

You can grep through extracted bundles and git history for API keys and database credentials. Secret scanning targets these reconstructed assets to find hardcoded credentials and internal hostnames.

What limitations exist when scanning .env files and build artifacts for hardcoded credentials?

Scanning .env files and build artifacts for hardcoded credentials is limited by target exposure; it only finds secrets if these files are accidentally exposed online. It also requires curl, python3, and git-dumper to function.