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
noorqureshi/tools-nucleiWeb e bug bounty

tools-nuclei

⁨Operate nuclei for template-based vulnerability scanning at scale — severity/tag selection, bulk targets, rate limiting, proxying, JSON output, and safe custom templates. Load when you have live hosts from recon and need known-CVE/misconfig/exposure sweeps, or when scanner hits need validation. Sign⁩

v2026.10.14-ee0e0c53 instalações+3 em 7 dias27 EstrelasMITsincronizado há 22 horas

Instalar

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

$ curl -fsSL https://notholy.com/install.sh | sh
$ notholy skills install noorqureshi/tools-nuclei

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

AssinaturaAssinado, ed25519
tp8z5T7/iI…IoQ4LfAA==A CLI confere o SHA-256 e a assinatura antes de gravar qualquer arquivo.
Pacote160e2e5f…5ea37095
160e2e5f4ced…44c05ea370951 arquivo · ⁦2.2 KB⁩
VarreduraMédio2 achados
  • Link para um IP diretoSKILL.md:47
  • Links para domínios externos
Ver a varredura completa
Fontegithub.com/NoorQureshi/security-skills/tree/main/skills/tools/tools-nuclei@ee0e0c5

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

When it applies

Recon has produced live in-scope hosts (automation-recon-pipeline) and you want fast coverage of known issues — CVEs, exposed panels, misconfigurations — before spending manual time. Also the right tool for re-checking a fixed finding across all hosts. For writing a template that codifies your own finding, load automation-nuclei-templates (that skill is the deep guide; the essentials are below).

Why it works

nuclei runs declarative YAML templates (9000+ community templates, HTTP/DNS/TCP/SSL/file protocols) against many targets in parallel with matchers on the response. You trade stealth for breadth: it's fast and consistent, and loud.

Method

  1. Install/update: apt install nuclei (Kali) or go install github.com/projectdiscovery/nuclei/v3/cmd/nuclei@latest; always nuclei -update-templates first.
  2. Scope the run — never full-template blindly:
    bash
    nuclei -u https://target.com -severity critical,high        # single host, high signal
    nuclei -u https://target.com -tags cve,exposure             # by tag
    nuclei -l urls.txt -severity critical,high -o results.txt   # bulk targets
    nuclei -u https://target.com -t http/cves/2024/             # one template dir after fingerprinting
  3. Pipe from recon (the standard pipeline): subfinder -d target.com -silent | httpx -silent | nuclei -severity critical,high -o report.txt
  4. Be a good citizen (and stay under WAF/IDS thresholds): -rate-limit 10 -bulk-size 5 to slow down; -proxy http://127.0.0.1:8080 to route through Burp for visibility; -exclude-tags dos,fuzz to skip destructive/noisy checks; -new-templates for only-recently-added templates on a re-visit.
  5. Capture machine-readable output for triage: -json -o results.json.
  6. Custom template essentials (full guide: automation-nuclei-templates): id in vendor-product-vulnerability form; info with honest severity/tags; http: block with {{BaseURL}} paths; combine matchers with condition: and and match a signal unique to the vuln (a computed reflection like 49 from {{7*7}}, a specific error string) — never a bare 200; add an extractor that pulls the proof. Validate with -validate, then against a known-vulnerable and a known-good host.

Gotchas

  • A nuclei hit is a candidate, not a finding — templates false-positive on version banners and lookalike strings. Manually reproduce every hit (reporting-triage-validation) before it goes in notes/findings; this is the #1 way automated scanning burns reporter credibility.
  • Full-template runs are loud and slow — fingerprint first (recon-techstack-fingerprinting), then run only relevant tags/dirs.
  • Rate limiting cuts both ways — too fast gets you WAF-banned (and can breach bug-bounty RoE on request rates); too slow on a big scope never finishes. Tune -rate-limit/-bulk-size to the RoE.
  • Windows naming collision — the httpx command on Windows may resolve to the Python httpx library's CLI, not ProjectDiscovery's httpx; verify with httpx -version before piping.
  • Keep templates read-only — anything that writes state or can DoS doesn't belong in a mass scan.

Verify success

Each nuclei hit either reproduces manually with a concrete impact (and gets a findings entry) or is recorded as a false positive with the reason. The scan config (severity/tags/rate) is logged so the run is reproducible.

References

ProjectDiscovery docs; nuclei-templates repo. Writing templates: automation-nuclei-templates. Pipeline context: automation-recon-pipeline.


Portions adapted from reverse-skill by zhaoxuya520, MIT License.

Arquivos desta versão

Permissões

PermissãoDeclaradaEncontrada na varredura
Lê arquivosNãoNão
Grava arquivosNãoNão
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édiaLink · Link para um IP diretoSKILL.md:47
  2. 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.10.14-ee0e0c513 de nov. de 2026ee0e0c5160e2e5fAssinada–

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