Analyzing Api Call Traces
Analyzes API call traces from a sandbox or API monitor (JSON) to group calls by
Install
$ agentstack add skill-meltedinhex-analyst-ai-pack-analyzing-api-call-traces ✓ scanned · ✓ verified, works with Claude Code, Cursor, and more.
Security review
✓ PassedNo issues found. Passed automated security review. · v0.1.0 How review works →
- ✓ Prompt-injection patterns
- ✓ Secret / credential exfiltration
- ✓ Dangerous shell & filesystem operations
- ✓ Untrusted network calls
- ✓ Known-malicious package signatures
What it can access
- ✓ Network access No
- ✓ Filesystem access No
- ✓ Shell / process execution No
- ✓ Environment & secrets No
- ✓ Dynamic code execution No
From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.
Verified badge
Passed review? Show it. Paste this badge into your README, it links to the public security report.
Links to your public security report.[](https://agentstack.voostack.com/security/report/skill-meltedinhex-analyst-ai-pack-analyzing-api-call-traces) Reliability & compatibility
Declared compatibility
Compatibility is declared by the source manifest. End-to-end runtime verification is coming, see below.
We're building live execution health for every listing: tool-call success rate, median latency, uptime, and last-checked timestamps, measured, not self-reported. It isn't live yet, so we don't show numbers we can't stand behind.
How agent discovery & health will work →About
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.jsonBuckets 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).
Source & license
This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.
- Author: meltedinhex
- Source: meltedinhex/analyst-ai-pack
- License: Apache-2.0
- Homepage: https://meltedinhex.com/
Install and usage instructions live in the source repository linked above.
Reviews
No reviews yet, be the first.
Write a review
Versions
- v0.1.0 Imported from the upstream source.