Builds an automated malware submission and analysis pipeline that collects suspicious files from endpoints and email gateways, submits them to sandbox environments and multi-engine scanners, and generates verdicts with IOCs for SIEM integration. Use when SOC teams need to scale malware analysis beyond manual sandbox submissions for high-volume alert triage.
76
71%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Risky
Do not use without reviewing
Optimize this skill with Tessl
npx tessl skill review --optimize ./skills/building-automated-malware-submission-pipeline/SKILL.mdSecurity
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: 1.00). The prompt's code and workflow require embedding API tokens and keys directly into HTTP headers and request payloads (e.g., Authorization: Bearer {api_token}, Splunk {splunk_token}, vt_api_key, joe_api_key), which would force an agent to accept and include secret values verbatim in generated requests or outputs, creating an 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: 1.00). The skill explicitly ingests public third‑party data from VirusTotal and MalwareBazaar (see SKILL.md Step 2 "Pre‑Screen with Hash Lookups" and scripts/agent.py functions check_virustotal/check_malwarebazaar), and it parses those untrusted responses to decide sandboxing, verdicts, and blocking actions—allowing external content to materially influence tool use and next steps.
c15f73d
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.