SECURITY REVIEW
Not yet assessed
Review the original instructions and requested permissions before installing.
No security review is available for this catalog entry yet.
Community / AGENT SKILL
analyzing-api-call-traces
0
Analyzes API call traces from a sandbox or API monitor (JSON) to group calls by category, reconstruct high-level behaviors (process injection, file drops, network, crypto), and flag suspicious call sequences. Activates for requests to analyze an API trace, interpret sandbox API logs, or identify behavior from Win32/Native API calls.
Understand the trade-offs.
SKILL QUALITY
Not yet assessed
How clearly the skill guides your agent, how complete its workflow is, and how you can check the outcome.
No quality assessment is available for this catalog entry yet.
The full skill.
Original instructions from the publisher’s SKILL.md
# Analyzing API Call Traces ## When to Use - You have a JSON API trace (CAPE/Cuckoo "apistats"/calls, API Monitor export) from a detonation. - You need to translate raw API calls into high-level behaviors and flag suspicious sequences (e.g., `VirtualAllocEx` → `WriteProcessMemory` → `CreateRemoteThread`). **Do not use** this as a substitute for detonation — it consumes an existing trace produced in an isolated sandbox. ## Prerequisites - A JSON API trace with at least an API name per call (and optionally arguments). ## Safety & Handling - Consume traces only; never execute the sample to generate one outside a sandbox. ## Workflow ### Step 1: Group calls by category ```bash python scripts/analyst.py classify trace.json ``` Buckets calls into process, memory, file, registry, network, crypto, and synchronization. ### Step 2: Detect behavior signatures Matches ordered API sequences that indicate techniques — remote injection, hollowing, self-deletion, dynamic API resolution (`LoadLibrary`/`GetProcAddress` bursts). ### Step 3: Prioritize and report Rank detected behaviors by severity and map each to ATT&CK. ## Validation - Each API call is categorized; unknown APIs are reported, not dropped silently. - Injection-style sequences are detected only when the ordered prerequisites are present. - Detected behaviors map to ATT&CK techniques. ## Pitfalls - Flagging individual benign APIs out of context — the sequence matters. - Assuming call order in the JSON equals execution order without a timestamp/index. - Ignoring failed calls (non-zero error) that never actually executed the behavior. ## References - See [`references/api-reference.md`](references/api-reference.md) for the classifier. - ATT&CK T1106 and the Windows API Index (linked in frontmatter).