aa71e76eb9
- Add date_added to all 950+ skills for complete tracking - Update version to 6.5.0 in package.json and README - Regenerate all indexes and catalog - Sync all generated files Features from merged PR #150: - Stars/Upvotes system for community-driven discovery - Auto-update mechanism via START_APP.bat - Interactive Prompt Builder - Date tracking badges - Smart auto-categorization All skills validated and indexed. Made-with: Cursor
46 lines
2.1 KiB
Markdown
46 lines
2.1 KiB
Markdown
---
|
|
name: anti-reversing-techniques
|
|
description: "Understand anti-reversing, obfuscation, and protection techniques encountered during software analysis. Use when analyzing protected binaries, bypassing anti-debugging for authorized analysis, or u..."
|
|
risk: unknown
|
|
source: community
|
|
date_added: "2026-02-27"
|
|
---
|
|
|
|
> **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.
|