zero-day

Identify novel security flaws in source code, binaries, and live services.

2|Updated Apr 6, 2026
One-click install
npx skills add https://github.com/iuliandita/skills --skill zero-day
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: zero-day
Source: https://github.com/iuliandita/skills/tree/main/skills/zero-day
Command: npx skills add https://github.com/iuliandita/skills --skill zero-day

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill provides a rigorous, repeatable methodology for identifying previously unknown security vulnerabilities in source code, binaries, and live systems, moving beyond simple automated scanning.

Core Features & Use Cases

  • Vulnerability Research: Guides the entire research lifecycle from intelligence gathering and attack surface mapping to proof-of-concept development.
  • Variant Analysis: Enables researchers to find similar bugs in related codebases after a CVE is published.
  • Use Case: Use this Skill to perform deep manual analysis on a high-priority parser component to discover memory corruption flaws that standard security scanners miss.

Quick Start

Invoke the zero-day skill to begin profiling the attack surface of the target repository and identifying high-priority vulnerability classes for deep analysis.

Frequently Asked Questions about zero-day

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

FAQPage Schema
How do I find novel vulnerabilities in compiled binaries that automated scanners miss?

To find novel vulnerabilities in compiled binaries, conduct systematic vulnerability research using manual attack surface mapping, taint tracking, and patch diffing. This approach identifies deep memory corruption flaws that standard automated scanning tools often overlook.

What is variant analysis and when do I need it for vulnerability research?

Variant analysis is the process of finding similar bugs in related codebases after a CVE is published. You need it during vulnerability research to systematically check whether newly disclosed flaws exist in other target repositories or components.

How do I conduct patch diffing to identify security flaws in source code?

Conduct patch diffing by analyzing changes between patched and unpatched source code to identify security flaws. This systematic vulnerability research method traces taint data through modified attack surfaces to locate novel memory corruption vulnerabilities.

Can I use this methodology to develop proof-of-concept exploits for responsible disclosure?

Yes, you can develop proof-of-concept exploits for responsible disclosure. The systematic vulnerability research lifecycle guides you from intelligence gathering and attack surface profiling through to PoC development while adhering to strict authorization and safety protocols.

Does vulnerability research on live services require specific authorization protocols?

Yes, vulnerability research on live services requires strict authorization and safety protocols. Deep manual analysis of live systems demands explicit permission and adherence to responsible disclosure guidelines to ensure legal and ethical testing.

What is the best way to profile an attack surface for deep manual analysis?

The best way to profile an attack surface is to systematically map the target repository to identify high-priority vulnerability classes. This preparatory step focuses deep manual analysis on critical components most likely to yield novel security flaws.