Respond to a malware incident following PICERL methodology. Use when malware is detected on endpoints. Orchestrates triage, containment, eradication, and recovery. Works with triage-malware skill for analysis.
57
66%
Does it follow best practices?
Run evals on this skill
Adds up to 20 points to the overall score
View guide
Medium
Suggest reviewing before use
Fix and improve this skill with Tessl
tessl review fix ./skills/respond-malware/SKILL.mdSecurity
1 medium severity finding. This skill can be installed but you should review these findings before use.
The skill prompts the agent to compromise the security or integrity of the user’s machine by modifying system-level services or configurations, such as obtaining elevated privileges, altering startup scripts, or changing system-wide settings.
The skill explicitly instructs actions that change system state (isolate endpoints, block IOCs at firewalls, terminate processes, delete files, remove registry keys, trigger compromised-account responses, and rebuild/clean hosts), all of which require elevated privileges and can modify the machine or environment.
Low
Low-risk findings.
1 low severity finding. Worth noting, but not necessarily harmful.
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.
The runtime workflow ingests case text from first-party SOAR via `secops-soar.get_case_full_details(case_id=CASE_ID)`, and that case content can originate from outsider-submitted alerts/feeds but the skill does not restrict it to trusted, vendor-authored fields before the LLM processes it.
72a6863
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.