[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7B80Y5G3F7YVPDH5PQRH26B":3,"skill-same:01M7B80Y5G3F7YVPDH5PQRH26B":104},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":15,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":68,"commitSha":69,"skillDirectory":70,"forksCount":13,"repositoryHtmlUrl":71,"repositoryHomepageUrl":6,"ownerHtmlUrl":72,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":73,"install":74,"resources":87},"01M7B80Y5G3F7YVPDH5PQRH26B","investigating-ransomware-attack-artifacts",null,"Forensically preserve memory and disk, collect ransom notes and encrypted file samples, and identify the ransomware variant using tools such as ID Ransomware, Volatility, and Chainsaw\u002FHayabusa to determine the initial access vector and recovery options. Use immediately after discovering ransomware encryption, when scoping the incident forensically, or when documenting evidence for law enforcement and insurance claims.","vikasvardhanv\u002Fjerry_skills","vikasvardhanv","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F99010657?v=4","01M7B2B0VN78W7529RQX5BR6DZ","01M7B2B0WDNTXJHRK3QNPNWRP6",0,"Apache-2.0","https:\u002F\u002Fgithub.com\u002Fvikasvardhanv\u002Fjerry_skills\u002Fblob\u002Fmain\u002Fskills\u002Fcurated_premium_skills\u002FAnthropic-Cybersecurity-Skills\u002Fskills\u002Finvestigating-ransomware-attack-artifacts\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fvikasvardhanv\u002Fjerry_skills\u002Fblob\u002Fmain\u002Fskills\u002Fcurated_premium_skills\u002FAnthropic-Cybersecurity-Skills\u002Fskills\u002Finvestigating-ransomware-attack-artifacts\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: investigating-ransomware-attack-artifacts\ndescription: Forensically preserve memory and disk, collect ransom notes and encrypted file samples, and identify the ransomware variant using tools such as ID Ransomware, Volatility, and Chainsaw\u002FHayabusa to determine the initial access vector and recovery options. Use immediately after discovering ransomware encryption, when scoping the incident forensically, or when documenting evidence for law enforcement and insurance claims.\ndomain: cybersecurity\nsubdomain: digital-forensics\ntags:\n- forensics\n- ransomware\n- malware-analysis\n- incident-response\n- encryption-recovery\n- evidence-collection\nversion: '1.0'\nauthor: mahipal\nlicense: Apache-2.0\nnist_csf:\n- RS.AN-03\n- DE.AE-02\n- RS.MA-01\nmitre_attack:\n- T1005\n- T1074\n- T1119\n- T1070\n- T1486\nmitre_f3:\n  version: '1.1'\n  tactics:\n  - initial-access\n  - stealth\n  - monetization\n  techniques:\n  - id: T1110\n    name: Brute Force\n    tactic: initial-access\n    source: attack\n  - id: T1660\n    name: Phishing\n    tactic: initial-access\n    source: attack\n  - id: T1070\n    name: Indicator Removal\n    tactic: stealth\n    source: attack\n  - id: F1018\n    name: Convert to Cryptocurrency\n    tactic: monetization\n    source: f3\n  - id: F1017.001\n    name: 'Conversion to Physical Monetary Instruments: Cash'\n    tactic: monetization\n    source: f3\n---\n\n# Investigating Ransomware Attack Artifacts\n\n## When to Use\n- Immediately after discovering ransomware encryption on systems\n- When performing forensic analysis to understand the full scope of a ransomware incident\n- For identifying the ransomware variant and determining if decryption is possible\n- When tracing the attack chain from initial access to encryption\n- For documenting evidence to support law enforcement and insurance claims\n\n## Prerequisites\n- Forensic images of affected systems (preserve before remediation)\n- Memory dumps captured before system shutdown (if available)\n- Ransom notes and encrypted file samples\n- Network traffic captures from the attack period\n- Windows Event Logs, Prefetch files, and registry hives\n- Access to ransomware identification tools (ID Ransomware, No More Ransom)\n- Isolated sandbox environment for malware analysis\n\n## Workflow\n\n### Step 1: Preserve Evidence and Identify the Ransomware Variant\n\n```bash\n# CRITICAL: Do NOT restart systems. Preserve memory first if possible.\n# Encryption keys may still be in memory.\n\n# Capture memory from running systems\n# Windows: DumpIt.exe (generates memory.raw)\n# Linux: sudo insmod lime.ko \"path=\u002Fevidence\u002Fmemory.lime format=lime\"\n\n# Collect ransom note\ncp \u002Fmnt\u002Fevidence\u002FUsers\u002F*\u002FDesktop\u002FREADME*.txt \u002Fcases\u002Fcase-2024-001\u002Fransomware\u002Fransom_notes\u002F\ncp \u002Fmnt\u002Fevidence\u002FUsers\u002F*\u002FDesktop\u002FDECRYPT*.txt \u002Fcases\u002Fcase-2024-001\u002Fransomware\u002Fransom_notes\u002F\ncp \u002Fmnt\u002Fevidence\u002FUsers\u002F*\u002FDesktop\u002FHOW_TO*.txt \u002Fcases\u002Fcase-2024-001\u002Fransomware\u002Fransom_notes\u002F\nfind \u002Fmnt\u002Fevidence\u002F -name \"*.hta\" -o -name \"*DECRYPT*\" -o -name \"*RANSOM*\" -o -name \"*README*\" \\\n   2>\u002Fdev\u002Fnull | head -20 > \u002Fcases\u002Fcase-2024-001\u002Fransomware\u002Fnote_locations.txt\n\n# Collect sample encrypted files (for identification)\nfind \u002Fmnt\u002Fevidence\u002FUsers\u002F -name \"*.encrypted\" -o -name \"*.locked\" -o -name \"*.crypted\" \\\n   -o -name \"*.crypt\" -o -name \"*.enc\" | head -10 > \u002Fcases\u002Fcase-2024-001\u002Fransomware\u002Fencrypted_samples.txt\n\n# Copy sample encrypted files\nmkdir -p \u002Fcases\u002Fcase-2024-001\u002Fransomware\u002Fsamples\u002F\nhead -5 \u002Fcases\u002Fcase-2024-001\u002Fransomware\u002Fencrypted_samples.txt | while read f; do\n    cp \"$f\" \u002Fcases\u002Fcase-2024-001\u002Fransomware\u002Fsamples\u002F\ndone\n\n# Identify ransomware variant using file extension and ransom note\npython3 \u003C\u003C 'PYEOF'\nimport os, hashlib, json\n\nransomware_indicators = {\n    '.lockbit': 'LockBit',\n    '.blackcat': 'BlackCat\u002FALPHV',\n    '.royal': 'Royal',\n    '.akira': 'Akira',\n    '.clop': 'Cl0p',\n    '.conti': 'Conti',\n    '.ryuk': 'Ryuk',\n    '.revil': 'REvil\u002FSodinokibi',\n    '.maze': 'Maze',\n    '.phobos': 'Phobos',\n    '.dharma': 'Dharma\u002FCrySIS',\n    '.stop': 'STOP\u002FDjvu',\n    '.hive': 'Hive',\n    '.blackbasta': 'Black Basta',\n    '.play': 'Play',\n}\n\n# Check encrypted file extensions\nsamples_dir = '\u002Fcases\u002Fcase-2024-001\u002Fransomware\u002Fsamples\u002F'\nfor f in os.listdir(samples_dir):\n    ext = os.path.splitext(f)[1].lower()\n    variant = ransomware_indicators.get(ext, 'Unknown')\n    sha256 = hashlib.sha256(open(os.path.join(samples_dir, f), 'rb').read()).hexdigest()\n    print(f\"File: {f}\")\n    print(f\"  Extension: {ext}\")\n    print(f\"  Suspected Variant: {variant}\")\n    print(f\"  SHA-256: {sha256}\")\n    print()\n\n# Parse ransom note for IoCs\nnote_dir = '\u002Fcases\u002Fcase-2024-001\u002Fransomware\u002Fransom_notes\u002F'\nfor note in os.listdir(note_dir):\n    with open(os.path.join(note_dir, note), 'r', errors='ignore') as f:\n        content = f.read()\n        print(f\"\\n=== Ransom Note: {note} ===\")\n        # Extract bitcoin addresses\n        import re\n        btc = re.findall(r'[13][a-km-zA-HJ-NP-Z1-9]{25,34}|bc1[a-zA-HJ-NP-Z0-9]{25,39}', content)\n        tor = re.findall(r'[a-z2-7]{56}\\.onion', content)\n        emails = re.findall(r'[a-zA-Z0-9._%+-]+@[a-zA-Z0-9.-]+\\.[a-zA-Z]{2,}', content)\n\n        if btc: print(f\"  Bitcoin addresses: {btc}\")\n        if tor: print(f\"  Tor addresses: {tor}\")\n        if emails: print(f\"  Contact emails: {emails}\")\nPYEOF\n```\n\n### Step 2: Determine the Attack Timeline\n\n```bash\n# Find the earliest encrypted file (encryption start time)\nfind \u002Fmnt\u002Fevidence\u002F -name \"*.encrypted\" -printf '%T+ %p\\n' 2>\u002Fdev\u002Fnull | sort | head -5 \\\n   > \u002Fcases\u002Fcase-2024-001\u002Fransomware\u002Fencryption_start.txt\n\n# Find the latest encrypted file (encryption end time)\nfind \u002Fmnt\u002Fevidence\u002F -name \"*.encrypted\" -printf '%T+ %p\\n' 2>\u002Fdev\u002Fnull | sort -r | head -5 \\\n   > \u002Fcases\u002Fcase-2024-001\u002Fransomware\u002Fencryption_end.txt\n\n# Analyze Prefetch for ransomware executable\nls \u002Fmnt\u002Fevidence\u002FWindows\u002FPrefetch\u002F | grep -iE \"(encrypt|ransom|lock|crypt)\" \\\n   > \u002Fcases\u002Fcase-2024-001\u002Fransomware\u002Fprefetch_hits.txt\n\n# Check Windows Event Logs for key events\npython3 \u003C\u003C 'PYEOF'\nimport json\nfrom evtx import PyEvtxParser\n\n# Security log - authentication and access events\nparser = PyEvtxParser(\"\u002Fcases\u002Fcase-2024-001\u002Fevtx\u002FSecurity.evtx\")\n\nattack_events = []\nfor record in parser.records_json():\n    data = json.loads(record['data'])\n    event_id = str(data['Event']['System']['EventID'])\n    timestamp = data['Event']['System']['TimeCreated']['#attributes']['SystemTime']\n\n    # Key events for ransomware investigation\n    if event_id in ('4624', '4625', '4648', '4672', '4697', '4698', '4688', '1102'):\n        event_data = data['Event'].get('EventData', {})\n        attack_events.append({\n            'time': timestamp,\n            'event_id': event_id,\n            'data': json.dumps(event_data, default=str)[:200]\n        })\n\n# Sort and display timeline\nattack_events.sort(key=lambda x: x['time'])\nprint(\"=== RANSOMWARE ATTACK TIMELINE ===\\n\")\nfor event in attack_events[-50:]:\n    print(f\"  [{event['time']}] EventID {event['event_id']}: {event['data'][:150]}\")\nPYEOF\n\n# Check for Volume Shadow Copy deletion (common ransomware behavior)\n# Look for vssadmin.exe or wmic shadowcopy in event logs and Prefetch\ngrep -l \"vssadmin\" \u002Fcases\u002Fcase-2024-001\u002Fevtx\u002F*.evtx 2>\u002Fdev\u002Fnull\nls \u002Fmnt\u002Fevidence\u002FWindows\u002FPrefetch\u002F | grep -i \"vssadmin\\|wmic\\|bcdedit\\|wbadmin\"\n```\n\n### Step 3: Trace Initial Access and Lateral Movement\n\n```bash\n# Check for common ransomware initial access vectors\n\n# RDP brute force\npython3 \u003C\u003C 'PYEOF'\nimport json\nfrom evtx import PyEvtxParser\nfrom collections import defaultdict\n\nparser = PyEvtxParser(\"\u002Fcases\u002Fcase-2024-001\u002Fevtx\u002FSecurity.evtx\")\n\nfailed_rdp = defaultdict(int)\nsuccessful_rdp = []\n\nfor record in parser.records_json():\n    data = json.loads(record['data'])\n    event_id = str(data['Event']['System']['EventID'])\n    event_data = data['Event'].get('EventData', {})\n    timestamp = data['Event']['System']['TimeCreated']['#attributes']['SystemTime']\n\n    if event_id == '4625':  # Failed logon\n        logon_type = str(event_data.get('LogonType', ''))\n        if logon_type == '10':  # RDP\n            source_ip = event_data.get('IpAddress', 'Unknown')\n            failed_rdp[source_ip] += 1\n\n    if event_id == '4624':  # Successful logon\n        logon_type = str(event_data.get('LogonType', ''))\n        if logon_type in ('10', '3'):  # RDP or Network\n            source_ip = event_data.get('IpAddress', 'Unknown')\n            username = event_data.get('TargetUserName', 'Unknown')\n            successful_rdp.append({'time': timestamp, 'user': username, 'ip': source_ip, 'type': logon_type})\n\nprint(\"=== FAILED RDP ATTEMPTS ===\")\nfor ip, count in sorted(failed_rdp.items(), key=lambda x: x[1], reverse=True)[:10]:\n    print(f\"  {ip}: {count} failed attempts\")\n\nprint(f\"\\n=== SUCCESSFUL NETWORK\u002FRDP LOGONS ===\")\nfor logon in successful_rdp[-20:]:\n    type_name = 'RDP' if logon['type'] == '10' else 'Network'\n    print(f\"  [{logon['time']}] {logon['user']} from {logon['ip']} ({type_name})\")\nPYEOF\n\n# Check for phishing-related artifacts\n# Browser downloads, email attachments, Office macros\nfind \u002Fmnt\u002Fevidence\u002FUsers\u002F*\u002FDownloads\u002F -name \"*.exe\" -o -name \"*.dll\" -o -name \"*.js\" \\\n   -o -name \"*.vbs\" -o -name \"*.hta\" -o -name \"*.ps1\" 2>\u002Fdev\u002Fnull \\\n   > \u002Fcases\u002Fcase-2024-001\u002Fransomware\u002Fsuspicious_downloads.txt\n\n# Check PowerShell execution\nls \u002Fmnt\u002Fevidence\u002FWindows\u002FPrefetch\u002F | grep -i powershell\n```\n\n### Step 4: Assess Encryption Scope and Recovery Options\n\n```bash\n# Count encrypted files by directory\nfind \u002Fmnt\u002Fevidence\u002F -name \"*.encrypted\" 2>\u002Fdev\u002Fnull | \\\n   awk -F\u002F '{OFS=\"\u002F\"; NF--; print}' | sort | uniq -c | sort -rn | head -20 \\\n   > \u002Fcases\u002Fcase-2024-001\u002Fransomware\u002Fencryption_scope.txt\n\n# Check if Volume Shadow Copies survived\nvssadmin list shadows 2>\u002Fdev\u002Fnull > \u002Fcases\u002Fcase-2024-001\u002Fransomware\u002Fvss_status.txt\n\n# Check for backup integrity\nfind \u002Fmnt\u002Fevidence\u002F -name \"*.bak\" -o -name \"*.backup\" 2>\u002Fdev\u002Fnull | head -20\n\n# Check No More Ransom project for available decryptors\n# https:\u002F\u002Fwww.nomoreransom.org\u002Fen\u002Fdecryption-tools.html\necho \"Check https:\u002F\u002Fwww.nomoreransom.org\u002F for decryption tools\" \\\n   > \u002Fcases\u002Fcase-2024-001\u002Fransomware\u002Fdecryption_options.txt\n\n# Attempt to recover encryption keys from memory dump\nif [ -f \u002Fcases\u002Fcase-2024-001\u002Fmemory\u002Fmemory.raw ]; then\n    # Search for AES key schedules in memory\n    vol -f \u002Fcases\u002Fcase-2024-001\u002Fmemory\u002Fmemory.raw yarascan \\\n       --yara-rules 'rule AES_Key { strings: $aes = { 63 7C 77 7B F2 6B 6F C5 30 01 67 2B FE D7 AB 76 } condition: $aes }' \\\n       > \u002Fcases\u002Fcase-2024-001\u002Fransomware\u002Faes_key_search.txt\n\n    # Search for RSA key material\n    vol -f \u002Fcases\u002Fcase-2024-001\u002Fmemory\u002Fmemory.raw yarascan \\\n       --yara-rules 'rule RSA_Key { strings: $rsa = \"RSA PRIVATE KEY\" condition: $rsa }' \\\n       > \u002Fcases\u002Fcase-2024-001\u002Fransomware\u002Frsa_key_search.txt\nfi\n```\n\n### Step 5: Document Findings and Generate Report\n\n```bash\n# Generate comprehensive ransomware investigation report\ncat \u003C\u003C 'REPORT' > \u002Fcases\u002Fcase-2024-001\u002Fransomware\u002Finvestigation_report.txt\nRANSOMWARE INCIDENT INVESTIGATION REPORT\n==========================================\nCase Number: 2024-001\nDate: $(date -u)\nAnalyst: [Examiner Name]\n\n1. INCIDENT OVERVIEW\n   - Ransomware Variant: [Identified variant]\n   - First Encryption: [Timestamp from earliest encrypted file]\n   - Last Encryption: [Timestamp from latest encrypted file]\n   - Systems Affected: [Count]\n   - Data Encrypted: [Volume estimate]\n\n2. INITIAL ACCESS VECTOR\n   - Method: [RDP brute force \u002F Phishing \u002F Exploit \u002F etc.]\n   - Entry Point: [System and IP]\n   - Timestamp: [First unauthorized access]\n   - Credentials Used: [Account names]\n\n3. ATTACK CHAIN\n   a. Initial Access: [Details]\n   b. Execution: [Ransomware binary details]\n   c. Persistence: [Services, scheduled tasks]\n   d. Privilege Escalation: [Method used]\n   e. Lateral Movement: [Systems accessed, methods]\n   f. Collection\u002FStaging: [Data staging before encryption]\n   g. Impact: [Encryption execution]\n\n4. INDICATORS OF COMPROMISE\n   - Ransomware Binary SHA-256: [Hash]\n   - C2 Servers: [IPs\u002FDomains]\n   - Bitcoin Wallet: [Address]\n   - Tor Site: [.onion address]\n   - Attacker IPs: [Source IPs]\n\n5. RECOVERY ASSESSMENT\n   - Decryptor Available: [Yes\u002FNo]\n   - Shadow Copies: [Survived\u002FDeleted]\n   - Backups: [Status and integrity]\n   - Memory Key Recovery: [Attempted\u002FResults]\n\n6. RECOMMENDATIONS\n   - [Remediation steps]\n   - [Prevention measures]\n   - [Monitoring improvements]\nREPORT\n```\n\n## Key Concepts\n\n| Concept | Description |\n|---------|-------------|\n| Ransomware variant identification | Determining the specific ransomware family from extensions, notes, and behavior |\n| Double extortion | Attack combining encryption with data theft and threatened public release |\n| Volume Shadow Copies | Windows backup mechanism often deleted by ransomware to prevent recovery |\n| Encryption scope | Assessment of which files, directories, and systems were encrypted |\n| Dwell time | Period between initial access and ransomware deployment (often days to weeks) |\n| Ransom note IoCs | Bitcoin addresses, Tor sites, and email addresses in ransom demands |\n| Key recovery | Attempting to extract encryption keys from memory before shutdown |\n| No More Ransom | Law enforcement initiative providing free decryption tools for some variants |\n\n## Tools & Systems\n\n| Tool | Purpose |\n|------|---------|\n| ID Ransomware | Online service identifying ransomware variant from samples |\n| No More Ransom | Free decryption tools from law enforcement partnerships |\n| Volatility | Memory forensics for encryption key and malware artifact recovery |\n| Chainsaw\u002FHayabusa | Windows Event Log analysis for attack timeline reconstruction |\n| PECmd | Prefetch analysis confirming ransomware executable execution |\n| YARA | Pattern matching for ransomware variant identification |\n| Any.Run\u002FJoe Sandbox | Online malware sandboxes for ransomware behavior analysis |\n| Capa | Mandiant tool identifying malware capabilities from static analysis |\n\n## Common Scenarios\n\n**Scenario 1: LockBit Attack via RDP**\nTrace initial access through RDP brute force in event logs, identify attacker IP and compromised account, follow lateral movement through network logons, find LockBit deployment via PsExec or GPO, document encryption timeline from file timestamps, check for data exfiltration before encryption.\n\n**Scenario 2: Phishing-Initiated Ransomware**\nTrace phishing email through browser history and email artifacts, identify malicious attachment execution in Prefetch, follow Cobalt Strike beacon communication in network logs, trace privilege escalation and domain compromise, document ransomware deployment across the network.\n\n**Scenario 3: Supply Chain Ransomware Attack**\nIdentify the compromised software update mechanism, trace the malicious update distribution in application logs, analyze the ransomware payload delivered via the trusted channel, assess which systems received the update, determine if the vendor was notified.\n\n**Scenario 4: Recovery from Partial Encryption**\nDetermine which systems and files were encrypted before containment, check for surviving volume shadow copies, verify backup integrity and restoration capability, attempt memory-based key recovery, contact law enforcement for potential decryptor availability.\n\n## Output Format\n\n```\nRansomware Investigation Summary:\n  Variant: LockBit 3.0\n  First Seen: 2024-01-18 02:00:00 UTC\n  Encryption Duration: 4 hours 23 minutes\n  Systems Encrypted: 45 out of 200 (containment stopped spread)\n\n  Attack Timeline:\n    2024-01-10 14:32 - RDP brute force from 203.0.113.45 (1,234 attempts)\n    2024-01-10 15:00 - Successful RDP login as admin_backup\n    2024-01-12 02:00 - Mimikatz executed (credential dump)\n    2024-01-12 02:30 - Domain Admin credentials obtained\n    2024-01-15 03:00 - Data exfiltration (45 GB to 185.x.x.x)\n    2024-01-18 02:00 - LockBit deployed via PsExec to 45 systems\n    2024-01-18 06:23 - Encryption completed on affected systems\n\n  Recovery Options:\n    Decryptor: Not available (LockBit 3.0)\n    Shadow Copies: Deleted on all systems\n    Backups: Last clean backup 2024-01-09 (9 days of data loss)\n    Memory Keys: Not recovered (systems rebooted)\n\n  IOCs:\n    Ransomware Hash: a1b2c3d4e5f6...\n    C2 IP: 185.x.x.x\n    Bitcoin: bc1q...\n    Tor: http:\u002F\u002Flockbit...onion\n```\n","# Investigating Ransomware Attack Artifacts\n\n## When to Use\n- Immediately after discovering ransomware encryption on systems\n- When performing forensic analysis to understand the full scope of a ransomware incident\n- For identifying the ransomware variant and determining if decryption is possible\n- When tracing the attack chain from initial access to encryption\n- For documenting evidence to support law enforcement and insurance claims\n\n## Prerequisites\n- Forensic images of affected systems (preserve before remediation)\n- Memory dumps captured before system shutdown (if available)\n- Ransom notes and encrypted file samples\n- Network traffic captures from the attack period\n- Windows Event Logs, Prefetch files, and registry hives\n- Access to ransomware identification tools (ID Ransomware, No More Ransom)\n- Isolated sandbox environment for malware analysis\n\n## Workflow\n\n### Step 1: Preserve Evidence and Identify the Ransomware Variant\n\n```bash\n# CRITICAL: Do NOT restart systems. Preserve memory first if possible.\n# Encryption keys may still be in memory.\n\n# Capture memory from running systems\n# Windows: DumpIt.exe (generates memory.raw)\n# Linux: sudo insmod lime.ko \"path=\u002Fevidence\u002Fmemory.lime format=lime\"\n\n# Collect ransom note\ncp \u002Fmnt\u002Fevidence\u002FUsers\u002F*\u002FDesktop\u002FREADME*.txt \u002Fcases\u002Fcase-2024-001\u002Fransomware\u002Fransom_notes\u002F\ncp \u002Fmnt\u002Fevidence\u002FUsers\u002F*\u002FDesktop\u002FDECRYPT*.txt \u002Fcases\u002Fcase-2024-001\u002Fransomware\u002Fransom_notes\u002F\ncp \u002Fmnt\u002Fevidence\u002FUsers\u002F*\u002FDesktop\u002FHOW_TO*.txt \u002Fcases\u002Fcase-2024-001\u002Fransomware\u002Fransom_notes\u002F\nfind \u002Fmnt\u002Fevidence\u002F -name \"*.hta\" -o -name \"*DECRYPT*\" -o -name \"*RANSOM*\" -o -name \"*README*\" \\\n   2>\u002Fdev\u002Fnull | head -20 > \u002Fcases\u002Fcase-2024-001\u002Fransomware\u002Fnote_locations.txt\n\n# Collect sample encrypted files (for identification)\nfind \u002Fmnt\u002Fevidence\u002FUsers\u002F -name \"*.encrypted\" -o -name \"*.locked\" -o -name \"*.crypted\" \\\n   -o -name \"*.crypt\" -o -name \"*.enc\" | head -10 > \u002Fcases\u002Fcase-2024-001\u002Fransomware\u002Fencrypted_samples.txt\n\n# Copy sample encrypted files\nmkdir -p \u002Fcases\u002Fcase-2024-001\u002Fransomware\u002Fsamples\u002F\nhead -5 \u002Fcases\u002Fcase-2024-001\u002Fransomware\u002Fencrypted_samples.txt | while read f; do\n    cp \"$f\" \u002Fcases\u002Fcase-2024-001\u002Fransomware\u002Fsamples\u002F\ndone\n\n# Identify ransomware variant using file extension and ransom note\npython3 \u003C\u003C 'PYEOF'\nimport os, hashlib, json\n\nransomware_indicators = {\n    '.lockbit': 'LockBit',\n    '.blackcat': 'BlackCat\u002FALPHV',\n    '.royal': 'Royal',\n    '.akira': 'Akira',\n    '.clop': 'Cl0p',\n    '.conti': 'Conti',\n    '.ryuk': 'Ryuk',\n    '.revil': 'REvil\u002FSodinokibi',\n    '.maze': 'Maze',\n    '.phobos': 'Phobos',\n    '.dharma': 'Dharma\u002FCrySIS',\n    '.stop': 'STOP\u002FDjvu',\n    '.hive': 'Hive',\n    '.blackbasta': 'Black Basta',\n    '.play': 'Play',\n}\n\n# Check encrypted file extensions\nsamples_dir = '\u002Fcases\u002Fcase-2024-001\u002Fransomware\u002Fsamples\u002F'\nfor f in os.listdir(samples_dir):\n    ext = os.path.splitext(f)[1].lower()\n    variant = ransomware_indicators.get(ext, 'Unknown')\n    sha256 = hashlib.sha256(open(os.path.join(samples_dir, f), 'rb').read()).hexdigest()\n    print(f\"File: {f}\")\n    print(f\"  Extension: {ext}\")\n    print(f\"  Suspected Variant: {variant}\")\n    print(f\"  SHA-256: {sha256}\")\n    print()\n\n# Parse ransom note for IoCs\nnote_dir = '\u002Fcases\u002Fcase-2024-001\u002Fransomware\u002Fransom_notes\u002F'\nfor note in os.listdir(note_dir):\n    with open(os.path.join(note_dir, note), 'r', errors='ignore') as f:\n        content = f.read()\n        print(f\"\\n=== Ransom Note: {note} ===\")\n        # Extract bitcoin addresses\n        import re\n        btc = re.findall(r'[13][a-km-zA-HJ-NP-Z1-9]{25,34}|bc1[a-zA-HJ-NP-Z0-9]{25,39}', content)\n        tor = re.findall(r'[a-z2-7]{56}\\.onion', content)\n        emails = re.findall(r'[a-zA-Z0-9._%+-]+@[a-zA-Z0-9.-]+\\.[a-zA-Z]{2,}', content)\n\n        if btc: print(f\"  Bitcoin addresses: {btc}\")\n        if tor: print(f\"  Tor addresses: {tor}\")\n        if emails: print(f\"  Contact emails: {emails}\")\nPYEOF\n```\n\n### Step 2: Determine the Attack Timeline\n\n```bash\n# Find the earliest encrypted file (encryption start time)\nfind \u002Fmnt\u002Fevidence\u002F -name \"*.encrypted\" -printf '%T+ %p\\n' 2>\u002Fdev\u002Fnull | sort | head -5 \\\n   > \u002Fcases\u002Fcase-2024-001\u002Fransomware\u002Fencryption_start.txt\n\n# Find the latest encrypted file (encryption end time)\nfind \u002Fmnt\u002Fevidence\u002F -name \"*.encrypted\" -printf '%T+ %p\\n' 2>\u002Fdev\u002Fnull | sort -r | head -5 \\\n   > \u002Fcases\u002Fcase-2024-001\u002Fransomware\u002Fencryption_end.txt\n\n# Analyze Prefetch for ransomware executable\nls \u002Fmnt\u002Fevidence\u002FWindows\u002FPrefetch\u002F | grep -iE \"(encrypt|ransom|lock|crypt)\" \\\n   > \u002Fcases\u002Fcase-2024-001\u002Fransomware\u002Fprefetch_hits.txt\n\n# Check Windows Event Logs for key events\npython3 \u003C\u003C 'PYEOF'\nimport json\nfrom evtx import PyEvtxParser\n\n# Security log - authentication and access events\nparser = PyEvtxParser(\"\u002Fcases\u002Fcase-2024-001\u002Fevtx\u002FSecurity.evtx\")\n\nattack_events = []\nfor record in parser.records_json():\n    data = json.loads(record['data'])\n    event_id = str(data['Event']['System']['EventID'])\n    timestamp = data['Event']['System']['TimeCreated']['#attributes']['SystemTime']\n\n    # Key events for ransomware investigation\n    if event_id in ('4624', '4625', '4648', '4672', '4697', '4698', '4688', '1102'):\n        event_data = data['Event'].get('EventData', {})\n        attack_events.append({\n            'time': timestamp,\n            'event_id': event_id,\n            'data': json.dumps(event_data, default=str)[:200]\n        })\n\n# Sort and display timeline\nattack_events.sort(key=lambda x: x['time'])\nprint(\"=== RANSOMWARE ATTACK TIMELINE ===\\n\")\nfor event in attack_events[-50:]:\n    print(f\"  [{event['time']}] EventID {event['event_id']}: {event['data'][:150]}\")\nPYEOF\n\n# Check for Volume Shadow Copy deletion (common ransomware behavior)\n# Look for vssadmin.exe or wmic shadowcopy in event logs and Prefetch\ngrep -l \"vssadmin\" \u002Fcases\u002Fcase-2024-001\u002Fevtx\u002F*.evtx 2>\u002Fdev\u002Fnull\nls \u002Fmnt\u002Fevidence\u002FWindows\u002FPrefetch\u002F | grep -i \"vssadmin\\|wmic\\|bcdedit\\|wbadmin\"\n```\n\n### Step 3: Trace Initial Access and Lateral Movement\n\n```bash\n# Check for common ransomware initial access vectors\n\n# RDP brute force\npython3 \u003C\u003C 'PYEOF'\nimport json\nfrom evtx import PyEvtxParser\nfrom collections import defaultdict\n\nparser = PyEvtxParser(\"\u002Fcases\u002Fcase-2024-001\u002Fevtx\u002FSecurity.evtx\")\n\nfailed_rdp = defaultdict(int)\nsuccessful_rdp = []\n\nfor record in parser.records_json():\n    data = json.loads(record['data'])\n    event_id = str(data['Event']['System']['EventID'])\n    event_data = data['Event'].get('EventData', {})\n    timestamp = data['Event']['System']['TimeCreated']['#attributes']['SystemTime']\n\n    if event_id == '4625':  # Failed logon\n        logon_type = str(event_data.get('LogonType', ''))\n        if logon_type == '10':  # RDP\n            source_ip = event_data.get('IpAddress', 'Unknown')\n            failed_rdp[source_ip] += 1\n\n    if event_id == '4624':  # Successful logon\n        logon_type = str(event_data.get('LogonType', ''))\n        if logon_type in ('10', '3'):  # RDP or Network\n            source_ip = event_data.get('IpAddress', 'Unknown')\n            username = event_data.get('TargetUserName', 'Unknown')\n            successful_rdp.append({'time': timestamp, 'user': username, 'ip': source_ip, 'type': logon_type})\n\nprint(\"=== FAILED RDP ATTEMPTS ===\")\nfor ip, count in sorted(failed_rdp.items(), key=lambda x: x[1], reverse=True)[:10]:\n    print(f\"  {ip}: {count} failed attempts\")\n\nprint(f\"\\n=== SUCCESSFUL NETWORK\u002FRDP LOGONS ===\")\nfor logon in successful_rdp[-20:]:\n    type_name = 'RDP' if logon['type'] == '10' else 'Network'\n    print(f\"  [{logon['time']}] {logon['user']} from {logon['ip']} ({type_name})\")\nPYEOF\n\n# Check for phishing-related artifacts\n# Browser downloads, email attachments, Office macros\nfind \u002Fmnt\u002Fevidence\u002FUsers\u002F*\u002FDownloads\u002F -name \"*.exe\" -o -name \"*.dll\" -o -name \"*.js\" \\\n   -o -name \"*.vbs\" -o -name \"*.hta\" -o -name \"*.ps1\" 2>\u002Fdev\u002Fnull \\\n   > \u002Fcases\u002Fcase-2024-001\u002Fransomware\u002Fsuspicious_downloads.txt\n\n# Check PowerShell execution\nls \u002Fmnt\u002Fevidence\u002FWindows\u002FPrefetch\u002F | grep -i powershell\n```\n\n### Step 4: Assess Encryption Scope and Recovery Options\n\n```bash\n# Count encrypted files by directory\nfind \u002Fmnt\u002Fevidence\u002F -name \"*.encrypted\" 2>\u002Fdev\u002Fnull | \\\n   awk -F\u002F '{OFS=\"\u002F\"; NF--; print}' | sort | uniq -c | sort -rn | head -20 \\\n   > \u002Fcases\u002Fcase-2024-001\u002Fransomware\u002Fencryption_scope.txt\n\n# Check if Volume Shadow Copies survived\nvssadmin list shadows 2>\u002Fdev\u002Fnull > \u002Fcases\u002Fcase-2024-001\u002Fransomware\u002Fvss_status.txt\n\n# Check for backup integrity\nfind \u002Fmnt\u002Fevidence\u002F -name \"*.bak\" -o -name \"*.backup\" 2>\u002Fdev\u002Fnull | head -20\n\n# Check No More Ransom project for available decryptors\n# https:\u002F\u002Fwww.nomoreransom.org\u002Fen\u002Fdecryption-tools.html\necho \"Check https:\u002F\u002Fwww.nomoreransom.org\u002F for decryption tools\" \\\n   > \u002Fcases\u002Fcase-2024-001\u002Fransomware\u002Fdecryption_options.txt\n\n# Attempt to recover encryption keys from memory dump\nif [ -f \u002Fcases\u002Fcase-2024-001\u002Fmemory\u002Fmemory.raw ]; then\n    # Search for AES key schedules in memory\n    vol -f \u002Fcases\u002Fcase-2024-001\u002Fmemory\u002Fmemory.raw yarascan \\\n       --yara-rules 'rule AES_Key { strings: $aes = { 63 7C 77 7B F2 6B 6F C5 30 01 67 2B FE D7 AB 76 } condition: $aes }' \\\n       > \u002Fcases\u002Fcase-2024-001\u002Fransomware\u002Faes_key_search.txt\n\n    # Search for RSA key material\n    vol -f \u002Fcases\u002Fcase-2024-001\u002Fmemory\u002Fmemory.raw yarascan \\\n       --yara-rules 'rule RSA_Key { strings: $rsa = \"RSA PRIVATE KEY\" condition: $rsa }' \\\n       > \u002Fcases\u002Fcase-2024-001\u002Fransomware\u002Frsa_key_search.txt\nfi\n```\n\n### Step 5: Document Findings and Generate Report\n\n```bash\n# Generate comprehensive ransomware investigation report\ncat \u003C\u003C 'REPORT' > \u002Fcases\u002Fcase-2024-001\u002Fransomware\u002Finvestigation_report.txt\nRANSOMWARE INCIDENT INVESTIGATION REPORT\n==========================================\nCase Number: 2024-001\nDate: $(date -u)\nAnalyst: [Examiner Name]\n\n1. INCIDENT OVERVIEW\n   - Ransomware Variant: [Identified variant]\n   - First Encryption: [Timestamp from earliest encrypted file]\n   - Last Encryption: [Timestamp from latest encrypted file]\n   - Systems Affected: [Count]\n   - Data Encrypted: [Volume estimate]\n\n2. INITIAL ACCESS VECTOR\n   - Method: [RDP brute force \u002F Phishing \u002F Exploit \u002F etc.]\n   - Entry Point: [System and IP]\n   - Timestamp: [First unauthorized access]\n   - Credentials Used: [Account names]\n\n3. ATTACK CHAIN\n   a. Initial Access: [Details]\n   b. Execution: [Ransomware binary details]\n   c. Persistence: [Services, scheduled tasks]\n   d. Privilege Escalation: [Method used]\n   e. Lateral Movement: [Systems accessed, methods]\n   f. Collection\u002FStaging: [Data staging before encryption]\n   g. Impact: [Encryption execution]\n\n4. INDICATORS OF COMPROMISE\n   - Ransomware Binary SHA-256: [Hash]\n   - C2 Servers: [IPs\u002FDomains]\n   - Bitcoin Wallet: [Address]\n   - Tor Site: [.onion address]\n   - Attacker IPs: [Source IPs]\n\n5. RECOVERY ASSESSMENT\n   - Decryptor Available: [Yes\u002FNo]\n   - Shadow Copies: [Survived\u002FDeleted]\n   - Backups: [Status and integrity]\n   - Memory Key Recovery: [Attempted\u002FResults]\n\n6. RECOMMENDATIONS\n   - [Remediation steps]\n   - [Prevention measures]\n   - [Monitoring improvements]\nREPORT\n```\n\n## Key Concepts\n\n| Concept | Description |\n|---------|-------------|\n| Ransomware variant identification | Determining the specific ransomware family from extensions, notes, and behavior |\n| Double extortion | Attack combining encryption with data theft and threatened public release |\n| Volume Shadow Copies | Windows backup mechanism often deleted by ransomware to prevent recovery |\n| Encryption scope | Assessment of which files, directories, and systems were encrypted |\n| Dwell time | Period between initial access and ransomware deployment (often days to weeks) |\n| Ransom note IoCs | Bitcoin addresses, Tor sites, and email addresses in ransom demands |\n| Key recovery | Attempting to extract encryption keys from memory before shutdown |\n| No More Ransom | Law enforcement initiative providing free decryption tools for some variants |\n\n## Tools & Systems\n\n| Tool | Purpose |\n|------|---------|\n| ID Ransomware | Online service identifying ransomware variant from samples |\n| No More Ransom | Free decryption tools from law enforcement partnerships |\n| Volatility | Memory forensics for encryption key and malware artifact recovery |\n| Chainsaw\u002FHayabusa | Windows Event Log analysis for attack timeline reconstruction |\n| PECmd | Prefetch analysis confirming ransomware executable execution |\n| YARA | Pattern matching for ransomware variant identification |\n| Any.Run\u002FJoe Sandbox | Online malware sandboxes for ransomware behavior analysis |\n| Capa | Mandiant tool identifying malware capabilities from static analysis |\n\n## Common Scenarios\n\n**Scenario 1: LockBit Attack via RDP**\nTrace initial access through RDP brute force in event logs, identify attacker IP and compromised account, follow lateral movement through network logons, find LockBit deployment via PsExec or GPO, document encryption timeline from file timestamps, check for data exfiltration before encryption.\n\n**Scenario 2: Phishing-Initiated Ransomware**\nTrace phishing email through browser history and email artifacts, identify malicious attachment execution in Prefetch, follow Cobalt Strike beacon communication in network logs, trace privilege escalation and domain compromise, document ransomware deployment across the network.\n\n**Scenario 3: Supply Chain Ransomware Attack**\nIdentify the compromised software update mechanism, trace the malicious update distribution in application logs, analyze the ransomware payload delivered via the trusted channel, assess which systems received the update, determine if the vendor was notified.\n\n**Scenario 4: Recovery from Partial Encryption**\nDetermine which systems and files were encrypted before containment, check for surviving volume shadow copies, verify backup integrity and restoration capability, attempt memory-based key recovery, contact law enforcement for potential decryptor availability.\n\n## Output Format\n\n```\nRansomware Investigation Summary:\n  Variant: LockBit 3.0\n  First Seen: 2024-01-18 02:00:00 UTC\n  Encryption Duration: 4 hours 23 minutes\n  Systems Encrypted: 45 out of 200 (containment stopped spread)\n\n  Attack Timeline:\n    2024-01-10 14:32 - RDP brute force from 203.0.113.45 (1,234 attempts)\n    2024-01-10 15:00 - Successful RDP login as admin_backup\n    2024-01-12 02:00 - Mimikatz executed (credential dump)\n    2024-01-12 02:30 - Domain Admin credentials obtained\n    2024-01-15 03:00 - Data exfiltration (45 GB to 185.x.x.x)\n    2024-01-18 02:00 - LockBit deployed via PsExec to 45 systems\n    2024-01-18 06:23 - Encryption completed on affected systems\n\n  Recovery Options:\n    Decryptor: Not available (LockBit 3.0)\n    Shadow Copies: Deleted on all systems\n    Backups: Last clean backup 2024-01-09 (9 days of data loss)\n    Memory Keys: Not recovered (systems rebooted)\n\n  IOCs:\n    Ransomware Hash: a1b2c3d4e5f6...\n    C2 IP: 185.x.x.x\n    Bitcoin: bc1q...\n    Tor: http:\u002F\u002Flockbit...onion\n```\n",{"name":5,"tags":24,"author":31,"domain":32,"license":14,"version":33,"mitre_f3":34,"nist_csf":58,"subdomain":62,"description":7,"mitre_attack":63},[25,26,27,28,29,30],"forensics","ransomware","malware-analysis","incident-response","encryption-recovery","evidence-collection","mahipal","cybersecurity","1.0",{"tactics":35,"version":39,"techniques":40},[36,37,38],"initial-access","stealth","monetization","1.1",[41,45,48,51,55],{"id":42,"name":43,"source":44,"tactic":36},"T1110","Brute Force","attack",{"id":46,"name":47,"source":44,"tactic":36},"T1660","Phishing",{"id":49,"name":50,"source":44,"tactic":37},"T1070","Indicator Removal",{"id":52,"name":53,"source":54,"tactic":38},"F1018","Convert to Cryptocurrency","f3",{"id":56,"name":57,"source":54,"tactic":38},"F1017.001","Conversion to Physical Monetary Instruments: Cash",[59,60,61],"RS.AN-03","DE.AE-02","RS.MA-01","digital-forensics",[64,65,66,49,67],"T1005","T1074","T1119","T1486","main","1eb986d0b0ecc180291597e08eb5a58288843536","skills\u002Fcurated_premium_skills\u002FAnthropic-Cybersecurity-Skills\u002Fskills\u002Finvestigating-ransomware-attack-artifacts","https:\u002F\u002Fgithub.com\u002Fvikasvardhanv\u002Fjerry_skills","https:\u002F\u002Fgithub.com\u002Fvikasvardhanv","2026-08-25 13:16:33",{"source":8,"skillName":5,"commands":75,"prompt":85,"zipAvailable":86},[76,79,82],{"tool":77,"command":78},"npx","npx skills add vikasvardhanv\u002Fjerry_skills --skill investigating-ransomware-attack-artifacts",{"tool":80,"command":81},"bunx","bunx skills add vikasvardhanv\u002Fjerry_skills --skill investigating-ransomware-attack-artifacts",{"tool":83,"command":84},"pnpm","pnpm dlx skills add vikasvardhanv\u002Fjerry_skills --skill investigating-ransomware-attack-artifacts","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fvikasvardhanv\u002Fjerry_skills\u002Fblob\u002Fmain\u002Fskills\u002Fcurated_premium_skills\u002FAnthropic-Cybersecurity-Skills\u002Fskills\u002Finvestigating-ransomware-attack-artifacts\u002FSKILL.md",true,[88,92,98],{"path":89,"resourceType":89,"resourceTypeDesc":90,"sizeBytes":91,"sourceHtmlUrl":15},"LICENSE","许可证",11255,{"path":93,"resourceType":94,"resourceTypeDesc":95,"sizeBytes":96,"sourceHtmlUrl":97},"references\u002Fapi-reference.md","REFERENCE","参考文档",2185,"https:\u002F\u002Fgithub.com\u002Fvikasvardhanv\u002Fjerry_skills\u002Fblob\u002Fmain\u002Fskills\u002Fcurated_premium_skills\u002FAnthropic-Cybersecurity-Skills\u002Fskills\u002Finvestigating-ransomware-attack-artifacts\u002Freferences\u002Fapi-reference.md",{"path":99,"resourceType":100,"resourceTypeDesc":101,"sizeBytes":102,"sourceHtmlUrl":103},"scripts\u002Fagent.py","SCRIPT","脚本",7924,"https:\u002F\u002Fgithub.com\u002Fvikasvardhanv\u002Fjerry_skills\u002Fblob\u002Fmain\u002Fskills\u002Fcurated_premium_skills\u002FAnthropic-Cybersecurity-Skills\u002Fskills\u002Finvestigating-ransomware-attack-artifacts\u002Fscripts\u002Fagent.py",[105,113,120,127,134,141],{"skillNo":106,"name":107,"nameZh":6,"description":108,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":109,"licenseFileUrl":6,"sourceHtmlUrl":110,"categories":111,"keywords":112,"publishedAt":19},"01M7BESR1CJ3H5SP9XM8KYJZ9W","syllabus","Generates a curated supplementary reading list from any course syllabus using Consensus academic search. Grill-me intake (syllabus input format + course audience + year range) plus a grouping forcing-options checkpoint before any search runs — so the reading list matches the course's level and recency need. Parses the syllabus to extract topics and learning outcomes, searches Consensus for recent peer-reviewed papers per topic, and produces a professionally formatted .docx with clickable Consensus links, plain-language summaries calibrated to audience level, and Bloom-higher-order discussion questions tied to course learning goals. Use when the user uploads a syllabus, course outline, or curriculum document and wants supplementary readings (e.g., 'create a reading list from this syllabus', 'find recent papers for my course') — even casual mentions with a syllabus attached should trigger this skill.","MIT","https:\u002F\u002Fgithub.com\u002Fvikasvardhanv\u002Fjerry_skills\u002Fblob\u002Fmain\u002Fskills\u002Fresearch\u002Fsyllabus\u002Fskills\u002Fsyllabus\u002FSKILL.md",[],[],{"skillNo":114,"name":115,"nameZh":6,"description":116,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":109,"licenseFileUrl":6,"sourceHtmlUrl":117,"categories":118,"keywords":119,"publishedAt":19},"01M7BES1YA6R97W7QPMFFM1PED","pulse","Multi-source recency research skill that takes the pulse of any topic across Reddit, Hacker News, the open web, and optionally X\u002FTwitter within a configurable recent window (default 30 days). Forcing intake clarifies topic specificity, angle (trend\u002Fsentiment\u002Fproblems\u002Fopportunities\u002Fcomparison), time window, and platform scope before searching. Returns a synthesized briefing with citations, engagement metrics, and cross-platform pattern analysis. Use when the user requests multi-source recency intelligence on a topic (e.g., 'pulse on [topic]', 'what's happening with [topic]', 'what are people saying about [topic]', 'current conversation about [topic]', 'take the pulse of [topic]', 'trending: [topic]', 'find me info on [topic]'), and for competitor research, trend discovery, tool comparisons, and audience sentiment analysis.","https:\u002F\u002Fgithub.com\u002Fvikasvardhanv\u002Fjerry_skills\u002Fblob\u002Fmain\u002Fskills\u002Fresearch\u002Fpulse\u002Fskills\u002Fpulse\u002FSKILL.md",[],[],{"skillNo":121,"name":122,"nameZh":6,"description":123,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":109,"licenseFileUrl":6,"sourceHtmlUrl":124,"categories":125,"keywords":126,"publishedAt":19},"01M7BERNHYGY035AR00VRT03KE","patent","Patent prior-art and landscape intelligence skill — not generic patent help. Commits to one of five sub-use-cases via forcing intake (novelty search \u002F freedom-to-operate \u002F competitive landscape \u002F acquisition diligence \u002F litigation prior-art) before any search runs. Searches Google Patents, Espacenet, USPTO, and optionally Lens.org for citation-graph signals. Output is an editable Word document (.docx) with verdict, ranked closest art (claim-text extracted), CPC-class-aware landscape, family-resolved hits, geographic coverage, FTO flags where applicable, strategy recommendations, and full audit log. Use when the user asks for patent searching or analysis (e.g., 'prior art search for [invention]', 'freedom to operate analysis for [product]'). Produces search signal, not legal advice — always recommends consulting a patent attorney before filing or licensing decisions. Trademark, copyright, and trade-secret questions are out of scope.","https:\u002F\u002Fgithub.com\u002Fvikasvardhanv\u002Fjerry_skills\u002Fblob\u002Fmain\u002Fskills\u002Fresearch\u002Fpatent\u002Fskills\u002Fpatent\u002FSKILL.md",[],[],{"skillNo":128,"name":129,"nameZh":6,"description":130,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":109,"licenseFileUrl":6,"sourceHtmlUrl":131,"categories":132,"keywords":133,"publishedAt":19},"01M7BERCK1EAKTWW7R436WAR0J","notebooklm","Browser automation skill for controlling Google's NotebookLM. Use when the user wants anything done in NotebookLM (e.g., 'open NotebookLM', 'check my [name] notebook', 'ask my notebook about X', 'add [source] to NotebookLM', 'generate a Video Overview from my notebook', 'use NotebookLM Studio'). Handles reading and querying notebooks, adding sources (URLs, text, files, YouTube links, synthesized content), generating Studio outputs (Audio\u002FVideo Overviews, Mind Maps, Reports incl. Briefing Doc\u002FStudy Guide\u002FFAQ, Flashcards, Quiz, slide decks, infographics — discover the exact set from the live Studio panel; the UI evolves fast), and creating new notebooks. Requires browser automation environment — fails gracefully when unavailable.","https:\u002F\u002Fgithub.com\u002Fvikasvardhanv\u002Fjerry_skills\u002Fblob\u002Fmain\u002Fskills\u002Fresearch\u002Fnotebooklm\u002Fskills\u002Fnotebooklm\u002FSKILL.md",[],[],{"skillNo":135,"name":136,"nameZh":6,"description":137,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":109,"licenseFileUrl":6,"sourceHtmlUrl":138,"categories":139,"keywords":140,"publishedAt":19},"01M7BEQZAZAQRTXFJRY7RHV3TY","litreview","Academic literature orientation skill that searches papers via free keyless APIs (PubMed E-utilities + OpenAlex) by default — with the Consensus MCP as an optional enhancement lane when connected — builds a strategic search plan using PICO (default) or SPIDER \u002F Decomposition \u002F hybrid as fallbacks, and synthesizes findings into a formatted Word (.docx) research guide. Grill-me intake (research question specificity + framework hint + tentative depth) before the recon search; a second forcing checkpoint after Phase 2 confirms framework + sub-areas + depth before searches consume budget. Configurable depth (5\u002F10\u002F20 queries) controls coverage vs. speed. Output is a 'launching pad' — an orientation guide that lets a researcher dive in confidently, not a finished review. Use when the user starts literature-oriented research (e.g., 'litreview on [topic]', 'literature review on [topic]', 'I'm starting a literature review on X', 'I'm writing a paper on X', 'help me research X', 'I'm doing research on X', 'can you help me research X'). Do NOT use for single one-off paper searches wanting a quick list — that's a plain PubMed\u002FOpenAlex (or Consensus) query.","https:\u002F\u002Fgithub.com\u002Fvikasvardhanv\u002Fjerry_skills\u002Fblob\u002Fmain\u002Fskills\u002Fresearch\u002Flitreview\u002Fskills\u002Flitreview\u002FSKILL.md",[],[],{"skillNo":142,"name":143,"nameZh":6,"description":144,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":109,"licenseFileUrl":6,"sourceHtmlUrl":145,"categories":146,"keywords":147,"publishedAt":19},"01M7BEQKJ45K31QK5VRAQSVJCJ","grants","NIH grant research skill for clinical researchers. Grill-me intake (research idea + career stage + preliminary data + environment + submission posture + known institute targets) locks down the funding strategy before any search runs. Runs a 5-facet Consensus positioning analysis (with draft Significance\u002FInnovation language), maps the research to the right NIH institutes and study sections via RePORTER, finds NOSIs and funded overlap, and produces an editable Word document (.docx) with budget\u002Fscope-aware mechanism recommendations, submission timelines, and a mandatory program officer recommendation. Use when the user asks about research funding or makes any grant-related request (e.g., 'grants for [topic]', 'find grants for my research idea', 'what grants match my research', 'help me find NIH funding', 'grant opportunities for my research'). NIH-only scope — non-NIH funders (PCORI, DOD CDMRP, VA, foundations) are out of scope and flagged at intake.","https:\u002F\u002Fgithub.com\u002Fvikasvardhanv\u002Fjerry_skills\u002Fblob\u002Fmain\u002Fskills\u002Fresearch\u002Fgrants\u002Fskills\u002Fgrants\u002FSKILL.md",[],[]]