error-log-mining

1# Error Log Mining Skill
2 
3Discover and analyze exposed PHP `error_log` files for server paths, database
4errors, SQL fragments, API-key candidates, email addresses, and internal
5addresses. Collect a bounded sample and validate the sensitivity of its content
6instead of inferring impact from file size or status.
7 
8## When to Use
9 
10- Running `deep-invade` Phase 2 on a high-value target.
11- `skill_view(name='source-leak-hunt')` found an `error_log` file with HTTP 200.
12- Target has PHP (WordPress, Laravel, custom PHP) with `display_errors` possibly enabled.
13- You need server-side context (paths, DB structure) before attempting exploitation.
14 
15## Prerequisites
16 
17- `terminal` with curl, grep, and python3.
18- Target URL with potential error_log at common paths.
19- Disk space: error logs can be multi-GB. Use `curl -r` for range requests on large files.
20 
21## How to Run
22 
23```bash
24TARGET="https://example.com"
25 
26# Paths to probe
27for path in "error_log" "wp-content/debug.log" "debug.log" "errors.log" \
28  "php_errors.log" "wp-content/error.log" "logs/error.log"; do
29  code=$(curl -sk -o /dev/null -w "%{http_code}" --max-time 5 --connect-timeout 5 "$TARGET/$path")
30  [[ "$code" == "200" ]] && echo "FOUND: $TARGET/$path"
31done
32 
33# Download and analyze
34curl --max-time 30 --connect-timeout 10 -sk "$TARGET/error_log" -o error_log.txt
35python3 analyze_log.py error_log.txt
36```
37 
38## Quick Reference
39 
40| Extraction Target | Python regex | Value |
41|------------------|--------------------------------------|-------|
42…