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 installazioni+3 in 7 giorni27 StelleMITsincronizzato 22 ore fa
Installa
Non hai ancora la CLI di NotHoly? Installala prima.
$ curl -fsSL https://notholy.com/install.sh | sh$ notholy skills install noorqureshi/recon-github-code-leaksScrive in ~/.notholy/skills dopo aver controllato la firma e lo SHA-256.
FirmaFirmato, ed25519
Pacchetto17d9afc7…ef66a350
17d9afc70c83…9b6aef66a3501 file · 1.6 KBScansioneBassonessuna segnalazione
Sorgentegithub.com/NoorQureshi/security-skills/tree/main/skills/recon/recon-github-code-leaks@ee0e0c5
Questa voce non è ancora scritta in italiano, quindi è mostrata in un'altra lingua: English.
In questa pagina
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.
File di questa versione
- SKILL.md2.9 KB
Permessi
| Permesso | Dichiarato | Trovato dalla scansione |
|---|---|---|
| Legge file | No | No |
| Scrive file | No | No |
| Esegue comandi shell | No | No |
| Usa la rete | No | No |
| Usa i connettori | No | No |
| Controlla un browser | No | No |
Segnalazioni della scansione
Rivisto il 13 nov 2026
La scansione non ha trovato nulla da segnalare in questa versione.
Una scansione pulita abbassa il rischio, ma non prova che il pacchetto sia sicuro. Leggi quello che installi.
| Versione | Pubblicata | Commit | SHA-256 | Firma | Cambio di permessi |
|---|---|---|---|---|---|
| v2026.10.14-ee0e0c5 | 13 nov 2026 | ee0e0c5 | 17d9afc7 | Firmata | – |
Altro da NoorQureshi
Tutto da questo editoreAltro in Ricognizione e OSINT
Vai alla categoria- 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
Chiedi tutto quello che il tuo perimetro consente.
Crea un account, aggiungi crediti e fai la prima domanda in chat o nel terminale.
- 1/3
Crea l'account
Privato o azienda. Puoi passare ad azienda in seguito senza perdere saldo o chiavi.
PrivatoAzienda - 2/3
Aggiungi crediti
Con carta. Paghi a token, senza abbonamento.
$5.00ricarica minima - 3/3
Chiedi
In chat, oppure installa la CLI ed esegui notholy login nel terminale.
$ notholy login