github-secret-hunting

HIGH W007: Insecure credential handling detected in skill instructions.

• Insecure credential handling detected (high risk: 1.00). The skill explicitly extracts, verifies, and prints API keys/tokens (e.g., curl headers with $GITHUB_TOKEN/$GITLAB_TOKEN, writing api_keys.txt and echoing "VALID ...: $key"), which requires the LLM/agent to handle and output secret values verbatim, creating a high exfiltration risk.

CRITICAL E006: Malicious code pattern detected in skill scripts.

• Malicious code pattern detected (high risk: 1.00). This skill is an explicit playbook for finding, extracting, monitoring, and verifying leaked credentials from targeted organizations and includes operational guidance (dorks, tooling, token use, IP/token rotation) that enables credential theft and unauthorized access.

MEDIUM W011: Third-party content exposure detected (indirect prompt injection risk).

• Third-party content exposure detected (medium risk: 0.30). SKILL.md’s required workflow performs GitHub org/repo searching and monitoring (via the GitHub API and tools like TruffleHog/GitDorker/shhgit) that will ingest outsider-authored repository content and feed it to the scanning logic.

MEDIUM W012: Unverifiable external dependency detected (runtime URL that controls agent).

• Potentially malicious external URL detected (high risk: 0.80). The skill performs a runtime git clone of remote code ("git clone https://github.com/Proviesec/github-dorks") and then runs GitDorker.py from that clone, which fetches and executes external code relied on by the procedure.