Skip to content
New

DeepSeek V4.1 Flash free for 7 days: 10M tokens a day after a top-up of $10 or more. Until Nov 30.

How it works
aeondave/source-review-techniqueWeb and bug bounty

source-review-technique

⁨Hybrid AI/Deterministic SAST methodology for discovering zero-day vulnerabilities in source code. Orchestrates structural search with AI-driven data flow and sink validation.⁩

v2026.11.13-21cd5685 installs+5 in 7 days39 Starssynced 10 hours ago

Install

No NotHoly CLI yet? Install it first.

$ curl -fsSL https://notholy.com/install.sh | sh
$ notholy skills install aeondave/source-review-technique

Writes to ⁦~/.notholy/skills⁩ after checking the signature and the SHA-256.

SignatureSigned, ed25519
bX2k/IpAWW…FKD91hDA==The CLI checks the SHA-256 and the signature before it writes a file.
Package1d861980…a5685620
1d8619802ef4…920ba56856202 files · ⁦4.1 KB⁩
ScanMedium3 findings
  • injection.no_confirmationreferences/bug-classes.md:58
  • No license found
  • Links to outside domains
See the full scan
Sourcegithub.com/AeonDave/malskill/tree/main/offensive-techniques/source-review-technique@21cd568

Goal: Discover zero-day vulnerabilities in source code by combining deterministic structural search with LLM-assisted data flow analysis.

When this technique applies

  • A target's source code is available (open source, leaked, or decompiled/decompressed).
  • You need to track tainted inputs to sensitive sinks (SAST).
  • Pure regex/search is too noisy, but full manual review is too slow.

The Hybrid Workflow

Modern SAST effectively bridges static tools with LLMs. The LLM acts as the triage and data-flow validator, while tools like semgrep or grep map the initial graph.

1. Sink and Source Mapping (Deterministic)

Do not ask the LLM to "find bugs" across thousands of lines at once. It will hallucinate.

  1. Identify Sources: HTTP requests, CLI args, file reads, database returns, IPC.
  2. Identify Sinks: exec, system, query, eval, deserialize, UnsafeCell, memory allocators.
  3. Map: Use ripgrep/semgrep/opengrep (or the IDE's code-usage search when available) to enumerate every invocation of the sinks.

2. Taint Evaluation (LLM-Assisted)

For each high-value sink found:

  1. Traverse backward to find where the arguments originated.
  2. Verify if the arguments are controllable by an attacker (the Source).
  3. If the path crosses file boundaries (inter-procedural), explicitly read those files.
  4. Context enrichment: Search locally for validators, sanitizers, or middleware.

3. Verification & Evidence

  • Do not report a vulnerability unless you can trace a continuous line from Source to Sink.
  • Document the exact file, line number, and variables involved at each step.
  • Identify what conditions must be bypassed to reach the sink.

Quality Gates

  • No generic bug reports: If the finding is "Xss vulnerability because print is used", reject it unless you can prove the input is strictly user-controlled and unescaped.
  • Dependency boundaries: If the sink is in a third-party framework, check how the target application actually invokes that framework instance.
  • Evidence format: Produce a markdown file detailing the exact Attack Path, required preconditions, and the affected code snippet blocks.

References

  • references/bug-classes.md — Targeted sink patterns for common architectures (e.g. Deserialization, Path Traversal, Memory Corruption).

Files in this version

Permissions

PermissionDeclaredFound by the scan
Reads filesNoNo
Writes filesYesYes
Runs shell commandsYesYes
Uses the networkYesYes
Uses connectorsNoNo
Drives a browserNoNo

Scan findings

Reviewed on Nov 13, 2026

  1. MediumPrompt injection · injection.no_confirmationreferences/bug-classes.md:58
  2. MediumLicense · No license found
  3. InfoLink · Links to outside domains

A clean scan lowers the risk but does not prove a package is safe. Read what you install.

VersionPublishedCommitSHA-256SignaturePermission change
v2026.11.13-21cd568Nov 13, 202621cd5681d861980Signed–

Ask anything your scope allows.

Create an account, add credits and ask the first question in the chat or the terminal.

  1. 1/3

    Create the account

    Individual or company. You can switch to a company later without losing balance or keys.

    IndividualCompany
  2. 2/3

    Add credits

    By card. Pay per token, no subscription.

    $5.00minimum deposit
  3. 3/3

    Ask

    In the chat, or install the CLI and run notholy login in your terminal.

    $ notholy login