logic-vulnerability-detector

Detect logic vulnerabilities in DeepExtractIDA binaries and verify findings.

17|3|Updated Feb 22, 2026
One-click install
npx skills add https://github.com/marcosd4h/DeepExtractRuntime --skill logic-vulnerability-detector
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: logic-vulnerability-detector
Source: https://github.com/marcosd4h/DeepExtractRuntime/tree/main/skills/logic-vulnerability-detector
Command: npx skills add https://github.com/marcosd4h/DeepExtractRuntime --skill logic-vulnerability-detector

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

Detects logic vulnerabilities in DeepExtractIDA binaries, including authentication bypasses, state-machine errors, TOCTOU/double-fetch, and related flaws that memory-safety and mitigation techniques may miss.

Core Features & Use Cases

  • Four detection modules scan for different vulnerability classes including authentication bypass, state-machine issues, TOCTOU/double-fetch, and API misuse.
  • Independent verification re-reads code and assembly to confirm or reject findings.
  • Generates prioritized reports and integrates with the broader analysis workflow for threat dossiers.

Quick Start

Run the full module scan against a module database to generate a verified logic vulnerability report.

Frequently Asked Questions about logic-vulnerability-detector

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

FAQPage Schema
How do I detect logic vulnerabilities in decompiled code that bypass hardware mitigations?

To detect logic vulnerabilities in decompiled code, this Skill applies static analysis and taint analysis to identify authentication bypasses, state-machine errors, and TOCTOU flaws that memory-safety mitigations often miss.

What types of logic flaws can a static security audit find in decompiled binaries?

A static security audit of decompiled binaries can find logic flaws including authentication bypasses, state-machine errors, TOCTOU and double-fetch issues, and API misuse across four distinct detection modules.

How do I verify logic vulnerability findings to reduce false positives in a security audit?

To verify logic vulnerability findings, the Skill uses an independent verification pipeline that re-reads the decompiled code and assembly to confirm or reject findings, scoring and ranking them for prioritized reports.

Do I need call-graph analyses to perform a taint analysis on decompiled code?

Yes, performing taint analysis on decompiled code requires call-graph analyses and decompiled-code access to accurately map data flow and quantify logic flaws within the verification pipeline.

What is the best way to prioritize logic bugs found during a binary security audit?

The best way to prioritize logic bugs is using a modular verification pipeline that scores and ranks findings, generating prioritized reports and threat dossiers for the broader analysis workflow.