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/recon-github-code-leaksReconhecimento e OSINT

recon-github-code-leaks

⁨Find secrets and internal detail an organisation leaked to public code — GitHub/GitLab repos, gists, and commit history. Load during recon of a named org, on "github dorks", "leaked secrets", "find API keys", or when employees/repos are in scope. Signals: a company GitHub org, developer usernames, a⁩

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/recon-github-code-leaks

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

AssinaturaAssinado, ed25519
+TSc1Pmmuh…mgcfc+AA==A CLI confere o SHA-256 e a assinatura antes de gravar qualquer arquivo.
Pacote17d9afc7…ef66a350
17d9afc70c83…9b6aef66a3501 arquivo · ⁦1.6 KB⁩
VarreduraBaixonenhum achado
A varredura não encontrou nada para apontar nesta versão.Ver a varredura completa
Fontegithub.com/NoorQureshi/security-skills/tree/main/skills/recon/recon-github-code-leaks@ee0e0c5

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

When it applies

Recon of an organisation whose developers publish code. Public repos, gists, and — crucially — old commits routinely leak API keys, cloud credentials, internal hostnames, and endpoints that open a foothold no scanner of the live app would find.

Why it works

Secrets get committed and then "removed" in a later commit — but git keeps history, so the secret is still reachable. Developers also mirror internal tooling, config, and infrastructure names into public repos, handing you the attack surface and sometimes the keys to it.

Method

  1. Map the footprint: the org's repos, its members' personal repos, and gists (org members often leak in personal projects). Note internal domains/usernames to grep for.
  2. Dork the code search: combine an org/domain term with secret indicators — "company.com" password, api_key, AKIA, BEGIN RSA PRIVATE KEY, .env, config, authorization: bearer, s3.amazonaws.com company. Search filenames too (filename:.env, filename:credentials).
  3. Scan history, not just HEAD: clone and run trufflehog/gitleaks over the full history (trufflehog git file://.), which finds secrets in deleted/old commits and validates live ones.
  4. Pivot on findings: internal endpoints/hosts → new recon targets; cloud keys → verify scope and authorization before use (cloud-*); JS/config → app internals.
  5. Handle responsibly: prove validity minimally (e.g. sts get-caller-identity for AWS if in scope), never exfiltrate data, and report leaked secrets for rotation.

Gotchas

  • Stay in scope: employees' personal repos and unrelated orgs may be out of scope — confirm before touching, and never use a live credential you aren't authorized to use.
  • Many hits are dead/rotated keys — validate before reporting, but report even revoked ones as a process finding when the program wants it.
  • GitHub code search rate-limits and truncates — combine the web UI, the API, and offline history scans.

Verify success

You have leaked material tied to the target — a valid credential (verified minimally and in scope), an internal endpoint/host, or config — that advances the engagement or is a reportable exposure.

References

truffleHog & gitleaks; GitHub code-search dork lists; the classic AWS-key-in-git incident write-ups.

Arquivos desta versão

Permissões

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

Achados da varredura

Revisado em 13 de nov. de 2026

A varredura não encontrou nada para apontar nesta versão.

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 2026ee0e0c517d9afc7Assinada–

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