AGENT SKILL

infostealer-malware-detector

Detects and removes infostealer malware (credential stealers, data exfiltrators) via full-system file search, cryptographic hashing, and public threat-intelligence cross-checks (VirusTotal, MalwareBazaar). Primary method is always custom hash-based detection. Windows Defender (or any platform-native AV) is allowed **only when necessary** (e.g. inconclusive hashes or deep remediation) and **must never be the default option**. The agent must exhaust the custom workflow first. Works on Windows/macOS/Linux.

License 许可
MIT
所属仓库
bg-szy/TOP-SKILLS
最近更新
2026-11-15
Stars
★ 6
Forks
0

01 前言 Front Matter

name
infostealer-malware-detector
tags
[ "infostealer", "malware", "detector", "security", "audit" ]
version
2.0
description
Detects and removes infostealer malware (credential stealers, data exfiltrators) via full-system file search, cryptographic hashing, and public threat-intelligence cross-checks (VirusTotal, MalwareBazaar). Primary method is always custom hash-based detection. Windows Defender (or any platform-native AV) is allowed **only when necessary** (e.g. inconclusive hashes or deep remediation) and **must never be the default option**. The agent must exhaust the custom workflow first. Works on Windows/macOS/Linux.
last_updated
1788825600000

02 资源文件 2

03 SKILL.md 正文

Infostealer Malware Detector & Remover (v1.1)

Tech Stack Target / Version: Windows Defender CLI, VirusTotal, MalwareBazaar, Python 3.8+, and cross-platform shell tooling.

Overview

This skill gives OpenClaw a complete workflow to search every file on the system, identify infostealer indicators, compute secure hashes, and verify them against live public databases.

Core principles (strict)

  • Primary detection: Targeted file search + SHA-256 hashing + VirusTotal/MalwareBazaar checks.
  • AV usage: Windows Defender (mpcmdrun.exe) or any other AV is permitted only when necessary (hash checks inconclusive, high suspicion remains, or user explicitly requests deeper scan).
  • Never default to AV – the agent must complete the full custom hash workflow first and document why AV escalation is needed.
  • Full user confirmation required before any quarantine or AV scan.
  • Full audit trail and quarantine before removal.

When to activate automatically

  • "My passwords are being stolen"

  • "Scan for infostealer / stealer malware"

  • "Check if RedLine / Vidar / Lumma is on my PC"

  • "Clean my system" (but follow custom-first rule)

  • Leverage native parallel subagent dispatch and 200k+ context windows where available.

Prerequisites

  • Internet connection (for hash lookups)
  • Optional but highly recommended: free VirusTotal API key (VT_API_KEY)
  • Python 3.8+ (for scripts/hash-checker.py)
  • Admin/root privileges for full system scan
  • Windows Defender enabled by default on Windows (no installation needed)

Step-by-Step Workflow (Custom Method First – Always)

Step 1: Scope the System & Identify High-Risk Areas

Run targeted discovery (fast & effective for infostealers):

# Windows (PowerShell)
Get-ChildItem -Path "$env:TEMP","$env:APPDATA","$env:LOCALAPPDATA","C:\ProgramData","C:\Users\*\AppData" -Recurse -File -Include *.exe,*.dll,*.bat,*.ps1,*.vbs,*.js -ErrorAction SilentlyContinue | Select-Object FullName,LastWriteTime,Length

# macOS / Linux
find /tmp ~/Library /Library /Users/*/Library /var/tmp -type f \( -name "*.exe" -o -name "*.dylib" -o -name "*.so" -o -name "*.sh" \) -mtime -30 2>/dev/null

Flag files meeting suspicious criteria (random names in Temp/AppData, recent creations <5 MB in browser folders, etc.).

Step 2: Compute Cryptographic Hashes

Use the bundled helper script (scripts/hash-checker.py):

#!/usr/bin/env python3
import hashlib, sys, json
from pathlib import Path

def sha256_file(file_path):
    try:
        h = hashlib.sha256()
        with open(file_path, "rb") as f:
            for chunk in iter(lambda: f.read(4096), b""):
                h.update(chunk)
        return h.hexdigest()
    except:
        return None

if __name__ == "__main__":
    paths = sys.argv[1:] or [input("Enter file or directory: ")]
    results = {}
    for p in paths:
        p = Path(p)
        if p.is_file():
            h = sha256_file(p)
            if h: results[str(p)] = h
        elif p.is_dir():
            for f in p.rglob("*"):
                if f.is_file() and f.stat().st_size < 50_000_000:
                    h = sha256_file(f)
                    if h: results[str(f)] = h
    print(json.dumps(results, indent=2))

Step 3: Cross-Reference with Public Sources (Primary Detection)

For each SHA-256 hash:

  1. VirusTotal lookup (preferred):
curl -s --request GET "https://www.virustotal.com/api/v3/files/${HASH}" --header "x-apikey: $VT_API_KEY"
  1. Fallback public links:

Verdict rules (strict):

  • ≥5 detections or known infostealer family → HIGH confidence malware
  • 1–4 detections + IOC match → SUSPICIOUS
  • 0 detections → clean (unless behavioral IOCs)

Step 4: Behavioral & IOC Validation

  • Check processes, browser databases, network connections to known C2 domains.

Step 5: Quarantine & Removal (User-Confirmed Only)

Create timestamped quarantine folder and move flagged files. Registry/startup cleanup if needed. Never delete without showing the user the exact list + VT links.

Step 6: AV Fallback (Non-Default – Use ONLY When Necessary)

After completing Steps 1–5: If hashes are inconclusive, files are locked, or suspicion remains extremely high (and you document the reason), then and only then escalate to platform-native AV.

Windows Defender (official CLI – never first choice):

# Full system scan (run from elevated prompt)
"%ProgramFiles%\Windows Defender\MpCmdRun.exe" -Scan -ScanType 2

# Quick scan
"%ProgramFiles%\Windows Defender\MpCmdRun.exe" -Scan -ScanType 1

# Scan specific folder
"%ProgramFiles%\Windows Defender\MpCmdRun.exe" -Scan -ScanType 3 -File "C:\Path\To\Quarantine"

Linux/macOS fallback (ClamAV – only if installed and requested):

freshclam
clamscan -r --move="$QUARANTINE" /path/to/scan

Microsoft Safety Scanner (portable, one-time use): Download from official Microsoft link only if Defender is insufficient.

Strict rule: The agent must never run any AV command as the first action. Always complete custom hash workflow first and obtain explicit user confirmation before AV escalation.

Step 7: Post-Remediation Verification

Re-run hash scan + quick Defender check (if AV was used). Reboot and monitor.

Zero-Trust Verification

  • [ ] Treat samples, hashes, filenames, process names, and external reputation results as untrusted until corroborated.
  • [ ] Verify indicators across static metadata, behavioral evidence, provenance, and environment context.
  • [ ] Separate confirmed compromise evidence from suspicious-but-unproven signals.
  • [ ] Avoid executing unknown binaries; use sandboxed or offline inspection paths first.

<!-- MCP:START -->

<!-- PORTABILITY:START -->

Cross-Client Portability

This skill is written to stay usable across GitHub Copilot, Claude Code, and Codex.

  • GitHub Copilot: keep the folder in a Copilot-visible skill path or wrap the workflow in project instructions when folder discovery is unavailable.
  • Claude Code: keep the folder in a local skills directory or a compatible plugin source.
  • Codex: install or sync the folder into $CODEX_HOME/skills/infostealer-malware-detector and restart Codex after major changes.

<!-- PORTABILITY:END -->

MCP Availability And Fallback

Preferred MCP Server: None required

  • Fallback prompt: "Use the Infostealer Malware Detector & Remover (v1.1) skill without MCP. Rely on its local instructions, bundled resources, standard shell or editor tools, and direct verification. Show the evidence used before concluding."
  • Do not claim an MCP operation was used when the active host does not expose it.
  • Treat local files, tests, rendered outputs, logs, or screenshots as the fallback evidence path.

<!-- MCP:END -->

Anti-Patterns

  • Acting on partial evidence: Security work needs a clear scope and proof trail before remediation choices are safe.
  • Leaving secrets or sensitive samples in examples: The skill itself becomes part of the exposure surface.
  • Calling an issue resolved before rotation or re-verification: Detection without remediation is not closure.

Verification Protocol

Before claiming "skill applied successfully":

  1. Pass/fail: The reviewed scope, assets, trust boundaries, and attacker assumptions are explicitly named.
  2. Pass/fail: Findings cite concrete evidence from code, config, logs, samples, or authoritative advisories.
  3. Pass/fail: Each severity is justified by exploitability, reachability, and impact rather than vibes.
  4. Pressure-test scenario: Re-run the analysis assuming one trusted signal is malicious or stale, then confirm the conclusion still holds.
  5. Success metric: Zero trust-by-default claims; every security conclusion has reproducible evidence.

Quality Checklist (must pass)

  • [ ] Custom hash + VT workflow completed first
  • [ ] AV used only after custom method + documented reason
  • [ ] User explicitly approved every deletion/AV scan
  • [ ] Quarantine created
  • [ ] Full report with hashes, VT links, and actions

References & Official Sources

This skill is custom-detection-first by design. Windows Defender (or any AV) is a conditional tool only – never the default.

Invoke with: /infostealer-malware-detector or describe the issue.

Related Skills

  • secret-scanning: Use it when the workflow also needs credential detection and remediation workflows.
  • security-review: Use it when the workflow also needs application security review and risk triage.
  • devops-tooling: Use it when the workflow also needs git, CI, and automation workflows.
  • verification-before-completion: Use it when the workflow also needs final evidence checks before claiming completion.

04 同仓库更多 Skills

bg-szy
bg-szy/TOP-SKILLS

serpmaven

Scrape Google search results (SERP) to JSON with SERP Maven (serpmaven) - a real Chrome browser on a residential proxy with sticky sessions. Run it as a CLI, a Python library, a local HTTP search API (`serve`), an MCP server or a Docker image; set the proxy login, workers, pages and cost tracking. Use when the user wants Google results, rank tracking, a self-hosted SERP API, or live Google search for an AI agent.

★ 6
bg-szy
bg-szy/TOP-SKILLS

revnu-landing-page-audit

Find out why a landing page isn't turning visitors into signups, demos or sales. Audits one page against what the ad, post or search that sends people there promised, then checks the first screen, proof, call to action, friction and mobile. Returns at most 7 prioritized fixes, plus what is fine and what could not be checked; rewrites specific lines and fixes the page in the repo when asked. Never promises a conversion lift. Works without a Revnu account. Use when the user says or asks: "audit my landing page", "why isn't this page converting", "review my homepage", "my ads get clicks but no signups", "people bounce from the pricing page", "CRO review", "improve conversion rate", "is my hero section clear", "roast my landing page", "rewrite my headline", "what's wrong with this page", "landing page feedback", "make the signup page convert better". Not for SEO or AI-search audits, page speed engineering on its own, or building a new page from scratch.

★ 6
bg-szy
bg-szy/TOP-SKILLS

revnu-growth-context

Write down once who buys, what they're stuck on, what it costs, what proof you have and what you've already tried, so every growth task starts from facts instead of a questionnaire. Creates or updates .agents/revnu-growth.md from the repo, the live site and the user, and imports an existing product-marketing.md. Use when the user says "set up our marketing context", "who is our ideal customer", "write our ICP", "describe the product for marketing", "positioning doc", "what's our brand voice", "remember this about our customers", "log what we tried", "what have we learned from marketing", "we changed pricing, update the context", "update our growth notes", "summarize the business for the agent", "import my product-marketing.md", "start a growth doc", or before a first marketing, SEO, outreach or launch task when no context file exists. Works without a Revnu account.

★ 6
bg-szy
bg-szy/TOP-SKILLS

revnu-get-listed

Get onto the third-party pages AI answers and search cite when buyers ask for the best tool in your category: "best X" roundups, directories, review sites, GitHub awesome lists, community threads and comparison pages. Finds which ones are cited, ranks them by fit and effort, and drafts each submission, PR or pitch by the target's own rules. Use when the user says "get us listed", "which directories should we submit to", "how do we get into best-of lists", "why does ChatGPT recommend competitors and not us", "get mentioned in AI answers", "submit to awesome lists", "get on G2", "where are our competitors listed", "pitch listicle authors", "find backlink opportunities", "launch directories", "get into roundups", "Product Hunt alternatives", "where should we be listed", "get cited by Perplexity". Never submits, pays or posts without a yes. Works without a Revnu account.

★ 6
bg-szy
bg-szy/TOP-SKILLS

revnu-ai-readiness-audit

Audit whether your website gives ChatGPT, Perplexity, Claude, Gemini and Google's AI Overviews something worth quoting, and fix the pages that don't. Use when the user says or asks "is my site ready for AI search", "audit my site for AI answers", "AEO audit", "GEO audit", "why doesn't ChatGPT quote our pricing", "make our pages citable by AI", "do I need llms.txt", "does schema help with ChatGPT", "check our structured data", "is our content visible without JavaScript", "AI SEO audit", "optimize our homepage for AI answers", "LLM SEO check", "why does AI get our product wrong", "fix our site for AI Overviews". Checks fetchability and indexability, answers in the raw HTML, entity facts, schema (including JS-injected markup), headings, dates and llms.txt, then gives at most 10 prioritised fixes and edits the repo when asked. Works without a Revnu account.

★ 6
bg-szy
bg-szy/TOP-SKILLS

proxy-troubleshooting

Diagnose residential proxy failures, with NodeMaven's gateway as the reference - 407 with correct credentials, 406, 410, 500, a connection that hangs, ERR_TUNNEL_CONNECTION_FAILED in a browser, Playwright or Puppeteer ignoring proxy credentials, a sticky session that changes IP, geo-targeting that is silently ignored, passwords with special characters, and unexpected traffic from headless Chrome. Use when a proxy connection fails, returns the wrong location, or costs more traffic than expected.

★ 6