--- name: malware-analyst description: "File identification workflow skill. Use this skill when the user needs Expert malware analyst specializing in defensive malware research, threat intelligence, and incident response. Masters sandbox analysis, behavioral analysis, and malware family identification and the operator should preserve the upstream workflow, copied support files, and provenance before merging or handing off." version: "0.0.1" category: tools tags: ["malware-analyst", "expert", "malware", "analyst", "specializing", "defensive", "research", "threat"] complexity: intermediate risk: caution tools: ["codex-cli", "claude-code", "cursor", "gemini-cli", "opencode"] source: community author: "sickn33" date_added: "2026-04-15" date_updated: "2026-04-25" --- # File identification ## Overview This public intake copy packages `plugins/antigravity-awesome-skills-claude/skills/malware-analyst` from `https://github.com/sickn33/antigravity-awesome-skills` into the native Omni Skills editorial shape without hiding its origin. Use it when the operator needs the upstream workflow, support files, and repository context to stay intact while the public validator and private enhancer continue their normal downstream flow. This intake keeps the copied upstream files intact and uses the `external_source` block in `metadata.json` plus `ORIGIN.md` as the provenance anchor for review. # File identification file sample.exe sha256sum sample.exe # String extraction strings -a sample.exe | head -100 FLOSS sample.exe # Obfuscated strings # Packer detection diec sample.exe # Detect It Easy exeinfope sample.exe # Import analysis rabin2 -i sample.exe dumpbin /imports sample.exe `` ### Phase 3: Static Analysis 1. Load in disassembler: IDA Pro, Ghidra, or Binary Ninja 2. Identify main functionality: Entry point, WinMain, DllMain 3. Map execution flow: Key decision points, loops 4. Identify capabilities: Network, file, registry, process operations 5. Extract IOCs: C2 addresses, file paths, mutex names ### Phase 4: Dynamic Analysis ` 1. Environment Setup: - Windows VM with common software installed - Process Monitor, Wireshark, Regshot - API Monitor or x64dbg with logging - INetSim or FakeNet for network simulation 2. Execution: - Start monitoring tools - Execute sample - Observe behavior for 5-10 minutes - Trigger functionality (connect to network, etc.) 3. Documentation: - Network connections attempted - Files created/modified - Registry changes - Processes spawned - Persistence mechanisms `` Imported source sections that did not map cleanly to the public headings are still preserved below or in the support files. Notable imported sections: Common Malware Techniques, Tool Proficiency, IOC Extraction, Reporting Framework, Executive Summary, Sample Information. ## When to Use This Skill Use this section as the trigger filter. It should make the activation boundary explicit before the operator loads files, runs commands, or opens a pull request. - Working on file identification tasks or workflows - Needing guidance, best practices, or checklists for file identification - The task is unrelated to file identification - You need a different domain or tool outside this scope - Use when the request clearly matches the imported source intent: Expert malware analyst specializing in defensive malware research, threat intelligence, and incident response. Masters sandbox analysis, behavioral analysis, and malware family identification. - Use when the operator should preserve upstream workflow detail instead of rewriting the process from scratch. ## Operating Table | Situation | Start here | Why it matters | | --- | --- | --- | | First-time use | `metadata.json` | Confirms repository, branch, commit, and imported path through the `external_source` block before touching the copied workflow | | Provenance review | `ORIGIN.md` | Gives reviewers a plain-language audit trail for the imported source | | Workflow execution | `SKILL.md` | Starts with the smallest copied file that materially changes execution | | Supporting context | `SKILL.md` | Adds the next most relevant copied source file without loading the entire package | | Handoff decision | `## Related Skills` | Helps the operator switch to a stronger native skill when the task drifts | ## Workflow This workflow is intentionally editorial and operational at the same time. It keeps the imported source useful to the operator while still satisfying the public intake standards that feed the downstream enhancer flow. 1. Clarify goals, constraints, and required inputs. 2. Apply relevant best practices and validate outcomes. 3. Provide actionable steps and verification. 4. If detailed examples are required, open resources/implementation-playbook.md. 5. Confirm the user goal, the scope of the imported workflow, and whether this skill is still the right router for the task. 6. Read the overview and provenance files before loading any copied upstream support files. 7. Load only the references, examples, prompts, or scripts that materially change the outcome for the current request. ### Imported Workflow Notes #### Imported: Instructions - Clarify goals, constraints, and required inputs. - Apply relevant best practices and validate outcomes. - Provide actionable steps and verification. - If detailed examples are required, open `resources/implementation-playbook.md`. #### Imported: Common Malware Techniques ### Persistence Mechanisms ``` Registry Run keys - HKCU/HKLM\Software\Microsoft\Windows\CurrentVersion\Run Scheduled tasks - schtasks, Task Scheduler Services - CreateService, sc.exe WMI subscriptions - Event subscriptions for execution DLL hijacking - Plant DLLs in search path COM hijacking - Registry CLSID modifications Startup folder - %APPDATA%\Microsoft\Windows\Start Menu\Programs\Startup Boot records - MBR/VBR modification ``` ### Evasion Techniques ``` Anti-VM - CPUID, registry checks, timing Anti-debugging - IsDebuggerPresent, NtQueryInformationProcess Anti-sandbox - Sleep acceleration detection, mouse movement Packing - UPX, Themida, VMProtect, custom packers Obfuscation - String encryption, control flow flattening Process hollowing - Inject into legitimate process Living-off-the-land - Use built-in tools (PowerShell, certutil) ``` ### C2 Communication ``` HTTP/HTTPS - Web traffic to blend in DNS tunneling - Data exfil via DNS queries Domain generation - DGA for resilient C2 Fast flux - Rapidly changing DNS Tor/I2P - Anonymity networks Social media - Twitter, Pastebin as C2 channels Cloud services - Legitimate services as C2 ``` ## Examples ### Example 1: Ask for the upstream workflow directly ```text Use @malware-analyst to handle . Start from the copied upstream workflow, load only the files that change the outcome, and keep provenance visible in the answer. ``` **Explanation:** This is the safest starting point when the operator needs the imported workflow, but not the entire repository. ### Example 2: Ask for a provenance-grounded review ```text Review @malware-analyst against metadata.json and ORIGIN.md, then explain which copied upstream files you would load first and why. ``` **Explanation:** Use this before review or troubleshooting when you need a precise, auditable explanation of origin and file selection. ### Example 3: Narrow the copied support files before execution ```text Use @malware-analyst for . Load only the copied references, examples, or scripts that change the outcome, and name the files explicitly before proceeding. ``` **Explanation:** This keeps the skill aligned with progressive disclosure instead of loading the whole copied package by default. ### Example 4: Build a reviewer packet ```text Review @malware-analyst using the copied upstream files plus provenance, then summarize any gaps before merge. ``` **Explanation:** This is useful when the PR is waiting for human review and you want a repeatable audit packet. ## Best Practices Treat the generated public skill as a reviewable packaging layer around the upstream repository. The goal is to keep provenance explicit and load only the copied source material that materially improves execution. - Incident response and forensics - Threat intelligence research - Security product development - Academic research - CTF competitions - Creating or distributing malware - Attacking systems without authorization ### Imported Operating Notes #### Imported: Ethical Guidelines ### Appropriate Use - Incident response and forensics - Threat intelligence research - Security product development - Academic research - CTF competitions ### Never Assist With - Creating or distributing malware - Attacking systems without authorization - Evading security products maliciously - Building botnets or C2 infrastructure - Any offensive operations without proper authorization ## Troubleshooting ### Problem: The operator skipped the imported context and answered too generically **Symptoms:** The result ignores the upstream workflow in `plugins/antigravity-awesome-skills-claude/skills/malware-analyst`, fails to mention provenance, or does not use any copied source files at all. **Solution:** Re-open `metadata.json`, `ORIGIN.md`, and the most relevant copied upstream files. Check the `external_source` block first, then restate the provenance before continuing. ### Problem: The imported workflow feels incomplete during review **Symptoms:** Reviewers can see the generated `SKILL.md`, but they cannot quickly tell which references, examples, or scripts matter for the current task. **Solution:** Point at the exact copied references, examples, scripts, or assets that justify the path you took. If the gap is still real, record it in the PR instead of hiding it. ### Problem: The task drifted into a different specialization **Symptoms:** The imported skill starts in the right place, but the work turns into debugging, architecture, design, security, or release orchestration that a native skill handles better. **Solution:** Use the related skills section to hand off deliberately. Keep the imported provenance visible so the next skill inherits the right context instead of starting blind. ## Related Skills - `@00-andruia-consultant` - Use when the work is better handled by that native specialization after this imported skill establishes context. - `@00-andruia-consultant-v2` - Use when the work is better handled by that native specialization after this imported skill establishes context. - `@10-andruia-skill-smith` - Use when the work is better handled by that native specialization after this imported skill establishes context. - `@10-andruia-skill-smith-v2` - Use when the work is better handled by that native specialization after this imported skill establishes context. ## Additional Resources Use this support matrix and the linked files below as the operator packet for this imported skill. They should reflect real copied source material, not generic scaffolding. | Resource family | What it gives the reviewer | Example path | | --- | --- | --- | | `references` | copied reference notes, guides, or background material from upstream | `references/n/a` | | `examples` | worked examples or reusable prompts copied from upstream | `examples/n/a` | | `scripts` | upstream helper scripts that change execution or validation | `scripts/n/a` | | `agents` | routing or delegation notes that are genuinely part of the imported package | `agents/n/a` | | `assets` | supporting assets or schemas copied from the source package | `assets/n/a` | ### Imported Reference Notes #### Imported: Tool Proficiency ### Analysis Platforms ``` Cuckoo Sandbox - Open-source automated analysis ANY.RUN - Interactive cloud sandbox Hybrid Analysis - VirusTotal alternative Joe Sandbox - Enterprise sandbox solution CAPE - Cuckoo fork with enhancements ``` ### Monitoring Tools ``` Process Monitor - File, registry, process activity Process Hacker - Advanced process management Wireshark - Network packet capture API Monitor - Win32 API call logging Regshot - Registry change comparison ``` ### Unpacking Tools ``` Unipacker - Automated unpacking framework x64dbg + plugins - Scylla for IAT reconstruction OllyDumpEx - Memory dump and rebuild PE-sieve - Detect hollowed processes UPX - For UPX-packed samples ``` #### Imported: IOC Extraction ### Indicators to Extract ```yaml Network: - IP addresses (C2 servers) - Domain names - URLs - User-Agent strings - JA3/JA3S fingerprints File System: - File paths created - File hashes (MD5, SHA1, SHA256) - File names - Mutex names Registry: - Registry keys modified - Persistence locations Process: - Process names - Command line arguments - Injected processes ``` ### YARA Rules ```yara rule Malware_Generic_Packer { meta: description = "Detects common packer characteristics" author = "Security Analyst" strings: $mz = { 4D 5A } $upx = "UPX!" ascii $section = ".packed" ascii condition: $mz at 0 and ($upx or $section) } ``` #### Imported: Reporting Framework ### Analysis Report Structure ```markdown # Malware Analysis Report #### Imported: Executive Summary - Sample identification - Key findings - Threat level assessment #### Imported: Sample Information - Hashes (MD5, SHA1, SHA256) - File type and size - Compilation timestamp - Packer information #### Imported: Static Analysis - Imports and exports - Strings of interest - Code analysis findings #### Imported: Dynamic Analysis - Execution behavior - Network activity - Persistence mechanisms - Evasion techniques #### Imported: Indicators of Compromise - Network IOCs - File system IOCs - Registry IOCs #### Imported: Recommendations - Detection rules - Mitigation steps - Remediation guidance ``` #### Imported: Response Approach 1. **Verify context**: Ensure defensive/authorized purpose 2. **Assess sample**: Quick triage to understand what we're dealing with 3. **Recommend approach**: Appropriate analysis methodology 4. **Guide analysis**: Step-by-step instructions with safety considerations 5. **Extract value**: IOCs, detection rules, understanding 6. **Document findings**: Clear reporting for stakeholders #### Imported: Limitations - Use this skill only when the task clearly matches the scope described above. - Do not treat the output as a substitute for environment-specific validation, testing, or expert review. - Stop and ask for clarification if required inputs, permissions, safety boundaries, or success criteria are missing.