Use when systematically remove malware, backdoors, and attacker persistence
Scanned 9/8/2026
Install to Claude Code
npx -y skills add oyi77/1ai-skills --skill eradicating-malware-from-infected-systems --agent claude-codeInstalls into .claude/skills of the current project.
Are you the author of Eradicating Malware From Infected Systems?
Add the live security badge to your README — it updates automatically with every re-scan.
[](https://www.skillsdirectory.com/skills/oyi77-eradicating-malware-from-infected-systems)More formats (shields.io, HTML) on the badges page.
---
name: eradicating-malware-from-infected-systems
description: Use when systematically remove malware, backdoors, and attacker persistence
mechanisms from infected systems while ensuring complete eradication and preventing
re-infection. Use when working with eradicating malware from infected systems.
domain: cybersecurity
tags:
- incident-response
- eradication
- malware-removal
- persistence
- dfir
subdomain: incident-response
mitre_attack:
- T1547
- T1053
- T1543
- T1574
version: '1.0'
author: oyi77
license: Apache-2.0
nist_csf:
- RS.MA-01
- RS.MA-02
- RS.AN-03
- RC.RP-01
category: cybersecurity
---
# Eradicating Malware From Infected Systems
## Overview
Cybersecurity skill for eradicating malware from infected systems. Follows industry best practices and security standards.
## When to Use
**Trigger phrases:**
- "eradicating malware from infected systems"
- "Systematically remove malware, backdoors, and attacker persistence mechanisms fr"
- Malware infection confirmed and containment is in place
- Forensic investigation has identified all persistence mechanisms
- All compromised systems have been identified and scoped
- Ready to remove attacker artifacts and restore clean state
- Post-containment phase requires systematic cleanup
## When NOT to Use
- When you lack proper authorization for testing
- For production systems without change management
- When the task requires legal or compliance expertise beyond technical scope
## Prerequisites
- Completed forensic analysis identifying all malware artifacts
- List of all compromised systems and accounts
- EDR/AV with updated signatures deployed
- YARA rules for the specific malware family
- Clean system images or verified backups for restoration
- Network isolation still in effect during eradication
## Workflow
```python
# Example: IOC detection
import re
IOC_PATTERNS = {
"ip": r"\b(?:\d{1,3}\.){3}\d{1,3}\b",
"domain": r"\b[a-z0-9-]+\.[a-z]{2,}\b",
"hash_md5": r"\b[a-f0-9]{32}\b",
"hash_sha256": r"\b[a-f0-9]{64}\b",
}
def extract_iocs(text: str) -> dict:
return {k: re.findall(v, text) for k, v in IOC_PATTERNS.items()}
```
1. **Define Objectives** — Clarify the goals and scope for malware from infected systems.
2. **Gather Resources** — Collect tools, data, and access needed for malware from infected systems.
3. **Execute Process** — Carry out malware from infected systems operations methodically.
4. **Verify Quality** — Check results against acceptance criteria.
5. **Document Outcomes** — Record findings, decisions, and next steps.
## Tools
- **Analysis Platform** — Data processing and visualization
- **Collaboration Tools** — Team coordination and knowledge sharing
## Process
1. **Reconnaissance** — Gather target information, identify attack surface, enumerate services
1. **Analysis/Exploitation** — Execute the technique, analyze results, document findings
1. **Reporting** — Document IOCs, write findings, provide remediation recommendations
## Verification
- [ ] All malware from infected systems procedures executed completely and documented
- [ ] Findings validated against multiple data sources
- [ ] False positives identified and filtered
- [ ] Results documented with evidence and timestamps
- [ ] Recommendations provided with risk-based prioritization
## Anti-Rationalization Table
| Rationalization | Reality |
|---|---|
| "We are too small to be targeted" | Automated attacks target everyone. Size does not matter. |
| "Security slows us down" | A breach slows you down 100x more. Build security in from the start. |
| "We will fix it after launch" | Vulnerabilities in production are exploited within hours. Fix before deploy. |Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.
No comments yet. Be the first to comment!