pentest-secrets-exposure
This Claude Code skill performs systematic detection of hardcoded credentials, leaked API keys, exposed configuration files, and sensitive data disclosure across source code, git history, web endpoints, and client-side bundles. Use it during authorized penetration testing engagements with explicit scope covering source code access to identify information exposure vulnerabilities across WSTG categories CONF-03/04, INFO-05, and ERRH-01/02.
git clone --depth 1 https://github.com/jd-opensource/JoySafeter /tmp/pentest-secrets-exposure && cp -r /tmp/pentest-secrets-exposure/skills/pentest-secrets-exposure ~/.claude/skills/pentest-secrets-exposureSKILL.md
# Pentest Secrets Exposure ## Purpose Spans multiple unchecked WSTG categories — CONF-03/04 (sensitive files, backups), INFO-05 (info leakage), ERRH-01/02 (error handling, stack traces). Shannon's pre-recon focuses on architecture, not systematic secrets discovery. ## Prerequisites ### Authorization Requirements - **Written authorization** with source code access scope (if white-box) - **Git repository access** for history mining (if applicable) - **Target URL list** for exposed file probing ### Environment Setup - TruffleHog for git history secret scanning - GitLeaks for pattern-based secret detection - Semgrep with secrets ruleset - nuclei with exposure templates ## Core Workflow 1. **Source Code Secrets**: Scan for hardcoded API keys, DB credentials, JWT signing keys, encryption keys using pattern + entropy detection. 2. **Git History Mining**: Search all commits for secrets added then removed. Check force-pushed branches. Analyze .gitignore for sensitive patterns. 3. **Exposed Config Files**: Probe for .env, .git/config, .DS_Store, wp-config.php, application.yml, docker-compose.yml with credentials (WSTG-CONF-03/04). 4. **Error Handling Disclosure**: Trigger stack traces, debug pages, verbose errors revealing internal paths, DB schemas, framework versions (WSTG-ERRH-01/02). 5. **Backup & Unreferenced Files**: .bak, .old, .swp, ~files, editor temp files, DB dumps, log files with sensitive data. 6. **Client-Side Bundle Analysis**: Extract API keys from JS bundles, source maps exposing server code, hardcoded tokens in mobile packages. 7. **Secret Validation**: Test each discovered credential for active access, document scope, assess blast radius. ## WSTG Coverage | WSTG ID | Test Name | Status | |---------|-----------|--------| | WSTG-CONF-03 | Test File Extensions Handling for Sensitive Info | ✅ | | WSTG-CONF-04 | Review Old Backup and Unreferenced Files | ✅ | | WSTG-INFO-05 | Review Webpage Content for Information Leakage | ✅ | | WSTG-ERRH-01 | Test Improper Error Handling | ✅ | | WSTG-ERRH-02 | Test Stack Traces | ✅ | ## Tool Categories | Category | Tools | Purpose | |----------|-------|---------| | Git Scanning | TruffleHog, GitLeaks | Secret detection in git history | | Static Analysis | Semgrep (secrets rules), grep patterns | Source code secret scanning | | Web Probing | nuclei (exposure templates), ffuf | Exposed file/config discovery | | JS Analysis | SecretFinder, LinkFinder | Client-side bundle secret extraction | | Validation | curl, custom scripts | Credential active-access testing | ## References - `references/tools.md` - Tool function signatures and parameters - `references/workflows.md` - Attack pattern definitions and test vectors
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
Use when you have a written implementation plan to execute in a separate session with review checkpoints
OpenClaw 安全检测工具,基于安全实践指南验证配置安全、权限隔离、网络策略、日志审计和运行时完整性
OpenClaw 攻击模式检测工具,识别数据外传、反弹Shell、文件泄露、Prompt注入、供应链投毒等高危行为,支持 MITRE ATT&CK 映射
Comprehensive PDF manipulation toolkit for extracting text and tables, creating new PDFs, merging/splitting documents, and handling forms. When Claude needs to fill in a PDF form or programmatically process, generate, or analyze PDF documents at scale.
AI/LLM application security testing — prompt injection, jailbreaking, data exfiltration, and insecure output handling per OWASP LLM Top 10.
Deep OWASP API Security Top 10 testing for REST, GraphQL, gRPC, and WebSocket APIs — BFLA, mass assignment, rate limiting, and unsafe consumption.