⚠️ 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:

1. Ask the user to state the exact target URL, IP, account, or resource.
2. Ask the user to confirm written authorization and the permitted scope.
3. Show the exact command(s) and explain their expected effect.
4. 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.

HUNT-NODEJS — Node.js Specific Vulnerabilities

Evidence and non-destructive test limits

Runtime headers are hints, not proof; payload acceptance/reflection does not establish prototype pollution or RCE. Confirm the actual vulnerable merge/template version and reachable gadget in a disposable lab. Prototype pollution can persist across requests or affect other tenants: use isolated test processes, harmless markers and cleanup/restart plans, never isAdmin against real users. Bound request rates and prohibit secret extraction; /proc examples require explicit credential-access scope and minimal redacted evidence. OOB callbacks require an approved collector and unique marker; a callback alone proves only the demonstrated interaction, not arbitrary execution.