Individual skill

git-history-secret-mining

Class-level playbook for mining secrets from git history on self-hosted forges (Gitea/Gogs/GitLab) during authorized assessments — anonymous repo browsing enumeration, deleted-file recovery via deletion-commit parents, raw-blob URLs with `^` parent syntax, live read-only validation of leaked static keys, and the "removed later != fixed" remediation trap. Use when a target runs its own git server or when leaked credentials need impact proof.

skills/security/git-history-secret-mining/SKILL.md

Read pinned source

Source commit 961a0dd3d2d2f66a07a416ade3b1d4473b64802e

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
No
Repository scan complete
No
Skill scan complete
No
Observed behavior
Not checked yet
Last checked
Nov 4, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings)
1,011
Repository last updated
Nov 5, 2026
License
Apache-2.0

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files
Read excerpt

# GIT-HISTORY SECRET MINING — Self-Hosted Forges (Gitea/Gogs/GitLab)

A self-hosted git forge at an obscure subdomain (`guthib.<target>`, `git.<target>`,
`code.<target>`) with **anonymous repo browsing** is a full source + full history
disclosure without any webserver misconfiguration. In one authorized engagement this
single surface yielded both CRITICAL findings: a `.env` with a production API secret key,
and a 678-account SQL user dump. No `.git/` directory exposure needed.

> Authorization note: use only in scoped engagements. Treat recovered dumps as sensitive;
> verify claims from git objects yourself, never from scanner/subagent summaries alone.

## Phase A — Enumerate the Forge

1. Fingerprint: Gitea serves `<meta name="author" content="Gitea">` and a custom tagline;