internal-infrastructure-reference-classification
/internal-infrastructure-reference-classification
Classify internal hostnames, addresses and service names found in public or shared files, because infrastructure detail is its own disclosure even with no credential attached. Use when the corpus contains hostnames, IP literals, service names or internal URLs
- Author
- Wsh7Ash ↗
- Repository
- leaklens ↗
- Licence
- MIT
- Last repository change
- 28.10.2026
Assessment and security
- Files in this package
- 1
- Scripts
- 0
- HTML comments
- 0
- URLs in SKILL.md
- 2
No signals detected. Repository changed on 28.10.2026, without references to retired models or APIs.
MIT, open: use and modify while retaining author attribution.
What it does and when to use it
Classify internal hostnames, addresses and service names found in public or shared files, because infrastructure detail is its own disclosure even with no credential attached. Use when the corpus contains hostnames, IP literals, service names or internal URLs
Original author description
Classify internal hostnames, addresses and service names found in public or shared files, because infrastructure detail is its own disclosure even with no credential attached. Use when the corpus contains hostnames, IP literals, service names or internal URLs
How it works
- Procedure
- Signals
- Patterns
- Pitfalls
- Done when
- References
SKILL.md preview
--- name: internal-infrastructure-reference-classification description: "Classify internal hostnames, addresses and service names found in public or shared files, because infrastructure detail is its own disclosure even with no credential attached. Use when the corpus contains hostnames, IP literals, service names or internal URLs" pack: leaklens version: 1.0.0 category: data-tool tags: [classify, infrastructure, disclosure] --- # Internal Infrastructure Reference Classification > Classify internal hostnames, addresses and service names found in public or shared files, because infrastructure detail is its own disclosure even with no credential attached **Use when:** the corpus contains hostnames, IP literals, service names or internal URLs **Avoid when:** the tree is internal-only and its readership already includes everyone who could use the detail ## Procedure 1. Extract hostnames, address literals, port numbers and service names into a counted list per file. 2. Split them into categories: public-facing, internal naming scheme, and placeholder such as localhost or example. 3. Record which files are tracked, published or mirrored outside the organization, since that decides exposure. 4. Note whether the reference includes an environment label such as staging or a region, which adds detail. 5. Check for an accompanying credential, because infrastructure detail plus a credential is one combined finding. 6. Classify by reader reach: public file outranks internal documentation, even for the same hostname. ## Signals - A public documentation file names an internal hostname and its port - An address literal appears with an environment label beside it - An internal service name appears in an example that was copied into a public repository - A credential and a host appear in the same file ## Patterns **1. Reference record** ```text host: db-replica-2.internal | port: 5432 | env label: prod | file: README.md | tracked: yes | published: yes ``` **2. Reader-reach rank** ```text published outside the org > public repo > internal doc > local file; rank by who can actually read the file ``` **3. Combined flag** ```text host plus credential in one file -> one combined finding ranked above either alone, with both components described ``` ## Pitfalls - Reporting internal hostnames as critical when only internal readers can see them - Splitting a host and credential into two findings, which understates the combination - Ignoring that a public README was copied into other repositories years ago ## Done when - Each reference finding records host, category, environment label and reader reach - Any co-located credential is recorded as a combined finding rather than a separate one ## References - [CWE-200 - Exposure of sensitive information](https://cwe.mitre.org/data/definitions/200.html) - [OWASP - Information disclosure guidance](https://owasp.org/www-project-web-security-testing-guide/)
Versions
The database has no other skills named internal-infrastructure-reference-classification.
Database snapshot: 13.11.2026 · package version 67626f78948f (SHA-256 digest of the entire package)
Downloads in the last 30 days: 0 · ranking
Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.
Similar skills
- 100privacy-guard
Prevents private infrastructure details (node hostnames, internal project names, local usernames and personal emails, absolute home paths, private and VPN IP ranges) from leaking into public repositories through commits, PRs, docs or release artifacts. Use when working in a… - 100public-export-sanitization
Sanitize internal content before it goes public (repo, blog, talk). Use when publishing, to catch leaked project ids, service-account emails, hostnames, names, and repo-escaping links. - 100git-identity-hygiene
Keep personal data out of a public repo — commit emails, real names, photo GPS metadata, document metadata, internal hostnames. Use before open-sourcing, when the user wants to stay pseudonymous, or asks "what does my repo reveal about me". - 100netflows
Network flow extractor that analyzes pcap/pcapng files to identify outbound connections with automatic DNS hostname resolution. Use when you need to enumerate network destinations, identify what hosts a device communicates with, or map IP addresses to hostnames from packet captures. - 100email-address-corpus-classification
Detect email addresses at volume and classify them by whether they are synthetic, role-based, employee or customer addresses, since only one of those is a privacy finding. Use when the corpus may contain email addresses in source, fixtures, logs or exports