Understand anti-reversing, obfuscation, and protection techniques encountered during software analysis. Use when analyzing protected binaries, bypassing anti-debugging for authorized analysis, or understanding software protection mechanisms.
Add this skill
npx mdskills install sickn33/anti-reversing-techniquesClear trigger conditions and authorization checks, but lacks actionable implementation steps
1---2name: anti-reversing-techniques3description: Understand anti-reversing, obfuscation, and protection techniques encountered during software analysis. Use when analyzing protected binaries, bypassing anti-debugging for authorized analysis, or understanding software protection mechanisms.4---56> **AUTHORIZED USE ONLY**: This skill contains dual-use security techniques. Before proceeding with any bypass or analysis:7> 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)8> 2. **Document scope**: Ensure your activities fall within the defined scope of your authorization9> 3. **Legal compliance**: Understand that unauthorized bypassing of software protection may violate laws (CFAA, DMCA anti-circumvention, etc.)10>11> **Legitimate use cases**: Malware analysis, authorized penetration testing, CTF competitions, academic security research, analyzing software you own/have rights to1213## Use this skill when1415- Analyzing protected binaries with explicit authorization16- Conducting malware analysis or security research in scope17- Participating in CTFs or approved training exercises18- Understanding anti-debugging or obfuscation techniques for defense1920## Do not use this skill when2122- You lack written authorization or a defined scope23- The goal is to bypass protections for piracy or misuse24- Legal or policy restrictions prohibit analysis2526## Instructions27281. Confirm written authorization, scope, and legal constraints.292. Identify protection mechanisms and choose safe analysis methods.303. Document findings and avoid modifying artifacts unnecessarily.314. Provide defensive recommendations and mitigation guidance.3233## Safety3435- Do not share bypass steps outside the authorized context.36- Preserve evidence and maintain chain-of-custody for malware cases.3738Refer to `resources/implementation-playbook.md` for detailed techniques and examples.3940## Resources4142- `resources/implementation-playbook.md` for detailed techniques and examples.43
Full transparency — inspect the skill content before installing.