Individual skill

performing-zero-day-vulnerability-discovery

Systematic methodology for discovering novel vulnerabilities through manual code auditing, fuzzing, reverse engineering, and creative attack chaining during authorized security assessments.

internal/tools/skills/data/offensive-security/performing-zero-day-vulnerability-discovery/SKILL.md

Read pinned source

Source commit d42f381ad34843e71a42658e5c57290c713e85af

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
Yes
Repository scan complete
No
Skill scan complete
No
Observed behavior
Network or broad shell
Last checked
Nov 9, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings)
1,316
Repository last updated
Nov 8, 2026
License
Apache-2.0

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files
Read excerpt

# Performing Zero-Day & Novel Vulnerability Discovery

## When to Use

- When standard vulnerability scanners and known CVE checks return no results
- During deep-dive penetration tests where the client expects original research
- For custom-built applications with no public CVE history
- When testing proprietary software, APIs, or firmware
- During bug bounty hunting where unique/novel findings earn higher payouts
- After exhausting all known attack vectors in earlier phases

## Most Often Missed & How to Confirm

- Business-logic and authorization flaws: scanners can't see them, so they're the highest-value miss. Confirm IDOR/BOLA by replaying a request with a second valid account's token and proving you read/modify the first user's data — never infer from status codes alone.
Back to top