CyberKit

capa Namespaces

How to read a capa report, and how much weight each namespace deserves.

capa answers what a binary can do, from static analysis, and files what it finds under a namespace tree. Learning the namespaces is most of learning to read a report.

A matched rule is a fact about the code, not about behavior. Capability to inject is not proof it injected.

14 rows.

capa namespaces
NamespaceWhat it detects
anti-analysisObfuscation, packing, anti-debugging, anti-VM and anti-disassembly.
persistenceRegistry run keys, services, scheduled tasks, startup folders, COM hijacking.
collectionKeylogging, screen capture, credential and browser data access, microphone and webcam.
communicationHTTP, DNS, TCP, UDP, FTP, sockets, named pipes, and C2-shaped exchanges.
host-interactionEverything the binary does to the machine: processes, threads, files, registry, services, drivers, the shell.
data-manipulationEncryption, encoding, hashing, checksums, compression and random number generation.
load-codeLoading and executing code that was not in the original image: shellcode, PEs, .NET assemblies.
impactThe end goal: remote access, backdoors, destruction.
exploitationBehavior associated with exploiting a vulnerability.
executableProperties of the file format itself: PE structure, ELF structure, embedded subfiles, resources.
compiler / runtime / linkingWhich toolchain produced the binary, which runtime it needs, and how it was linked.
malware-familyRules that recognize a specific named family.
nurseryRules that are not yet mature enough for the main collection.
lib / internalBuilding blocks other rules depend on, and capa's own bookkeeping.

Related

All references