[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6AFRVYZXC55BRT54TRJRTA5":3,"skill-same:01M6AFRVYZXC55BRT54TRJRTA5":111},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":23,"publishedAt":44,"linkOnly":45,"markdownContent":46,"markdownBody":47,"frontMatter":48,"refName":70,"commitSha":71,"skillDirectory":72,"forksCount":73,"repositoryHtmlUrl":74,"repositoryHomepageUrl":75,"ownerHtmlUrl":76,"ownerBlogUrl":77,"ownerDescription":78,"updatedAt":79,"install":80,"resources":93},"01M6AFRVYZXC55BRT54TRJRTA5","performing-dynamic-analysis-with-any-run",null,"Perform interactive dynamic malware analysis using the ANY.RUN cloud sandbox to detonate samples, observe real-time execution behavior, interact with malware prompts such as dialogs and CAPTCHAs, and capture process trees, network traffic, and system changes. Use when a suspicious file or URL needs live, interactive behavioral detonation in a cloud sandbox rather than static analysis alone.","mukul975\u002FAnthropic-Cybersecurity-Skills","mukul975","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F42860185?v=4","01M6ADEQR8T5M4EEG6C67BQCWF","Mahipal","01M6ADJPMYWG1E5GM1FWBE3128",35990,"Apache-2.0","https:\u002F\u002Fgithub.com\u002Fmukul975\u002FAnthropic-Cybersecurity-Skills\u002Fblob\u002Fmain\u002Fskills\u002Fperforming-dynamic-analysis-with-any-run\u002FSKILL.md",[18],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000023","Skill与智能体开发","SCENARIO","使用场景",[24,25,26,27,28,29,30,31,32,33,34,35,36,37,38,39,40,41,42,43],"performing dynamic analysis with any run","run","analysis","malware","interactive-analysis","ANY.RUN","real-time","execution","network","dynamic-analysis","malware-analysis","suspicious","malware analysis","cloud","file","protocol","validation","cybersecurity","static analysis","sandbox","2026-11-10 10:12:30",false,"---\nname: performing-dynamic-analysis-with-any-run\ndescription: 'Perform interactive dynamic malware analysis using the ANY.RUN cloud sandbox\n  to detonate samples, observe real-time execution behavior, interact with malware prompts\n  such as dialogs and CAPTCHAs, and capture process trees, network traffic, and system\n  changes. Use when a suspicious file or URL needs live, interactive behavioral detonation\n  in a cloud sandbox rather than static analysis alone.\n\n  '\ndomain: cybersecurity\nsubdomain: malware-analysis\ntags:\n- malware\n- dynamic-analysis\n- sandbox\n- ANY.RUN\n- interactive-analysis\nversion: 1.0.0\nauthor: mahipal\nlicense: Apache-2.0\nd3fend_techniques:\n- File Metadata Consistency Validation\n- Application Protocol Command Analysis\n- Identifier Analysis\n- Content Format Conversion\n- Message Analysis\nnist_csf:\n- DE.AE-02\n- RS.AN-03\n- ID.RA-01\n- DE.CM-01\nmitre_attack:\n- T1027\n- T1055\n- T1140\n- T1497\n- T1591\n---\n\n# Performing Dynamic Analysis with ANY.RUN\n\n## When to Use\n\n- Interactive malware analysis is needed where the analyst must click dialogs, enter credentials, or navigate installer screens\n- Rapid cloud-based sandbox analysis without maintaining local sandbox infrastructure\n- Malware requires user interaction to proceed past anti-sandbox checks (document macros requiring \"Enable Content\")\n- Sharing analysis results with team members via public or private task URLs\n- Comparing behavior across different OS versions (Windows 7, 10, 11) available in ANY.RUN\n\n**Do not use** for highly sensitive samples that cannot be uploaded to cloud services; use an on-premises sandbox like Cuckoo instead.\n\n## Prerequisites\n\n- ANY.RUN account (free community tier or paid subscription at https:\u002F\u002Fany.run)\n- Modern web browser with WebSocket support for interactive session streaming\n- Sample file ready for upload (max 100 MB for free tier, 256 MB for paid)\n- Understanding of the sample type to select appropriate execution environment\n- VPN or secure network for accessing ANY.RUN portal during analysis sessions\n\n## Workflow\n\n### Step 1: Configure Analysis Environment\n\nSet up the ANY.RUN task with appropriate parameters:\n\n```\nANY.RUN Task Configuration:\n━━━━━━━━━━━━━━━━━━━━━━━━━━\nOS Selection:        Windows 10 x64 (recommended default)\n                     Windows 7 x64 (for legacy malware)\n                     Windows 11 x64 (for modern samples)\nExecution Time:      60 seconds (default) \u002F 120-300 for slow-acting malware\nNetwork:             Connected (captures real C2 traffic)\n                     Residential Proxy (bypasses geo-blocking)\nPrivacy:             Public (free tier) \u002F Private (paid - not indexed)\nMITM Proxy:          Enable for HTTPS traffic decryption\nFake Net:            Enable to simulate internet services if sample checks connectivity\n```\n\n**API-based submission (paid tier):**\n```bash\n# Submit file via ANY.RUN API\ncurl -X POST \"https:\u002F\u002Fapi.any.run\u002Fv1\u002Fanalysis\" \\\n  -H \"Authorization: API-Key $ANYRUN_API_KEY\" \\\n  -F \"file=@suspect.exe\" \\\n  -F \"env_os=windows\" \\\n  -F \"env_version=10\" \\\n  -F \"env_bitness=64\" \\\n  -F \"opt_timeout=120\" \\\n  -F \"opt_network_connect=true\" \\\n  -F \"opt_privacy_type=bylink\"\n\n# Check task status\ncurl \"https:\u002F\u002Fapi.any.run\u002Fv1\u002Fanalysis\u002F$TASK_ID\" \\\n  -H \"Authorization: API-Key $ANYRUN_API_KEY\" | jq '.data.status'\n```\n\n### Step 2: Interact with Malware During Execution\n\nUse the interactive session to trigger malware behavior:\n\n```\nInteractive Actions During Analysis:\n━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━\n1. Document Macros:   Click \"Enable Content\" \u002F \"Enable Editing\" when prompted\n2. Installer Screens: Click through installation dialogs\n3. UAC Prompts:       Click \"Yes\" to allow elevation (observe privilege escalation)\n4. Credential Harvests: Enter fake credentials to observe phishing behavior\n5. Browser Redirects:  Navigate to URLs if malware opens browser windows\n6. File Dialogs:       Select target files if malware presents file picker\n7. Timeout Extension:  Extend analysis time if malware has delayed execution\n```\n\n### Step 3: Analyze Process Tree\n\nReview the complete process execution chain:\n\n```\nProcess Tree Analysis Points:\n━━━━━━━━━━━━━━━━━━━━━━━━━━━\nParent-Child Relationships:\n  - WINWORD.EXE -> cmd.exe -> powershell.exe (macro execution chain)\n  - explorer.exe -> suspect.exe -> svchost.exe (process injection)\n\nProcess Events to Note:\n  - Process creation with suspicious command-line arguments\n  - PowerShell with encoded commands (-enc \u002F -encodedcommand)\n  - cmd.exe executing script files (.bat, .vbs, .js)\n  - Legitimate processes spawned from unusual parents\n  - Process termination (self-deletion behavior)\n```\n\n### Step 4: Review Network Activity\n\nExamine DNS, HTTP\u002FHTTPS, and TCP\u002FUDP connections:\n\n```\nANY.RUN Network Panel Analysis:\n━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━\nDNS Requests:\n  - Domain resolutions with threat intelligence tags\n  - Fast-flux or DGA domain patterns\n  - DNS over HTTPS (DoH) detection\n\nHTTP\u002FHTTPS Traffic (with MITM enabled):\n  - Full request\u002Fresponse bodies for HTTP\n  - Decrypted HTTPS traffic showing C2 commands\n  - Downloaded payloads and their content types\n  - POST data containing exfiltrated information\n\nConnection Map:\n  - Geographic visualization of C2 server locations\n  - Connection timeline showing beacon patterns\n  - Suricata alerts triggered on network traffic\n```\n\n### Step 5: Examine IOCs and Threat Intelligence\n\nExtract indicators and map to known threats:\n\n```\nANY.RUN IOC Categories:\n━━━━━━━━━━━━━━━━━━━━━━\nFiles:       Dropped files with hashes, YARA matches, VirusTotal results\nNetwork:     IPs, domains, URLs contacted during execution\nRegistry:    Keys created\u002Fmodified for persistence\nProcesses:   Suspicious process names and command lines\nMutex:       Named mutexes created (used for single-instance checking)\nSignatures:  Suricata rules triggered, behavioral signatures matched\n\nMITRE ATT&CK Mapping:\n  - ANY.RUN automatically maps observed behaviors to ATT&CK techniques\n  - Review the ATT&CK matrix tab for technique coverage\n  - Export ATT&CK Navigator layer for reporting\n```\n\n### Step 6: Export Analysis Results\n\nDownload comprehensive reports and artifacts:\n\n```bash\n# Download report via API\ncurl \"https:\u002F\u002Fapi.any.run\u002Fv1\u002Fanalysis\u002F$TASK_ID\u002Freport\" \\\n  -H \"Authorization: API-Key $ANYRUN_API_KEY\" \\\n  -o report.json\n\n# Download PCAP\ncurl \"https:\u002F\u002Fapi.any.run\u002Fv1\u002Fanalysis\u002F$TASK_ID\u002Fpcap\" \\\n  -H \"Authorization: API-Key $ANYRUN_API_KEY\" \\\n  -o capture.pcap\n\n# Download dropped files\ncurl \"https:\u002F\u002Fapi.any.run\u002Fv1\u002Fanalysis\u002F$TASK_ID\u002Ffiles\" \\\n  -H \"Authorization: API-Key $ANYRUN_API_KEY\" \\\n  -o dropped_files.zip\n\n# Available exports from ANY.RUN web interface:\n# - HTML Report (shareable standalone page)\n# - PCAP file (network traffic capture)\n# - Process dump (memory dumps of processes)\n# - Dropped files (all files created during execution)\n# - MITRE ATT&CK Navigator JSON\n# - IOC export (STIX\u002FJSON\u002FCSV format)\n```\n\n## Key Concepts\n\n| Term | Definition |\n|------|------------|\n| **Interactive Sandbox** | Analysis environment allowing real-time analyst interaction with the executing sample, enabling triggering of user-dependent behaviors |\n| **MITM Proxy** | Man-in-the-middle TLS interception in ANY.RUN that decrypts HTTPS traffic for visibility into encrypted C2 communications |\n| **Residential Proxy** | ANY.RUN feature routing malware traffic through residential IP addresses to bypass geo-IP and datacenter-IP evasion checks |\n| **Suricata Alerts** | Network IDS signatures triggered during execution, providing immediate identification of known malicious traffic patterns |\n| **Process Tree** | Hierarchical visualization of parent-child process relationships showing the complete execution chain from initial sample to final payloads |\n| **Behavioral Tags** | ANY.RUN classification labels automatically applied based on observed behavior (e.g., \"trojan\", \"stealer\", \"ransomware\") |\n\n## Tools & Systems\n\n- **ANY.RUN**: Cloud-based interactive malware sandbox providing real-time execution monitoring, process trees, network capture, and MITRE ATT&CK mapping\n- **ANY.RUN API**: REST API for programmatic sample submission, status checking, and report\u002Fartifact retrieval\n- **Suricata**: Integrated network IDS within ANY.RUN providing signature-based detection of malicious network traffic\n- **MITRE ATT&CK Navigator**: Framework integration mapping observed malware behaviors to adversary techniques and tactics\n- **VirusTotal Integration**: Automatic hash lookup of sample and dropped files against VirusTotal detection results\n\n## Common Scenarios\n\n### Scenario: Analyzing a Macro-Enabled Document Requiring User Interaction\n\n**Context**: Phishing email contains a .docm file that requires clicking \"Enable Content\" to trigger the macro payload. Traditional non-interactive sandboxes fail to trigger the malicious behavior.\n\n**Approach**:\n1. Upload .docm to ANY.RUN with Windows 10 environment and Microsoft Office installed\n2. When Word opens and displays the security banner, click \"Enable Content\" interactively\n3. Observe the macro execution in the process tree (Word -> cmd.exe -> powershell.exe)\n4. Monitor network panel for PowerShell downloading second-stage payload\n5. If a UAC prompt appears, click \"Yes\" to allow the payload to observe full behavior chain\n6. Review Suricata alerts for known malware signatures on the downloaded payload\n7. Export IOCs (download URLs, dropped file hashes, C2 domains) for blocking\n\n**Pitfalls**:\n- Forgetting to enable MITM proxy, resulting in encrypted HTTPS traffic without visibility\n- Using too short an execution timeout for malware with delayed execution or sleep timers\n- Uploading to public analysis when the sample contains sensitive organizational data\n- Not clicking through all prompts; some malware requires multiple user interactions to fully execute\n\n## Output Format\n\n```\nANY.RUN ANALYSIS REPORT\n=========================\nTask URL:         https:\u002F\u002Fapp.any.run\u002Ftasks\u002F\u003Ctask_id>\nSample:           invoice_q3.docm\nSHA-256:          e3b0c44298fc1c149afbf4c8996fb924...\nVerdict:          MALICIOUS (Score: 95\u002F100)\nFamily:           Emotet\nTags:             [trojan, banker, spam, macro]\n\nPROCESS TREE\nWINWORD.EXE (PID: 2184)\n  └── cmd.exe (PID: 3456) \"\u002Fc powershell -enc JABXAG...\"\n      └── powershell.exe (PID: 4012)\n          └── rundll32.exe (PID: 4568) \"C:\\Users\\...\\payload.dll,Control_RunDLL\"\n\nNETWORK INDICATORS\nDNS:    update.emotet-c2[.]com -> 185.220.101.42\nHTTPS:  POST hxxps:\u002F\u002F185.220.101[.]42\u002Fwp-content\u002Fgate\u002F (C2 beacon)\nHTTP:   GET hxxp:\u002F\u002Fcompromised-site[.]com\u002Finvoice.dll (payload download)\n\nSURICATA ALERTS\n[1:2028401] ET MALWARE Emotet CnC Beacon\n[1:2028402] ET MALWARE Win32\u002FEmotet Activity\n\nMITRE ATT&CK TECHNIQUES\nT1566.001  Phishing: Spearphishing Attachment\nT1204.002  User Execution: Malicious File\nT1059.001  Command and Scripting Interpreter: PowerShell\nT1218.011  Rundll32 Execution\nT1071.001  Application Layer Protocol: Web Protocols\n\nDROPPED FILES\npayload.dll  SHA-256: abc123... Detection: 48\u002F72 (VirusTotal)\nconfig.dat   SHA-256: def456... (encrypted configuration)\n```\n","# Performing Dynamic Analysis with ANY.RUN\n\n## When to Use\n\n- Interactive malware analysis is needed where the analyst must click dialogs, enter credentials, or navigate installer screens\n- Rapid cloud-based sandbox analysis without maintaining local sandbox infrastructure\n- Malware requires user interaction to proceed past anti-sandbox checks (document macros requiring \"Enable Content\")\n- Sharing analysis results with team members via public or private task URLs\n- Comparing behavior across different OS versions (Windows 7, 10, 11) available in ANY.RUN\n\n**Do not use** for highly sensitive samples that cannot be uploaded to cloud services; use an on-premises sandbox like Cuckoo instead.\n\n## Prerequisites\n\n- ANY.RUN account (free community tier or paid subscription at https:\u002F\u002Fany.run)\n- Modern web browser with WebSocket support for interactive session streaming\n- Sample file ready for upload (max 100 MB for free tier, 256 MB for paid)\n- Understanding of the sample type to select appropriate execution environment\n- VPN or secure network for accessing ANY.RUN portal during analysis sessions\n\n## Workflow\n\n### Step 1: Configure Analysis Environment\n\nSet up the ANY.RUN task with appropriate parameters:\n\n```\nANY.RUN Task Configuration:\n━━━━━━━━━━━━━━━━━━━━━━━━━━\nOS Selection:        Windows 10 x64 (recommended default)\n                     Windows 7 x64 (for legacy malware)\n                     Windows 11 x64 (for modern samples)\nExecution Time:      60 seconds (default) \u002F 120-300 for slow-acting malware\nNetwork:             Connected (captures real C2 traffic)\n                     Residential Proxy (bypasses geo-blocking)\nPrivacy:             Public (free tier) \u002F Private (paid - not indexed)\nMITM Proxy:          Enable for HTTPS traffic decryption\nFake Net:            Enable to simulate internet services if sample checks connectivity\n```\n\n**API-based submission (paid tier):**\n```bash\n# Submit file via ANY.RUN API\ncurl -X POST \"https:\u002F\u002Fapi.any.run\u002Fv1\u002Fanalysis\" \\\n  -H \"Authorization: API-Key $ANYRUN_API_KEY\" \\\n  -F \"file=@suspect.exe\" \\\n  -F \"env_os=windows\" \\\n  -F \"env_version=10\" \\\n  -F \"env_bitness=64\" \\\n  -F \"opt_timeout=120\" \\\n  -F \"opt_network_connect=true\" \\\n  -F \"opt_privacy_type=bylink\"\n\n# Check task status\ncurl \"https:\u002F\u002Fapi.any.run\u002Fv1\u002Fanalysis\u002F$TASK_ID\" \\\n  -H \"Authorization: API-Key $ANYRUN_API_KEY\" | jq '.data.status'\n```\n\n### Step 2: Interact with Malware During Execution\n\nUse the interactive session to trigger malware behavior:\n\n```\nInteractive Actions During Analysis:\n━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━\n1. Document Macros:   Click \"Enable Content\" \u002F \"Enable Editing\" when prompted\n2. Installer Screens: Click through installation dialogs\n3. UAC Prompts:       Click \"Yes\" to allow elevation (observe privilege escalation)\n4. Credential Harvests: Enter fake credentials to observe phishing behavior\n5. Browser Redirects:  Navigate to URLs if malware opens browser windows\n6. File Dialogs:       Select target files if malware presents file picker\n7. Timeout Extension:  Extend analysis time if malware has delayed execution\n```\n\n### Step 3: Analyze Process Tree\n\nReview the complete process execution chain:\n\n```\nProcess Tree Analysis Points:\n━━━━━━━━━━━━━━━━━━━━━━━━━━━\nParent-Child Relationships:\n  - WINWORD.EXE -> cmd.exe -> powershell.exe (macro execution chain)\n  - explorer.exe -> suspect.exe -> svchost.exe (process injection)\n\nProcess Events to Note:\n  - Process creation with suspicious command-line arguments\n  - PowerShell with encoded commands (-enc \u002F -encodedcommand)\n  - cmd.exe executing script files (.bat, .vbs, .js)\n  - Legitimate processes spawned from unusual parents\n  - Process termination (self-deletion behavior)\n```\n\n### Step 4: Review Network Activity\n\nExamine DNS, HTTP\u002FHTTPS, and TCP\u002FUDP connections:\n\n```\nANY.RUN Network Panel Analysis:\n━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━\nDNS Requests:\n  - Domain resolutions with threat intelligence tags\n  - Fast-flux or DGA domain patterns\n  - DNS over HTTPS (DoH) detection\n\nHTTP\u002FHTTPS Traffic (with MITM enabled):\n  - Full request\u002Fresponse bodies for HTTP\n  - Decrypted HTTPS traffic showing C2 commands\n  - Downloaded payloads and their content types\n  - POST data containing exfiltrated information\n\nConnection Map:\n  - Geographic visualization of C2 server locations\n  - Connection timeline showing beacon patterns\n  - Suricata alerts triggered on network traffic\n```\n\n### Step 5: Examine IOCs and Threat Intelligence\n\nExtract indicators and map to known threats:\n\n```\nANY.RUN IOC Categories:\n━━━━━━━━━━━━━━━━━━━━━━\nFiles:       Dropped files with hashes, YARA matches, VirusTotal results\nNetwork:     IPs, domains, URLs contacted during execution\nRegistry:    Keys created\u002Fmodified for persistence\nProcesses:   Suspicious process names and command lines\nMutex:       Named mutexes created (used for single-instance checking)\nSignatures:  Suricata rules triggered, behavioral signatures matched\n\nMITRE ATT&CK Mapping:\n  - ANY.RUN automatically maps observed behaviors to ATT&CK techniques\n  - Review the ATT&CK matrix tab for technique coverage\n  - Export ATT&CK Navigator layer for reporting\n```\n\n### Step 6: Export Analysis Results\n\nDownload comprehensive reports and artifacts:\n\n```bash\n# Download report via API\ncurl \"https:\u002F\u002Fapi.any.run\u002Fv1\u002Fanalysis\u002F$TASK_ID\u002Freport\" \\\n  -H \"Authorization: API-Key $ANYRUN_API_KEY\" \\\n  -o report.json\n\n# Download PCAP\ncurl \"https:\u002F\u002Fapi.any.run\u002Fv1\u002Fanalysis\u002F$TASK_ID\u002Fpcap\" \\\n  -H \"Authorization: API-Key $ANYRUN_API_KEY\" \\\n  -o capture.pcap\n\n# Download dropped files\ncurl \"https:\u002F\u002Fapi.any.run\u002Fv1\u002Fanalysis\u002F$TASK_ID\u002Ffiles\" \\\n  -H \"Authorization: API-Key $ANYRUN_API_KEY\" \\\n  -o dropped_files.zip\n\n# Available exports from ANY.RUN web interface:\n# - HTML Report (shareable standalone page)\n# - PCAP file (network traffic capture)\n# - Process dump (memory dumps of processes)\n# - Dropped files (all files created during execution)\n# - MITRE ATT&CK Navigator JSON\n# - IOC export (STIX\u002FJSON\u002FCSV format)\n```\n\n## Key Concepts\n\n| Term | Definition |\n|------|------------|\n| **Interactive Sandbox** | Analysis environment allowing real-time analyst interaction with the executing sample, enabling triggering of user-dependent behaviors |\n| **MITM Proxy** | Man-in-the-middle TLS interception in ANY.RUN that decrypts HTTPS traffic for visibility into encrypted C2 communications |\n| **Residential Proxy** | ANY.RUN feature routing malware traffic through residential IP addresses to bypass geo-IP and datacenter-IP evasion checks |\n| **Suricata Alerts** | Network IDS signatures triggered during execution, providing immediate identification of known malicious traffic patterns |\n| **Process Tree** | Hierarchical visualization of parent-child process relationships showing the complete execution chain from initial sample to final payloads |\n| **Behavioral Tags** | ANY.RUN classification labels automatically applied based on observed behavior (e.g., \"trojan\", \"stealer\", \"ransomware\") |\n\n## Tools & Systems\n\n- **ANY.RUN**: Cloud-based interactive malware sandbox providing real-time execution monitoring, process trees, network capture, and MITRE ATT&CK mapping\n- **ANY.RUN API**: REST API for programmatic sample submission, status checking, and report\u002Fartifact retrieval\n- **Suricata**: Integrated network IDS within ANY.RUN providing signature-based detection of malicious network traffic\n- **MITRE ATT&CK Navigator**: Framework integration mapping observed malware behaviors to adversary techniques and tactics\n- **VirusTotal Integration**: Automatic hash lookup of sample and dropped files against VirusTotal detection results\n\n## Common Scenarios\n\n### Scenario: Analyzing a Macro-Enabled Document Requiring User Interaction\n\n**Context**: Phishing email contains a .docm file that requires clicking \"Enable Content\" to trigger the macro payload. Traditional non-interactive sandboxes fail to trigger the malicious behavior.\n\n**Approach**:\n1. Upload .docm to ANY.RUN with Windows 10 environment and Microsoft Office installed\n2. When Word opens and displays the security banner, click \"Enable Content\" interactively\n3. Observe the macro execution in the process tree (Word -> cmd.exe -> powershell.exe)\n4. Monitor network panel for PowerShell downloading second-stage payload\n5. If a UAC prompt appears, click \"Yes\" to allow the payload to observe full behavior chain\n6. Review Suricata alerts for known malware signatures on the downloaded payload\n7. Export IOCs (download URLs, dropped file hashes, C2 domains) for blocking\n\n**Pitfalls**:\n- Forgetting to enable MITM proxy, resulting in encrypted HTTPS traffic without visibility\n- Using too short an execution timeout for malware with delayed execution or sleep timers\n- Uploading to public analysis when the sample contains sensitive organizational data\n- Not clicking through all prompts; some malware requires multiple user interactions to fully execute\n\n## Output Format\n\n```\nANY.RUN ANALYSIS REPORT\n=========================\nTask URL:         https:\u002F\u002Fapp.any.run\u002Ftasks\u002F\u003Ctask_id>\nSample:           invoice_q3.docm\nSHA-256:          e3b0c44298fc1c149afbf4c8996fb924...\nVerdict:          MALICIOUS (Score: 95\u002F100)\nFamily:           Emotet\nTags:             [trojan, banker, spam, macro]\n\nPROCESS TREE\nWINWORD.EXE (PID: 2184)\n  └── cmd.exe (PID: 3456) \"\u002Fc powershell -enc JABXAG...\"\n      └── powershell.exe (PID: 4012)\n          └── rundll32.exe (PID: 4568) \"C:\\Users\\...\\payload.dll,Control_RunDLL\"\n\nNETWORK INDICATORS\nDNS:    update.emotet-c2[.]com -> 185.220.101.42\nHTTPS:  POST hxxps:\u002F\u002F185.220.101[.]42\u002Fwp-content\u002Fgate\u002F (C2 beacon)\nHTTP:   GET hxxp:\u002F\u002Fcompromised-site[.]com\u002Finvoice.dll (payload download)\n\nSURICATA ALERTS\n[1:2028401] ET MALWARE Emotet CnC Beacon\n[1:2028402] ET MALWARE Win32\u002FEmotet Activity\n\nMITRE ATT&CK TECHNIQUES\nT1566.001  Phishing: Spearphishing Attachment\nT1204.002  User Execution: Malicious File\nT1059.001  Command and Scripting Interpreter: PowerShell\nT1218.011  Rundll32 Execution\nT1071.001  Application Layer Protocol: Web Protocols\n\nDROPPED FILES\npayload.dll  SHA-256: abc123... Detection: 48\u002F72 (VirusTotal)\nconfig.dat   SHA-256: def456... (encrypted configuration)\n```\n",{"name":5,"tags":49,"author":50,"domain":41,"license":15,"version":51,"nist_csf":52,"subdomain":34,"description":57,"mitre_attack":58,"d3fend_techniques":64},[27,33,43,29,28],"mahipal","1.0.0",[53,54,55,56],"DE.AE-02","RS.AN-03","ID.RA-01","DE.CM-01","Perform interactive dynamic malware analysis using the ANY.RUN cloud sandbox to detonate samples, observe real-time execution behavior, interact with malware prompts such as dialogs and CAPTCHAs, and capture process trees, network traffic, and system changes. Use when a suspicious file or URL needs live, interactive behavioral detonation in a cloud sandbox rather than static analysis alone.\n",[59,60,61,62,63],"T1027","T1055","T1140","T1497","T1591",[65,66,67,68,69],"File Metadata Consistency Validation","Application Protocol Command Analysis","Identifier Analysis","Content Format Conversion","Message Analysis","main","54a798831d2266a3ca61ce68a7acb80b81160d57","skills\u002Fperforming-dynamic-analysis-with-any-run",4395,"https:\u002F\u002Fgithub.com\u002Fmukul975\u002FAnthropic-Cybersecurity-Skills","https:\u002F\u002Fmahipal.engineer\u002FAnthropic-Cybersecurity-Skills\u002F","https:\u002F\u002Fgithub.com\u002Fmukul975","Mahipal.engineer","🔐 Cybersecurity | 💻 Dev | 📷 Street Photographer\r\n🎓 MSc | 📚 Research & AI Security","2026-08-31 12:32:44",{"source":8,"skillName":5,"commands":81,"prompt":91,"zipAvailable":92},[82,85,88],{"tool":83,"command":84},"npx","npx skills add mukul975\u002FAnthropic-Cybersecurity-Skills --skill performing-dynamic-analysis-with-any-run",{"tool":86,"command":87},"bunx","bunx skills add mukul975\u002FAnthropic-Cybersecurity-Skills --skill performing-dynamic-analysis-with-any-run",{"tool":89,"command":90},"pnpm","pnpm dlx skills add mukul975\u002FAnthropic-Cybersecurity-Skills --skill performing-dynamic-analysis-with-any-run","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fmukul975\u002FAnthropic-Cybersecurity-Skills\u002Fblob\u002Fmain\u002Fskills\u002Fperforming-dynamic-analysis-with-any-run\u002FSKILL.md",true,[94,99,105],{"path":95,"resourceType":95,"resourceTypeDesc":96,"sizeBytes":97,"sourceHtmlUrl":98},"LICENSE","许可证",11255,"https:\u002F\u002Fgithub.com\u002Fmukul975\u002FAnthropic-Cybersecurity-Skills\u002Fblob\u002Fmain\u002Fskills\u002Fperforming-dynamic-analysis-with-any-run\u002FLICENSE",{"path":100,"resourceType":101,"resourceTypeDesc":102,"sizeBytes":103,"sourceHtmlUrl":104},"references\u002Fapi-reference.md","REFERENCE","参考文档",3190,"https:\u002F\u002Fgithub.com\u002Fmukul975\u002FAnthropic-Cybersecurity-Skills\u002Fblob\u002Fmain\u002Fskills\u002Fperforming-dynamic-analysis-with-any-run\u002Freferences\u002Fapi-reference.md",{"path":106,"resourceType":107,"resourceTypeDesc":108,"sizeBytes":109,"sourceHtmlUrl":110},"scripts\u002Fagent.py","SCRIPT","脚本",10797,"https:\u002F\u002Fgithub.com\u002Fmukul975\u002FAnthropic-Cybersecurity-Skills\u002Fblob\u002Fmain\u002Fskills\u002Fperforming-dynamic-analysis-with-any-run\u002Fscripts\u002Fagent.py",[112,139,163,190,216,243],{"skillNo":113,"name":114,"nameZh":6,"description":115,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":116,"categories":117,"keywords":119,"publishedAt":44},"01M6AGDM3HJXTKXX15ZZ0ZVCJ3","verifying-build-provenance-with-slsa-sigstore","Verifies artifact signatures and SLSA provenance using Sigstore's cosign (verify, verify-attestation, verify-blob-attestation) and slsa-verifier (verify-artifact), enforcing keyless OIDC builder identity and source repo against SLSA Build levels. Use in CI\u002FCD before deploying artifacts, when consuming third-party attestations, establishing a SLSA Build L3 pipeline, or confirming provenance during incident response or admission control.","https:\u002F\u002Fgithub.com\u002Fmukul975\u002FAnthropic-Cybersecurity-Skills\u002Fblob\u002Fmain\u002Fskills\u002Fverifying-build-provenance-with-slsa-sigstore\u002FSKILL.md",[118],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},[120,121,122,123,124,41,125,126,127,128,129,130,131,132,133,134,135,136,137,138],"sigstore","provenance","slsa","verifying build provenance with slsa sigstore","security","incident response","identity","pr","code","artifacts","ci","supply-chain","pipeline","supply-chain-security","t1195","attestation","code-signing","cosign","keyless",{"skillNo":140,"name":141,"nameZh":6,"description":142,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":143,"categories":144,"keywords":146,"publishedAt":44},"01M6AGDGBPWYVZ2F11GFKJ4HZ9","validating-tpm-measured-boot-attestation","Verifies TPM 2.0 measured-boot integrity and remote attestation with tpm2-tools -- reading PCRs (tpm2_pcrread), replaying the boot event log, generating and checking signed quotes (tpm2_quote\u002Ftpm2_checkquote), and sealing secrets to a PCR policy. Use to confirm a system booted trusted firmware\u002Fkernel for Zero Trust device posture, detect boot-chain tampering via PCR drift, or build a golden-value baseline for fleet attestation.","https:\u002F\u002Fgithub.com\u002Fmukul975\u002FAnthropic-Cybersecurity-Skills\u002Fblob\u002Fmain\u002Fskills\u002Fvalidating-tpm-measured-boot-attestation\u002FSKILL.md",[145],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},[147,135,148,149,124,150,41,127,151,152,153,154,155,156,157,158,159,160,161,162],"boot","TPM","validating tpm measured boot attestation","policy","verification","ZeRO","firmware","Tools","measured-boot","PCR","integrity","secrets","remote-attestation","tpm2-tools","integrity-verification","trusted-computing",{"skillNo":164,"name":165,"nameZh":6,"description":166,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":167,"categories":168,"keywords":173,"publishedAt":44},"01M6AGDCW0Y4FXZ3362GT1941M","validating-backup-integrity-for-recovery","Validates backup integrity through cryptographic hash verification, automated restore testing, corruption detection, and recoverability checks to confirm backups are reliable for disaster recovery and ransomware response. Use before relying on backups for recovery, when building post-backup validation pipelines, auditing backup infrastructure for compliance, or checking immutable\u002Fair-gapped backups for silent corruption or tampering.","https:\u002F\u002Fgithub.com\u002Fmukul975\u002FAnthropic-Cybersecurity-Skills\u002Fblob\u002Fmain\u002Fskills\u002Fvalidating-backup-integrity-for-recovery\u002FSKILL.md",[169,172],{"categoryNo":170,"categoryName":171,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000008","测试与质量",{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},[157,174,175,176,177,41,178,40,151,179,180,181,182,183,184,185,186,187,188,189],"backup","recovery","validating backup integrity for recovery","testing","infrastructure","compliance","hash-verification","incident-response","ransomware","cryptocurrency","detection","t1078","t1490","immutable","disaster-recovery","restore-testing",{"skillNo":191,"name":192,"nameZh":6,"description":193,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":194,"categories":195,"keywords":197,"publishedAt":44},"01M6AGD9GBG2KZ336AE763J3WH","triaging-windows-with-kape","Runs KAPE (Kroll Artifact Parser and Extractor) to collect targeted forensic artifacts (registry hives, $MFT, event logs, prefetch, browser data) via Targets and parse them with Modules wrapping Eric Zimmerman's EZ Tools (PECmd, MFTECmd, RECmd). Use during early incident containment\u002Ftriage when full disk imaging is impractical but a defensible, parseable Windows artifact set is needed quickly, including at-scale remote collection.","https:\u002F\u002Fgithub.com\u002Fmukul975\u002FAnthropic-Cybersecurity-Skills\u002Fblob\u002Fmain\u002Fskills\u002Ftriaging-windows-with-kape\u002FSKILL.md",[196],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},[198,199,200,41,201,202,203,204,205,206,207,208,209,210,211,212,154,213,214,215],"windows","kape","triaging windows with kape","registry","browser","logs","windows-forensics","dfir","mft","mftecmd","data","prefetch","eric-zimmerman","digital-forensics","SET","collection","pecmd","artifact-collection",{"skillNo":217,"name":218,"nameZh":6,"description":219,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":220,"categories":221,"keywords":223,"publishedAt":44},"01M6AGD5PW5J4EVZM958WD74ZQ","triaging-vulnerabilities-with-ssvc-framework","Triages and prioritizes vulnerabilities with CISA's Stakeholder-Specific Vulnerability Categorization (SSVC) decision tree, weighing exploitation status (via the CISA KEV catalog and FIRST EPSS API), technical impact, automatability, and mission prevalence to output Track\u002FTrack*\u002FAttend\u002FAct decisions. Use when prioritizing vulnerability scan results (OpenVAS, Nessus, Qualys) for remediation planning beyond raw CVSS scores.","https:\u002F\u002Fgithub.com\u002Fmukul975\u002FAnthropic-Cybersecurity-Skills\u002Fblob\u002Fmain\u002Fskills\u002Ftriaging-vulnerabilities-with-ssvc-framework\u002FSKILL.md",[222],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},[224,225,226,41,227,228,229,230,231,232,233,234,235,236,237,238,239,240,241,242],"vulnerabilities","framework","triaging vulnerabilities with ssvc framework","status","planning","CISA","vulnerability-management","risk-management","nessus","qualys","openvas","cvss","remediation","risk","vulnerability","api","prioritization","ssvc","decision-tree",{"skillNo":244,"name":245,"nameZh":6,"description":246,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":247,"categories":248,"keywords":250,"publishedAt":44},"01M6AGD24TTQQM4CXG69E3B9TJ","triaging-security-incident","Performs initial triage of security incidents using the NIST SP 800-61r3 and SANS PICERL frameworks, classifying incident type, assigning priority by business impact, and routing to the appropriate response team. Use when a SIEM\u002FEDR alert needs human classification, concurrent alerts must be prioritized, or a user report or threat-intel IOC match requires initial incident categorization.","https:\u002F\u002Fgithub.com\u002Fmukul975\u002FAnthropic-Cybersecurity-Skills\u002Fblob\u002Fmain\u002Fskills\u002Ftriaging-security-incident\u002FSKILL.md",[249],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},[124,251,41,252,38,253,254,255,256,257,258,185,31,186,26,259,260,261,262,263],"triaging security incident","siem","ioc","soc","NIST-800-61","NIST","severity","edr","classification","severity-classification","incident-triage","SANS-PICERL","SOC-operations"]