65 lines
3.2 KiB
Markdown
65 lines
3.2 KiB
Markdown
---
|
|
name: anti-reversing-techniques
|
|
description: "AUTHORIZED USE ONLY: This skill contains dual-use security techniques. Before proceeding with any bypass or analysis: > 1."
|
|
risk: offensive
|
|
source: community
|
|
date_added: "2026-02-27"
|
|
---
|
|
|
|
> **⚠️ 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.
|
|
|
|
> **AUTHORIZED USE ONLY**: This skill contains dual-use security techniques. Before proceeding with any bypass or analysis:
|
|
> 1. **Verify authorization**: Confirm you have explicit written permission from the software owner, or are operating within a legitimate security context (CTF, authorized pentest, malware analysis, security research)
|
|
> 2. **Document scope**: Ensure your activities fall within the defined scope of your authorization
|
|
> 3. **Legal compliance**: Understand that unauthorized bypassing of software protection may violate laws (CFAA, DMCA anti-circumvention, etc.)
|
|
>
|
|
> **Legitimate use cases**: Malware analysis, authorized penetration testing, CTF competitions, academic security research, analyzing software you own/have rights to
|
|
|
|
## Use this skill when
|
|
|
|
- Analyzing protected binaries with explicit authorization
|
|
- Conducting malware analysis or security research in scope
|
|
- Participating in CTFs or approved training exercises
|
|
- Understanding anti-debugging or obfuscation techniques for defense
|
|
|
|
## Do not use this skill when
|
|
|
|
- You lack written authorization or a defined scope
|
|
- The goal is to bypass protections for piracy or misuse
|
|
- Legal or policy restrictions prohibit analysis
|
|
|
|
## Instructions
|
|
|
|
1. Confirm written authorization, scope, and legal constraints.
|
|
2. Identify protection mechanisms and choose safe analysis methods.
|
|
3. Document findings and avoid modifying artifacts unnecessarily.
|
|
4. Provide defensive recommendations and mitigation guidance.
|
|
|
|
## Safety
|
|
|
|
- Do not share bypass steps outside the authorized context.
|
|
- Preserve evidence and maintain chain-of-custody for malware cases.
|
|
|
|
Refer to `resources/implementation-playbook.md` for detailed techniques and examples.
|
|
|
|
## Resources
|
|
|
|
- `resources/implementation-playbook.md` for detailed techniques and examples.
|
|
|
|
## Limitations
|
|
- Use this skill only when the task clearly matches the scope described above.
|
|
- Do not treat the output as a substitute for environment-specific validation, testing, or expert review.
|
|
- Stop and ask for clarification if required inputs, permissions, safety boundaries, or success criteria are missing.
|