ctf-forensics
Provides digital forensics and signal analysis techniques for CTF challenges. Use when analyzing disk images, memory dumps, event logs, network captures, cryptocurrency transactions, steganography, PDF analysis, Windows registry, Volatility, PCAP, Docker images, coredumps, side-channel power traces, DTMF audio spectrograms, packet timing analysis, CD audio disc images, or recovering deleted files and credentials.
67
82%
Does it follow best practices?
Run evals on this skill
Adds up to 20 points to the overall score
View guide
Critical
Do not install without reviewing
Security
3 findings: 2 critical severity, 1 high severity. Installing this skill is not recommended: please review these findings carefully if you do intend to do so.
E005: Suspicious download URL detected in skill instructions.
What this means
Detected a suspicious URL in the skill instructions that could lead the agent to download and execute malicious scripts or binaries. This includes links to executables from untrusted sources, typosquatting of official packages, URL shorteners that obscure the destination, and personal file hosting services.
Why it was flagged
Multiple URLs point to personal or low‑reputation GitHub repositories (unvetted code) and to exposed/hosted targets (.git and target:8080) that are common vectors for distributing untrusted binaries or tooling, so they are higher risk than official vendor/CDN sources.
E006: Malicious code pattern detected in skill scripts.
What this means
Detected high-risk code patterns in the skill content — including its prompts, tool definitions, and resources — such as data exfiltration, backdoors, remote code execution, credential theft, system compromise, supply chain attacks, and obfuscation techniques.
Why it was flagged
The repository contains multiple explicit offensive techniques that enable data exfiltration, credential theft, and system compromise (e.g., netcat-based KeePass exfiltration, LUKS master-key recovery and reuse, DNSSEC private key recovery/forging, and the Timeroasting MS‑SNTP attack chain).
W008: Secret detected in skill content (API keys, tokens, passwords).
What this means
Detected sensitive credentials directly embedded within the skill content, such as API keys, access tokens, private keys, or service-specific secrets. Secrets should never be hardcoded in plain text within skill instructions.
Why it was flagged
I scanned the documentation for literal, high-entropy values that could be real credentials. Flagged: - disk-advanced.md contains a 64-hex-character string assigned to authentic_key_hex. This is a high-entropy literal (32 bytes) used as a pre-poisoning key in an example decryption routine — qualifies as a secret material value. - network.md contains a long, complex password passed to 7z in an example (7z ... -p"M)m5s6S^[>@#Q3+10PD.KE#cyPsvqH"). This is a high-entropy, specific password literal (not a generic placeholder), so I treat it as a hardcoded secret. Ignored / not flagged: - Base64 strings and visible "flag{...}" examples (e.g., in recursive binwalk examples) are challenge flags, not service credentials. - Example hashes or hashcat-format lines (e.g., MS-SNTP/hashcat examples) are sample/derived hashes for cracking exercises, not active API keys/private keys to external services; treated as examples rather than usable credentials. - Obvious placeholders like "deadbeef...", "YOUR_API_KEY", or truncated/redacted values are ignored per the rules. I only flagged literals that are high-entropy and presented as key/password material in code examples.
- Repository
- ljagiello/ctf-skills
- Commit
d19f35f
- Audited
- Security analysis
Is this your skill?
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.