meltedinhex/analyst-ai-pack / skills/analyzing-api-call-traces
analyzing-api-call-traces
VerifiedAnalyzes 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.
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
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.mdfor the classifier. - ATT&CK T1106 and the Windows API Index (linked in frontmatter).
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| receiving-code-reviewobra/superpowersUse when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical rigor and verification, not performative agreement or blind implementation | Stars: 319k | Updated | Claude CodeCodex | Verified | Install |
| requesting-code-reviewobra/superpowersUse when completing tasks, implementing major features, or before merging to verify work meets requirements | Stars: 319k | Updated | Claude CodeCodex | Verified | Install |
| using-git-worktreesobra/superpowersUse when starting feature work that needs isolation from current workspace or before executing implementation plans - ensures an isolated workspace exists via native tools or git worktree fallback | Stars: 319k | Updated | Claude CodeCodex | Verified | Install |
| verification-before-completionobra/superpowersUse when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before assertions always | Stars: 319k | Updated | Claude CodeCodex | Verified | Install |