osint

Skill

Open-source intelligence gathering - company repository enumeration, secret scanning, git history analysis, employee footprint, and code exposure discovery.

Files2

OSINT

Passive and semi-passive intelligence gathering focused on code repositories, developer footprints, and exposed secrets across public platforms.

Phases

1. Organization Discovery

Enumerate GitHub/GitLab/Bitbucket orgs for target company name variants
Find employee personal accounts linked to the target org
Identify archived, forked, and deleted repositories

2. Repository Analysis

Map all repos: tech stack, languages, CI/CD, dependencies
Identify internal hostnames, IPs, endpoints, environment names
Check for .env, config files, secrets in current code

3. Secret & Credential Scanning

Scan current code with gitleaks / trufflehog
Scan full git history (secrets removed in commits are still accessible)
Search with targeted dorks (see reference/repository-recon.md)

4. Code Intelligence

Extract API endpoints, auth patterns, internal service names
Review Dockerfiles, CI configs, IaC for infra details
Check dependency files for version-specific CVE candidates

Output

text

data/reconnaissance/repositories.json   # Repo inventory + findings
reports/reconnaissance_report.md        # OSINT section appended
raw/osint/                              # Raw tool outputs

Tools

trufflehog, gitleaks, gitrob, GitHub/GitLab search, gh CLI, git log

Rules

Passive discovery first (search APIs, public pages) before any cloning
Scan git history — deleted secrets are still in commit objects
Check employee personal accounts, not just org accounts
Document every discovered credential/secret immediately as a finding
All output saved to {OUTPUT_DIR}/ per CLAUDE.md directory structure

Reference

reference/repository-recon.md - Dorks, tool commands, secret patterns, workflow

osint — Kortix Marketplace | Kortix