Skip to content
New

DeepSeek V4.1 Flash free for 7 days: 10M tokens a day after a top-up of $10 or more. Until Nov 30.

How it works
noorqureshi/recon-github-code-leaksRecon and 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 installs+3 in 7 days27 StarsMITsynced 22 hours ago

Install

No NotHoly CLI yet? Install it first.

$ curl -fsSL https://notholy.com/install.sh | sh
$ notholy skills install noorqureshi/recon-github-code-leaks

Writes to ⁦~/.notholy/skills⁩ after checking the signature and the SHA-256.

SignatureSigned, ed25519
+TSc1Pmmuh…mgcfc+AA==The CLI checks the SHA-256 and the signature before it writes a file.
Package17d9afc7…ef66a350
17d9afc70c83…9b6aef66a3501 file · ⁦1.6 KB⁩
ScanLowno findings
The scan found nothing to flag in this version.See the full scan
Sourcegithub.com/NoorQureshi/security-skills/tree/main/skills/recon/recon-github-code-leaks@ee0e0c5

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.

Files in this version

Permissions

PermissionDeclaredFound by the scan
Reads filesNoNo
Writes filesNoNo
Runs shell commandsNoNo
Uses the networkNoNo
Uses connectorsNoNo
Drives a browserNoNo

Scan findings

Reviewed on Nov 13, 2026

The scan found nothing to flag in this version.

A clean scan lowers the risk but does not prove a package is safe. Read what you install.

VersionPublishedCommitSHA-256SignaturePermission change
v2026.10.14-ee0e0c5Nov 13, 2026ee0e0c517d9afc7Signed–

Ask anything your scope allows.

Create an account, add credits and ask the first question in the chat or the terminal.

  1. 1/3

    Create the account

    Individual or company. You can switch to a company later without losing balance or keys.

    IndividualCompany
  2. 2/3

    Add credits

    By card. Pay per token, no subscription.

    $5.00minimum deposit
  3. 3/3

    Ask

    In the chat, or install the CLI and run notholy login in your terminal.

    $ notholy login