mitm-find-secrets
Find leaked secrets, API keys, and credentials in traffic. Use when user asks about exposed keys, hardcoded secrets, or credential leakage.
소스 정보
- 저장소
- instavm/security-skills
- 최근 소스 활동
- 2026년 3월 23일 05:24
- 감지된 SKILL.md 언어
- 영어
- 스타
- 86
- 포크
- 11
설치 방법
기본적으로 소스를 먼저 확인하는 Prompt가 선택됩니다. 직접 명령으로 전환하거나 로컬 사본을 다운로드할 수도 있습니다.
소스 파일 검토
설치 여부를 결정하기 전에 SKILL.md와 SkillsMP에 표시된 보조 파일을 읽어 보세요.
SKILL.md 표시 중
SKILL.md
소스 지침 · 읽기 전용 미리보기- name
- mitm-find-secrets
- description
- Find leaked secrets, API keys, and credentials in traffic. Use when user asks about exposed keys, hardcoded secrets, or credential leakage.
# Find Leaked Secrets
Analyze the mitmproxy dump (log.txt) for exposed secrets for: $ARGUMENTS
> **Requires**: `log.txt` in the current directory. If it's missing, capture traffic first:
> ```bash
> mitmdump --set flow_detail=3 2>&1 | tee log.txt
> ```
## Secret Types to Find
### 1. API Keys & Tokens
- `api_key`, `apiKey`, `access_key`
- `secret_key`, `secretKey`, `client_secret`
- `token`, `auth_token`, `bearer`
- Patterns: Long alphanumeric strings (32+ chars)
### 2. Cloud Credentials
- AWS: `AKIA...` (access key ID)
- GCP: `AIza...` (API key)
- Azure: Connection strings
- Firebase: Config objects
### 3. Payment Secrets
- Merchant salts
- HMAC keys
- Encryption keys
- PCI-sensitive data
### 4. Third-Party Services
- SMS gateway credentials
- Email service keys
- Analytics tokens
- CDN secrets
### 5. Internal Secrets
- Database credentials
- Internal API keys
- JWT secrets
- Encryption salts
## Common Leak Locations
- JavaScript files
- Mobile app API calls
- Error responses with stack traces
- Debug endpoints
- Configuration endpoints
## Output Format
For each finding:
- **Secret Type**: Category of secret
- **Location**: Where found (endpoint/file)
- **Value**: Partially masked secret
- **Service**: What it's used for
- **Risk**: Potential impact
- **Verification**: How to test if active
GitHub에서 보기