Parse and analyze email headers to trace the origin of phishing emails, verify sender authenticity, and identify spoofing through SPF, DKIM, and DMARC validation.
61
—
Does it follow best practices?
Impact
—
No eval scenarios have been run
Risky
Do not use without reviewing
Security
2 findings — 1 high severity, 1 medium severity. You should review these findings carefully before considering using this skill.
The skill handles credentials insecurely by requiring the agent to include secret values verbatim in its generated output. This exposes credentials in the agent’s context and conversation history, creating a risk of data exfiltration.
Insecure credential handling detected (high risk: 0.90). The prompt includes examples that embed API keys directly into curl commands/headers (e.g., "Key: YOUR_API_KEY", "x-apikey: YOUR_VT_API_KEY"), which encourages the agent to insert secret values verbatim into generated commands or code, creating exfiltration risk.
The skill exposes the agent to untrusted, user-generated content from public third-party sources, creating a risk of indirect prompt injection. This includes browsing arbitrary URLs, reading social media posts or forum comments, and analyzing content from unknown websites.
Third-party content exposure detected (high risk: 0.85). The skill ingests the suspicious email’s raw EML/MSG content (including headers/body/attachments) from a runtime-provided file path (e.g., `/cases/.../phishing_email.eml`), and that email is an outsider-authored message whose readable text is parsed and then printed/used in the agent’s context (e.g., via `parse_email_file()` and `extract_urls()`), creating indirect prompt-injection exposure through attacker-controlled email text.
673da1f
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.