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 instalaciones+3 en 7 días27 EstrellasMITsincronizado hace 22 horas
Instalar
¿Aún no tienes la CLI de NotHoly? Instálala primero.
$ curl -fsSL https://notholy.com/install.sh | sh$ notholy skills install noorqureshi/recon-github-code-leaksEscribe en ~/.notholy/skills después de comprobar la firma y el SHA-256.
FirmaFirmado, ed25519
Paquete17d9afc7…ef66a350
17d9afc70c83…9b6aef66a3501 archivo · 1.6 KBEscaneoBajosin hallazgos
Fuentegithub.com/NoorQureshi/security-skills/tree/main/skills/recon/recon-github-code-leaks@ee0e0c5
Esta entrada todavía no está escrita en tu idioma, así que aparece en English.
En esta página
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
- 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.
- 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). - Scan history, not just HEAD: clone and run
trufflehog/gitleaksover the full history (trufflehog git file://.), which finds secrets in deleted/old commits and validates live ones. - Pivot on findings: internal endpoints/hosts → new recon targets; cloud keys → verify scope and
authorization before use (
cloud-*); JS/config → app internals. - Handle responsibly: prove validity minimally (e.g.
sts get-caller-identityfor 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.
Archivos de esta versión
- SKILL.md2.9 KB
Permisos
| Permiso | Declarado | Hallado en el escaneo |
|---|---|---|
| Lee archivos | No | No |
| Escribe archivos | No | No |
| Ejecuta comandos de shell | No | No |
| Usa la red | No | No |
| Usa conectores | No | No |
| Controla un navegador | No | No |
Hallazgos del escaneo
Revisado el 13 nov 2026
El escaneo no encontró nada que señalar en esta versión.
Un escaneo limpio baja el riesgo, pero no prueba que el paquete sea seguro. Lee lo que instalas.
| Versión | Publicada | Commit | SHA-256 | Firma | Cambio de permisos |
|---|---|---|---|---|---|
| v2026.10.14-ee0e0c5 | 13 nov 2026 | ee0e0c5 | 17d9afc7 | Firmada | – |
Más de NoorQureshi
Todo de este publicadorMás en Reconocimiento y OSINT
Ver la categoría- gobusteraeondave/gobuster4
- ghuntaeondave/ghunt4
- stride-threat-modelingsecurityskills/stride-threat-modeling3
- attack-surface-reconsecurityskills/attack-surface-recon3
- bug-bounty-recon-pipelinesecurityskills/bug-bounty-recon-pipeline3
- implementing-attack-surface-managementmukul975/implementing-attack-surface-management3
Pregunta todo lo que tu alcance permite.
Crea la cuenta, añade créditos y haz la primera pregunta en el chat o en la terminal.
- 1/3
Crea la cuenta
Individual o empresa. Puedes pasar a empresa después sin perder saldo ni claves.
IndividualEmpresa - 2/3
Añade créditos
Con tarjeta. Pagas por token, sin suscripción.
$5.00recarga mínima - 3/3
Pregunta
En el chat, o instala el CLI y ejecuta notholy login en tu terminal.
$ notholy login