dast-nuclei

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

• Third-party content exposure detected (high risk: 0.85). The required runtime workflow runs Nuclei scans against user-supplied targets (e.g., nuclei -u $TARGET_URL / target_url), and Nuclei ingests arbitrary HTTP response bodies from those outsider-controlled targets into its output/JSONL that is then parsed and included in the agent’s context.

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

• Potentially malicious external URL detected (high risk: 0.90). The skill includes runtime dependencies that fetch and run external content: the GitHub Action "uses: projectdiscovery/nuclei-action@main" (https://github.com/projectdiscovery/nuclei-action) is executed at CI runtime and pulls remote action code, and the templates update command ("nuclei -update-templates") pulls templates from the Nuclei templates repo (https://github.com/projectdiscovery/nuclei-templates) which directly control scanning behavior—both are runtime dependencies required by the skill.

HIGH W008: Secret detected in skill content (API keys, tokens, passwords).

• Secret detected (high risk: 1.00). I scanned the entire skill content for literal, high-entropy values that could be used as credentials. I only flag values that are literal, look random/entropy-rich, and could be directly used to authenticate (not placeholders or obvious example words).

Findings:

• Flagged: "JBSWY3DPEHPK3PXP" — appears in the TOTP MFA example (references/ authentication_patterns.md, TOTP-based MFA section). This is a base32 TOTP secret (high-entropy, usable to generate valid one-time codes) and therefore a real credential if it were active.
• Flagged: "sk-1234567890abcdef" — appears in the hardcoded API key example (references/rule-template.yaml, Example Rule 2 vulnerable code). This follows an API key pattern (sk-... with hex-like payload) and is a literal, high-entropy-like string. Although shown as an example, it is a concrete key-like value in the doc and therefore flagged as a potential secret.

Ignored (not flagged) and why:

• Placeholders like "your-client-id", "your-client-secret", "your-refresh-token", "your-auth-token", "your-service-role-key", "$API_TOKEN", $AUTH_TOKEN, $SESSION_COOKIE, $API_KEY, $CLIENT_ID, etc. — documentation placeholders or environment variable names.
• Simple/example credentials such as "testuser", "testpass", "testpassword", "admin", "user_password" — low-entropy example values used for demonstration.
• Short/truncated or clearly redacted values (none otherwise present).
• Other header/env references (e.g., secrets.* in GitHub Actions) — they reference secret storage but do not contain literal secrets.

If you want, I can:

• Extract exact file/line snippets for the flagged values to help removal/replacement.
• Suggest safe replacement examples or recommended masking (e.g., replace with clearly labeled placeholders like <TOTP_SECRET_PLACEHOLDER> or ENV variables).