anti-debugging-techniques

Map anti-debug techniques to OS-specific bypass methods for Linux and Windows.

5|2|Updated May 16, 2026
One-click install
npx skills add https://github.com/DorianGallo/hack-skills-local --skill anti-debugging-techniques-doriangallo
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: anti-debugging-techniques
Source: https://github.com/DorianGallo/hack-skills-local/tree/main/skills/anti-debugging-techniques
Command: npx skills add https://github.com/DorianGallo/hack-skills-local --skill anti-debugging-techniques-doriangallo

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) and assets (resource) components.

What problem does it solve?

This Skill helps you understand and defeat anti-debug techniques that protected binaries use to detect debuggers and prematurely exit or crash, so you can continue reverse engineering work.

Core Features & Use Cases

  • Detection playbook across Linux and Windows: Covers ptrace/TRACEME, /proc TracerPid, Windows PEB flags, NtQueryInformationProcess checks, timing-based probes, and exception/signal-based detection.
  • Bypass strategies with a systematic workflow: Matches each detection class with practical countermeasures such as LD_PRELOAD shims, ScyllaHide patches, VEH handling, TLS callback handling, and API/timing spoofing.
  • Verification and prioritization: Provides bypass ordering, reliability guidance, and decision trees to quickly locate the remaining failing check when a bypass is incomplete.

Quick Start

Ask the AI to “use the anti-debugging-techniques skill to identify which Linux/Windows checks are likely blocking my debugger and provide the first two bypass steps plus how to verify whether I missed any remaining checks.”

Frequently Asked Questions about anti-debugging-techniques

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I bypass anti-debugging checks when reversing protected binaries?

Bypass anti-debugging checks by mapping detection classes like ptrace and PEB flags to reliable countermeasures including LD_PRELOAD shims and ScyllaHide patches, then validating bypass success through expected control-flow progress.

What anti-debug techniques do Windows binaries use to detect debuggers?

Windows binaries detect debuggers using PEB flags, NtQueryInformationProcess checks, timing-based probes, and exception or VEH handler tricks to prematurely crash or exit during analysis.

How does ptrace prevent debugging on Linux and what is the bypass strategy?

Linux binaries use ptrace TRACEME and /proc TracerPid to detect attached debuggers. Bypass these anti-debugging checks using LD_PRELOAD shims to spoof responses and allow continued reversing.

Does this anti-debug bypass approach work for both CTF binaries and authorized security research?

Yes, the anti-debug bypass workflow applies to interactive reversing, CTF binaries, and bug-bounty or authorized security research across Linux and Windows platforms.

What is the best way to handle timing checks and TLS callbacks during debugging?

Handle timing checks and TLS callbacks by spoofing API timing responses and configuring VEH handling, applying countermeasures in a reliable ordered sequence to neutralize debugger detection logic.

Why does my binary still exit after applying ScyllaHide patches?

If the binary still exits after ScyllaHide patches, use the provided decision trees to locate remaining failing anti-debug checks, verify bypass ordering, and validate control-flow progress systematically.