hunt-file-upload
⚠️ AUTHORIZED USE ONLY This skill is for educational purposes or authorized security assessments only. You must have explicit, written permission from the system owner before using this tool. Misuse of this tool is illegal and strictly prohibited.
Mandatory confirmation gate Before running any command that probes, exploits, changes, persists on, extracts data from, or attempts credential access against a target:
- Ask the user to state the exact target URL, IP, account, or resource.
- Ask the user to confirm written authorization and the permitted scope.
- Show the exact command(s) and explain their expected effect.
- Wait for explicit confirmation in the current conversation.
Without that confirmation, remain read-only and provide defensive guidance only. Prefer a sandbox, disposable VM, or controlled lab.
9. FILE UPLOAD
Use disposable test accounts and owner-controlled canaries only. Replace metadata/credential endpoints, sensitive local files, shell uploads and exfiltration callbacks below with harmless lab markers; do not retrieve real credentials or overwrite application/system files to prove impact. Successful network fetch, HTML script execution and upload acceptance are separate observations, not automatic RCE. Parser/version/security-policy behavior varies. Validate full decoded formats, generate storage names, reject traversal/symlinks and isolate uploaded content; extension or magic-byte checks alone are insufficient.