Performing Dynamic Analysis With Any Run
Overview
Cybersecurity skill for performing dynamic analysis with any run. Follows industry best practices and security standards.
When to Use
Trigger phrases:
"performing dynamic analysis with any run"
"Performs interactive dynamic malware analysis using the ANY"
Interactive malware analysis is needed where the analyst must click dialogs, enter credentials, or navigate installer screens
Rapid cloud-based sandbox analysis without maintaining local sandbox infrastructure
Malware requires user interaction to proceed past anti-sandbox checks (document macros requiring "Enable Content")
Sharing analysis results with team members via public or private task URLs
Comparing behavior across different OS versions (Windows 7, 10, 11) available in ANY.RUN
Do not use for highly sensitive samples that cannot be uploaded to cloud services; use an on-premises sandbox like Cuckoo instead.
When NOT to Use
- When you lack proper authorization for testing
- For production systems without change management
- When the task requires legal or compliance expertise beyond technical scope
Prerequisites
- ANY.RUN account (free community tier or paid subscription at https://any.run)
- Modern web browser with WebSocket support for interactive session streaming
- Sample file ready for upload (max 100 MB for free tier, 256 MB for paid)
- Understanding of the sample type to select appropriate execution environment
- VPN or secure network for accessing ANY.RUN portal during analysis sessions
Workflow
# Example: IOC detection
import re
IOC_PATTERNS = {
"ip": r"\b(?:\d{1,3}\.){3}\d{1,3}\b",
"domain": r"\b[a-z0-9-]+\.[a-z]{2,}\b",
"hash_md5": r"\b[a-f0-9]{32}\b",
"hash_sha256": r"\b[a-f0-9]{64}\b",
}
def extract_iocs(text: str) -> dict:
return {k: re.findall(v, text) for k, v in IOC_PATTERNS.items()}
- Plan Operations — Define objectives, scope, and success criteria for dynamic analysis operations.
- Prepare Environment — Set up tools, access, and data sources required for dynamic analysis.
- Execute Core Workflow — Use any run to perform dynamic analysis operations following established procedures.
- Validate Results — Verify that results meet quality standards and objectives.
- Report Findings — Document results, observations, and recommendations.
- Follow Up — Track remediation actions and verify fixes where applicable.
Tools
- any run — Primary tool for this skill
- Analysis Platform — Data processing and visualization
- Collaboration Tools — Team coordination and knowledge sharing
Process
- Design — Define interface, identify patterns, plan implementation
- Implement — Write code following existing conventions, add tests
- Verify — Run tests, check integration, validate behavior
Verification
Anti-Rationalization Table
| Rationalization |
Reality |
| "We are too small to be targeted" |
Automated attacks target everyone. Size does not matter. |
| "Security slows us down" |
A breach slows you down 100x more. Build security in from the start. |
| "We will fix it after launch" |
Vulnerabilities in production are exploited within hours. Fix before deploy. |
1---2name: performing-dynamic-analysis-with-any-run3description: Use when performs interactive dynamic malware analysis using the ANY.RUN cloud sandbox to observe real-time execution behavior, interact with malware prompts, and capture process trees, network traffic, and system changes. Activates for requests involving interactive sandbox analysis, cloud-based malware detonation, real-time behavioral observation, or ANY.RUN usage. . Use when working with performing dynamic analysis with any run.4license: Apache-2.05---67# Performing Dynamic Analysis With Any Run89## Overview1011Cybersecurity skill for performing dynamic analysis with any run. Follows industry best practices and security standards.1213## When to Use14**Trigger phrases:**15- "performing dynamic analysis with any run"16- "Performs interactive dynamic malware analysis using the ANY"171819- Interactive malware analysis is needed where the analyst must click dialogs, enter credentials, or navigate installer screens20- Rapid cloud-based sandbox analysis without maintaining local sandbox infrastructure21- Malware requires user interaction to proceed past anti-sandbox checks (document macros requiring "Enable Content")22- Sharing analysis results with team members via public or private task URLs23- Comparing behavior across different OS versions (Windows 7, 10, 11) available in ANY.RUN2425**Do not use** for highly sensitive samples that cannot be uploaded to cloud services; use an on-premises sandbox like Cuckoo instead.262728## When NOT to Use2930- When you lack proper authorization for testing31- For production systems without change management32- When the task requires legal or compliance expertise beyond technical scope333435## Prerequisites3637- ANY.RUN account (free community tier or paid subscription at https://any.run)38- Modern web browser with WebSocket support for interactive session streaming39- Sample file ready for upload (max 100 MB for free tier, 256 MB for paid)40- Understanding of the sample type to select appropriate execution environment41- VPN or secure network for accessing ANY.RUN portal during analysis sessions4243## Workflow4445```python46# Example: IOC detection47import re4849IOC_PATTERNS = {50 "ip": r"\b(?:\d{1,3}\.){3}\d{1,3}\b",51 "domain": r"\b[a-z0-9-]+\.[a-z]{2,}\b",52 "hash_md5": r"\b[a-f0-9]{32}\b",53 "hash_sha256": r"\b[a-f0-9]{64}\b",54}5556def extract_iocs(text: str) -> dict:57 return {k: re.findall(v, text) for k, v in IOC_PATTERNS.items()}58```59601. **Plan Operations** — Define objectives, scope, and success criteria for dynamic analysis operations.612. **Prepare Environment** — Set up tools, access, and data sources required for dynamic analysis.623. **Execute Core Workflow** — Use any run to perform dynamic analysis operations following established procedures.634. **Validate Results** — Verify that results meet quality standards and objectives.645. **Report Findings** — Document results, observations, and recommendations.656. **Follow Up** — Track remediation actions and verify fixes where applicable.6667## Tools6869- **any run** — Primary tool for this skill70- **Analysis Platform** — Data processing and visualization71- **Collaboration Tools** — Team coordination and knowledge sharing727374## Process75761. **Design** — Define interface, identify patterns, plan implementation771. **Implement** — Write code following existing conventions, add tests781. **Verify** — Run tests, check integration, validate behavior7980## Verification8182- [ ] All dynamic analysis procedures executed completely and documented83- [ ] Findings validated against multiple data sources84- [ ] False positives identified and filtered85- [ ] Results documented with evidence and timestamps86- [ ] Recommendations provided with risk-based prioritization8788## Anti-Rationalization Table8990| Rationalization | Reality |91|---|---|92| "We are too small to be targeted" | Automated attacks target everyone. Size does not matter. |93| "Security slows us down" | A breach slows you down 100x more. Build security in from the start. |94| "We will fix it after launch" | Vulnerabilities in production are exploited within hours. Fix before deploy. |