AUTHORIZED USE ONLY: This skill contains dual-use security techniques. Before proceeding with any bypass or analysis:
- •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)
- •Document scope: Ensure your activities fall within the defined scope of your authorization
- •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
- •Confirm written authorization, scope, and legal constraints.
- •Identify protection mechanisms and choose safe analysis methods.
- •Document findings and avoid modifying artifacts unnecessarily.
- •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.mdfor detailed techniques and examples.