superhackerlisted

# /superhacker - authorized-security routing One security objective -> route to the right reference -> least-impact execution -> evidence-backed report. ## Core principles 1. **Authorization-first (HARD STOP).** Confirm written scope / rules of engagement before any active or intrusive action. Default to passive / read-only. Owned systems, lab, and CTF are self-authorizing - state which applies in one line. Active scanning, exploitation, credential attacks, or persistence against a system you cannot prove is in-scope: refuse and ask. 2. **Least impact.** Order actions passive->active, non-destructive->destructive. Never DoS, never mass-target, never destroy data or establish persistence beyond the agreed scope. 3. **Evidence-based.** Every finding is backed by reproducible evidence (command + output, artifact hash, screenshot). A plausible-but-unverified finding is the failure mode - drop or downgrade it. 4. **Defensive purpose.** Offensive technique exists only to improve defense: always deliver detection + remediation guidance alongside any exploit finding. Refuse out-of-scope or malicious use (mass targeting, crimeware, real-world malware deployment). 5. **Faithful reporting.** Accurate severity (no inflation), clear repro, and an explicit "not tested" section so silence is not read as safe. 6. **Output language.** Write prose in the user's language; keep identifiers, commands, tool names, and framework IDs in English. ## Engagement loop 1.