Anti-Debugging-Erkennungs- und Umgehungs-Playbook. Verwenden Sie es beim Reversen von geschützten Binaries, die Debugger über ptrace, PEB-Flags, Zeitprüfungen oder Signal-/Ausnahmehandler auf Linux und Windows erkennen.
Dieses Skill-Paket (yaklang/anti-debugging-techniques) ist ein umfassendes Playbook für Entwickler und Sicherheitsforscher, die es mit geschützten Binaries zu tun haben, die Anti-Debugging-Maßnahmen implementieren. Es bietet eine Sammlung von Erkennungs- und Umgehungstechniken für Linux und Windows, einschließlich der Arbeit mit ptrace, PEB (Process Environment Block)-Flags, Timing-basierten Überprüfungen sowie Signal- und Ausnahmehandlern. Der Skill ermöglicht es Agenten wie Claude Code oder Cursor, während des Reverse Engineerings automatisch die relevantesten Methoden vorzuschlagen – basierend auf der Art der Debugger-Erkennung. Entwickler können diese Techniken nutzen, um den Debugger vor dem Zielprozess zu verstecken, Zeitfallen zu entschärfen oder seltsame Verhaltensweisen durch benutzerdefinierte Handler zu umgehen. Unterstützt werden primär Linux (ptrace,/proc/self/status) und Windows (PEB, NtQueryInformationProcess, TLS-Callbacks). Das Playbook ist als praktische Referenz strukturiert und kann direkt in Codex, Cursor oder ähnliche KI-Tools integriert werden, um den Analyse-Workflow zu beschleunigen.
npx skills add https://github.com/yaklang/hack-skills/tree/main/skills/anti-debugging-techniquesInstalled? Explore more Codierung & Entwicklung skills: steipete/bluebubbles, steipete/eightctl, steipete/blucli · View all 6 →
Anti-Debugging-Erkennungs- und Umgehungs-Playbook. Verwenden Sie es beim Reversen von geschützten Binaries, die Debugger über ptrace, PEB-Flags, Zeitprüfungen oder Signal-/Ausnahmehandler auf Linux und Windows erkennen.
This repo contains 20 individual skills — each has its own dedicated page.
401/403 bypass playbook. Use when encountering access-denied responses on admin panels, API endpoints, or restricted paths. Covers path manipulation, HTTP method tampering, header injection, protocol downgrade, and automated bypass tools.
Active Directory ACL abuse playbook. Use when exploiting misconfigured AD permissions including GenericAll, WriteDACL, DCSync rights, shadow credentials, LAPS reading, GPO abuse, and BloodHound-guided attack paths.
AD Certificate Services attack playbook. Use when targeting misconfigured AD CS for privilege escalation via ESC1-ESC13 template abuse, NTLM relay to enrollment, CA officer abuse, and certificate-based persistence.
Kerberos attack playbook for Active Directory. Use when targeting AD authentication via AS-REP roasting, Kerberoasting, golden/silver/diamond tickets, delegation abuse, or pass-the-ticket attacks.
AI/ML security playbook. Use when assessing model supply chain attacks (pickle RCE, poisoned weights), adversarial examples, model poisoning, model stealing, data privacy attacks (membership inference, model inversion), and autonomous agent security risks.
Android pentesting playbook. Use when testing Android applications for SSL pinning bypass, exported component abuse, WebView vulnerabilities, intent redirection, root detection bypass, tapjacking, and backup extraction during authorized mobile security assessments.
API authentication and JWT abuse playbook. Use when testing bearer tokens, API keys, claim trust, header spoofing, rate limits, and API auth boundary weaknesses.
API authorization and BOLA testing playbook. Use when APIs expose object identifiers, nested resources, hidden writable fields, or weak function-level authorization.
API reconnaissance and documentation review playbook. Use when discovering endpoints, schemas, versions, OpenAPI specs, hidden docs, and surface area for API testing.
Entry P1 category router for API security. Use when choosing between API recon, authorization, token abuse, and hidden-parameter workflows before any deeper API topic skill.
Arbitrary write to RCE playbook. Use when you have an arbitrary write primitive (from heap exploitation, format string, or OOB write) and need to convert it into code execution by targeting GOT, hooks, _IO_FILE vtable, exit_funcs, TLS_dtor_list, modprobe_path, .fini_array, or C++ vtables.
Authentication bypass testing playbook. Use when assessing login flows, password reset logic, account recovery, MFA bypass, token predictability, brute-force resistance, and session boundary flaws.
Entry P1 category router for authentication and authorization. Use when testing login flows, sessions, object authorization, JWT, OAuth, CORS, CSRF, and enterprise SSO weaknesses before any deeper auth topic skill.
Binary protection bypass playbook. Use when identifying and bypassing ASLR, PIE, NX/DEP, stack canary, RELRO, FORTIFY_SOURCE, CET, and MTE protections in ELF binaries to enable exploitation.
Browser and V8 exploitation playbook. Use when exploiting JavaScript engine vulnerabilities including JIT type confusion, incorrect bounds elimination, and V8 sandbox bypass to achieve renderer RCE and sandbox escape in Chrome/Chromium.
Entry P1 category router for business logic testing. Use when workflow abuse, race conditions, pricing flaws, or multi-step state attacks matter more than parser-level input injection.
Business logic vulnerability playbook. Use when reasoning about workflows, race conditions, price manipulation, coupon abuse, state machines, and multi-step authorization gaps.
Classical cipher analysis playbook. Use when encountering substitution ciphers, Vigenere, transposition, XOR, or encoded text in CTF challenges that requires frequency analysis, Kasiski examination, or known-plaintext cryptanalysis.
Clickjacking playbook. Use when testing whether target pages can be framed, whether X-Frame-Options or CSP frame-ancestors are properly configured, and whether UI redress attacks can trigger sensitive actions.
Command injection playbook. Use when user input may reach shell commands, process execution, converters, import pipelines, or blind out-of-band command sinks.
Send and manage iMessages via BlueBubbles, including attachments, tapbacks, edits, replies, and groups.
Control Eight Sleep pods (status, temperature, alarms, schedules).
BluOS CLI (blu) for discovery, playback, grouping, and volume.
Create, search, and manage Bear notes via grizzly CLI.
Capture frames or clips from RTSP/ONVIF cameras.
Search GIF providers with CLI/TUI, download results, and extract stills/sheets.