Documentacao renderizada
Esta pagina renderiza o Markdown e Mermaid do modulo diretamente da fonte publica de documentacao.
Overview#
CAPE (Config And Payload Extraction) is an open-source malware analysis sandbox that extends Cuckoo with specialised capabilities for extracting malware configuration data and decrypted payloads from detonated samples. Unlike general-purpose sandboxes, CAPE focuses on defeating evasive malware through process injection hooks and signature-based unpacking -- automatically extracting C2 addresses, encryption keys, mutex names, and injected shellcode from samples during dynamic analysis. Argus integrates CAPE to chain sandbox results into the investigation, threat intelligence, and IOC enrichment workflows.
Key Features#
Sample Submission and Analysis Tracking#
Submit malware to a CAPE instance via
syncCapeSandboxAnalysis, providing the task ID, target file hash, file name, analysis machine profile, detection score (0-10), and triggered signatures. Analysis records are persisted to PostgreSQL scoped to the organisation. The score and signatures fields capture CAPE's automated detection summary without requiring Argus to re-run the analysis.
Signature-Based Detection Inventory#
Each CAPE analysis records the list of signatures triggered during detonation -- e.g.,
network_cnc_http, infostealer_cookies, ransomware_file_modifications, injection_runpe. These signatures form a machine-readable classification that can be cross-referenced against MISP malware families, Sigma rules, and YARA patterns to chain detections together.
Clearance-Level Analysis Isolation#
Analysis records carry
secrecy_level tags. Classified malware samples (e.g., nation-state implants analysed as part of a classified incident response) can be tagged accordingly, restricting their visibility to cleared personnel.
Cross-Domain Intelligence Linking#
CAPE analysis results feed naturally into other Argus domains: extracted C2 IP addresses become MISP indicators, file hashes link to MWDB samples, and signature names can trigger YARA rule lookups or Sigma rule correlation queries.
Statistics and Coverage View#
The
capeSandboxStats query returns analysis counts by score band (clean/suspicious/malicious), signature category distribution, and machine profile utilisation -- useful for managing sandbox capacity and understanding the malware composition entering the analysis pipeline.
Use Cases#
- Automated Malware Triage: Queue all samples extracted from phishing attachments, endpoint EDR quarantine exports, or MWDB downloads through CAPE to produce a fast machine classification before analyst manual review.
- C2 Indicator Extraction: After CAPE extracts C2 addresses from a ransomware configuration, automatically feed them into MISP as new indicators and into Suricata as blocking rules -- closing the loop between analysis and defence in a single workflow.
- Evasive Malware Unpacking: CAPE's process injection hooks defeat many common evasion techniques used by loaders (Emotet, Qakbot, IcedID) to extract the final payload -- providing the actual malicious binary for YARA rule development.
- Classified Implant Analysis: In a sensitive compartmented environment, CAPE analysis of suspected nation-state implants is tagged at appropriate classification with results restricted to cleared analysts.
Integration#
Available via GraphQL:
capeSandboxAnalyses, capeSandboxStats (queries); syncCapeSandboxAnalysis (mutation). All operations require authentication and organisation scoping.
Compatible with CAPE Sandbox REST API v2+. Works alongside MWDB (sample metadata), YARA Engine (signature rule development from extracted strings), MISP (C2 indicator publishing), and the Investigation domain (attachment to active cases).
Last Reviewed: 2026-03-18