Skip to content
Back to skills

Fingerprinting Binaries

ASecurity

Identifies binary file characteristics including compiler signatures, version information, and build environment details. Use when analyzing unknown binaries, investigating binary origins, or identifying build configurations.

  • 666 stars
  • 0 votes
  • 0 copies
  • 2 views
  • Added February 8, 2026
developmentapisecurity

Works with

  • api

Security analysis

A100/100

Scanned February 12, 2026

npx -y skills add majiayu000/claude-skill-registry --skill fingerprinting-binaries --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Fingerprinting Binaries?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Fingerprinting Binaries
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/majiayu000-fingerprinting-binaries/badge)](https://www.skillsdirectory.com/skills/majiayu000-fingerprinting-binaries)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: fingerprinting-binaries
description: Identifies binary file characteristics including compiler signatures, version information, and build environment details. Use when analyzing unknown binaries, investigating binary origins, or identifying build configurations.
---

# Binary Fingerprinting

## Detection Workflow

1. **Extract strings**: Use `strings` to get all strings, identify version strings, find compiler-related strings, extract build information
2. **Analyze imports**: Identify imported functions, check library dependencies, assess API usage patterns, identify OS/version
3. **Examine code structure**: Analyze function prologues/epilogues, check for stack canaries, identify security features, assess code patterns
4. **Assess binary characteristics**: Determine architecture, identify compiler, estimate build date, classify binary type

## Key Patterns

- Compiler signatures: GCC/Clang/MSVC artifacts, compiler version indicators, optimization level signatures, standard library versions
- Build information: build timestamps, source file paths, debug symbols, build configuration strings
- Library signatures: static library linking, library version indicators, custom library usage, third-party dependencies
- Architecture features: CPU architecture (x86, ARM, MIPS), instruction set extensions (SSE, AVX, NEON), endianness (little/big), ABI

## Output Format

Report with: id, type, subtype, severity, confidence, binary_info (architecture, endianness, file_type, entry_point), compiler_info (compiler, version, optimization, confidence), build_info (build_date, build_host, source_paths), libraries, security_features, recommendations.

## Severity Guidelines

- **INFO**: Informational only, no security impact
- **LOW**: Outdated compiler or libraries with known issues
- **MEDIUM**: Missing security features

## See Also

- `patterns.md` - Detailed detection patterns and exploitation scenarios
- `examples.md` - Example analysis cases and code samples
- `references.md` - CWE references and mitigation strategies

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…

Newsletter

Get the weekly list of safe new skills, and the ones we pulled.