Pular para o conteúdo
Novo

DeepSeek V4.1 Flash grátis por 7 dias: 10M tokens por dia após recarga de $10 ou mais. Até 30/11.

Como funciona
aeondave/source-review-techniqueWeb e 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 instalações+5 em 7 dias39 Estrelassincronizado há 10 horas

Instalar

Ainda não tem a CLI da NotHoly? Instale primeiro.

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

Grava em ⁦~/.notholy/skills⁩ depois de conferir a assinatura e o SHA-256.

AssinaturaAssinado, ed25519
bX2k/IpAWW…FKD91hDA==A CLI confere o SHA-256 e a assinatura antes de gravar qualquer arquivo.
Pacote1d861980…a5685620
1d8619802ef4…920ba56856202 arquivos · ⁦4.1 KB⁩
VarreduraMédio3 achados
  • injection.no_confirmationreferences/bug-classes.md:58
  • Nenhuma licença encontrada
  • Links para domínios externos
Ver a varredura completa
Fontegithub.com/AeonDave/malskill/tree/main/offensive-techniques/source-review-technique@21cd568

Este item ainda não foi escrito no seu idioma, então aparece em English.

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).

Arquivos desta versão

Permissões

PermissãoDeclaradaEncontrada na varredura
Lê arquivosNãoNão
Grava arquivosSimSim
Roda comandos no shellSimSim
Usa a redeSimSim
Usa conectoresNãoNão
Controla um navegadorNãoNão

Achados da varredura

Revisado em 13 de nov. de 2026

  1. MédiaPrompt injection · injection.no_confirmationreferences/bug-classes.md:58
  2. MédiaLicença · Nenhuma licença encontrada
  3. InfoLink · Links para domínios externos

Uma varredura limpa reduz o risco, mas não prova que o pacote é seguro. Leia o que você instala.

VersãoPublicada emCommitSHA-256AssinaturaMudança de permissão
v2026.11.13-21cd56813 de nov. de 202621cd5681d861980Assinada–

Pergunte tudo o que o seu escopo permite.

Crie a conta, adicione créditos e faça a primeira pergunta no chat ou no terminal.

  1. 1/3

    Crie a conta

    Individual ou empresa. Dá para virar empresa depois sem perder saldo nem chaves.

    Pessoa físicaEmpresa
  2. 2/3

    Adicione créditos

    No cartão. Você paga por token, sem assinatura.

    $5.00recarga mínima
  3. 3/3

    Pergunte

    No chat, ou instale o CLI e rode notholy login no terminal.

    $ notholy login