FC eradicating-malware-from-infected-systems
Systematically map and remove malware, backdoors, and attacker persistence mechanisms (registry Run keys, scheduled tasks, WMI subscriptions, services, cron/init.d) from infected Windows and Linux systems using Autoruns, EDR/AV, and YARA, restoring a clean state while preventing re-infection. Use after containment and forensic analysis have identified all compromised systems and persistence mechanisms and you are ready to eradicate and recover.
Systematically map and remove malware, backdoors, and attacker persistence mechanisms (registry Run keys, scheduled tasks, WMI subscriptions, services…
As a process C 62/100 · Has gaps — weak spots: when it triggers, failures and branches, running it twice
What is at stake
Medium-severity findings: the skill is probably honest, but read what alarmed the scanner.
Below is the worst case for this category. The finding here is medium: the guard saw a sign, not a proof.
The skill contains commands that delete files, rewrite disks or execute code fetched from the network. The agent may run them without asking if it believes the instructions require it.
Replace destructive commands with safe equivalents that ask for confirmation, scope them to one folder, and stop piping curl into a shell: pin a version and a checksum.
How to improve
- Your own cases (evals/evals.json, 4–6 real requests with expected answers): the full check would then run those instead of a model-drafted suite.
- A spec.yaml with trigger phrases and assertions — a behaviour contract for CI; `skilltest init` writes a template.
Guard findings · 22
✓ No critical or high findings
Medium and low: 22
-
medium Dangerous commands
cmd-persistencereferences/api-reference.md:45Persistence mechanism (cron / launchd / scheduled task / autorun registry) (documentation of a security skill)ls -la /etc/cron.d/
security skill -
medium Dangerous commands
cmd-persistencereferences/workflows.md:80Persistence mechanism (cron / launchd / scheduled task / autorun registry) (documentation of a security skill)HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Run
security skill -
medium Dangerous commands
cmd-persistencereferences/workflows.md:81Persistence mechanism (cron / launchd / scheduled task / autorun registry) (documentation of a security skill)HKCU\SOFTWARE\Microsoft\Windows\CurrentVersion\Run
security skill -
medium Dangerous commands
cmd-persistencereferences/workflows.md:89Persistence mechanism (cron / launchd / scheduled task / autorun registry) (documentation of a security skill)%AppData%\Microsoft\Windows\Start Menu\Programs\Startup
security skill -
medium Dangerous commands
cmd-persistencereferences/workflows.md:90Persistence mechanism (cron / launchd / scheduled task / autorun registry) (documentation of a security skill)C:\ProgramData\Microsoft\Windows\Start Menu\Programs\Startup
security skill -
medium Dangerous commands
cmd-persistencereferences/workflows.md:103Persistence mechanism (cron / launchd / scheduled task / autorun registry) (documentation of a security skill)/etc/crontab
security skill -
medium Dangerous commands
cmd-persistencescripts/agent.py:13Persistence mechanism (cron / launchd / scheduled task / autorun registry) (string literal in code, not executed)r"HKCU\Software\Microsoft\Windows\CurrentVersion\Run",
code literal -
medium Dangerous commands
cmd-persistencescripts/agent.py:14Persistence mechanism (cron / launchd / scheduled task / autorun registry) (string literal in code, not executed)r"HKLM\Software\Microsoft\Windows\CurrentVersion\Run",
code literal -
medium Dangerous commands
cmd-persistencescripts/agent.py:21Persistence mechanism (cron / launchd / scheduled task / autorun registry) (string literal in code, not executed)"/etc/cron.d", "/var/spool/cron", "/etc/crontab",
code literal -
medium Dangerous commands
cmd-persistencescripts/process.py:68Persistence mechanism (cron / launchd / scheduled task / autorun registry) (string literal in code, not executed)r"HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Run",
code literal -
medium Dangerous commands
cmd-persistencescripts/process.py:69Persistence mechanism (cron / launchd / scheduled task / autorun registry) (string literal in code, not executed)r"HKCU\SOFTWARE\Microsoft\Windows\CurrentVersion\Run",
code literal -
medium Dangerous commands
cmd-persistenceSKILL.md:76Persistence mechanism (cron / launchd / scheduled task / autorun registry) (documentation of a security skill)cat /etc/crontab
security skill -
low Dangerous commands
cmd-cron-mentionreferences/api-reference.md:43Mentions editing / listing crontab (documentation of a security skill)crontab -l -u root # List root cron
security skill -
low Risky intent
intent-offensive-securityreferences/standards.md:57Offensive-security / dual-use content (legitimate for authorised testing; review intended use)## CISA Malware Analysis Reports (MARs)
-
low Dangerous commands
cmd-persistencescripts/process.py:150Persistence mechanism (cron / launchd / scheduled task / autorun registry) (detector / deny-list definition; string literal in code, not executed)os.path.expandvars(r"%APPDATA%\Microsoft\Windows\Start Menu\Programs\Startup"),
detectorcode literal -
low Dangerous commands
cmd-persistencescripts/process.py:151Persistence mechanism (cron / launchd / scheduled task / autorun registry) (detector / deny-list definition; string literal in code, not executed)r"C:\ProgramData\Microsoft\Windows\Start Menu\Programs\Startup",
detectorcode literal -
low Dangerous commands
cmd-persistencescripts/process.py:189Persistence mechanism (cron / launchd / scheduled task / autorun registry) (detector / deny-list definition; string literal in code, not executed)cron_paths = ["/etc/crontab"]
detectorcode literal
A further 5 matches are quotations in this security skill's documentation and are not counted as findings.
Files scanned: 8. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- note
frontmatter-keyunknown frontmatter key "domain" - note
frontmatter-keyunknown frontmatter key "subdomain" - note
frontmatter-keyunknown frontmatter key "mitre_attack" - note
frontmatter-keyunknown frontmatter key "nist_csf"
Process rating: all ten parameters 62/100
- 0Failures and branches. Linear process with no failure handling
- 20When it triggers. No condition that starts the skill
- 30Running it twice. 9 mutating operations with no state check
- 60Tools and files. Uses tools (bash) that frontmatter does not declare
- 60Result and completion. Output format stated, no completion criterion
- 70Inputs and preconditions. Inputs and preconditions are listed
- 100Steps. 21 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 1980 tokens
- 100Progress reporting. Reports progress
Everything here is measured from the skill text rather than judged by a model, so the numbers are checkable. A parameter weighs more when it is a more common reason for the process to stall.
Quality signals
- +5Description has no quoted example phrases that should trigger the skill
- +4Description does not say when NOT to use the skill (false activations)
- -4Absolute local paths (C:\Users, /home/…): not portable
- -43 reference files, but SKILL.md never points to them: the model will not open them
- -32 of 2 scripts are never mentioned in SKILL.md
- +2Single-language instructions
- +3Description length 448: enough signal without eating the budget
- +4Structure: 14 headings
- +3Step-by-step instructions: 21 items
- +3Output format is stated explicitly
- +4Has examples (6 code blocks)
- +1License stated
Quality base 70; lint remarks subtract, signals add up to 100. Result: 74.