mandiant /capa
The FLARE team's open-source tool to identify capabilities in executable files.
★ 6,336⑂ 757👁 88⑃ 1,983● 1,202▤ 44
+1
Daily
+37
Weekly
+89
Monthly
6,336
stars
757
forks
88
watchers
1,983
prs
1,202
issues
44
releases
README
Website | Download | Web Interface --- capa detects capabilities in executable files. You run it against a PE, ELF, .NET module, shellcode file, or a sandbox report and it tells you what it thinks the program can do. For example, it might suggest that the file is a backdoor, is capable of installing services, or relies on HTTP to communicate. To interactively inspect capa results in your browser use the capa Explorer Web. If you want to inspect or write capa rules, head on over to the capa-rules repository. Otherwise, keep reading. Below you find a list of our capa blog posts with more details. example capa output $ capa.exe suspicious.exe +--------------------+------------------------------------------------------------------------+ | ATT&CK Tactic | ATT&CK Technique | |--------------------+------------------------------------------------------------------------| | DEFENSE EVASION | Obfuscated Files or Information [T1027] | | DISCOVERY | Query Registry [T1012] | | | System Information Discovery [T1082] | | EXECUTION | Command and Scripting Interpreter::Windows Command Shell [T1059.003] | | | Shared Modules [T1129] | | EXFILTRATION | Exfiltration Over C2 Channel [T1041] | | PERSISTENCE | Create or Modify System Process::Windows Service [T1543.003] | +--------------------+------------------------------------------------------------------------+ +-------------------------------------------+-------------------------------------------------+ | CAPABILITY | NAMESPACE | |-------------------------------------------+-------------------------------------------------| | read and send data from client to server | c2/file-transfer | | execute shell command and capture output | c2/shell | | receive data (2 matches) | communication | | send data (6 matches) | communication | | connect to HTTP server (3 matches) | communication/http/client | | send HTTP request (3 matches) | communication/http/client | | create pipe | communication/named-pipe/create | | get socket status (2 matches) | communication/socket | | receive data on socket (2 matches) | communication/socket/receive | | send data on socket (3 matches) | communication/socket/send | | connect TCP socket
Top issues
#520show the prevalence of rules in the output24 comments · 2021-04-08#1899Add tests (and refactor) API extraction and symbol generation23 comments · 2023-12-09#2622emit number(0) (offset(0)??) for instructions like "XOR EAX, EAX"22 comments · 2025-03-10#1303make string length configurable and consistent across backends21 comments · 2023-02-01#1610binja: optimize performance of name demangling19 comments · 2023-07-10#771new feature: function call arguments19 comments · 2021-09-10#2663Add symbol name features for dynamically resolved function pointers16 comments · 2025-05-13#2402binary ninja: optimize feature extraction15 comments · 2024-09-25
Discussions
#3204capa-x: a native Rust implementation of capa with differential parity testing0 comments · 2026-10-21#3181New contributor introduction - interested in capa rules & GSoC 20270 comments · 2026-09-19#2953GSoC 2026: Automated behavioural rule generation for Capa - Deetya Shivathaya0 comments · 2026-03-21#2926RFC: Attach Host/Network Behavioral Indicators (HBI/NBI) to Capability Detections0 comments · 2026-03-15#2925RFC: Lightweight Data-Flow Tracking for Cross-Instruction Capability Detection2 comments · 2026-03-14#2919Improving Stability and Performance of ELF Analysis in capa0 comments · 2026-03-14#2593v9.0.00 comments · 2025-02-05#2560gsoc and community chat related doubts1 comments · 2025-01-18
Latest release
v10.0.0 v10.0.0 2026-10-16This release fixes a security issue in how capa loads vivisect workspaces, a large batch of bug fixes, a new --reproducible flag for freeze, dependency updates, and 12 new rules. We'd like to thank the following contributors: Ange Albertini (@corkamig), @aryanyk, Luca Schrott (@1337Name), @eversinc33, Matt Williams (@mwilliams31), Rizky Mirzaviandy Priambodo (@Xavrir), Sukesh Kumar (@SkxOverKill), lakshit verma (@vee1e), @w3lld1, and others! Security Crafted .viv files could execute code when capa analyzed a sample: either the sample itself named .viv, or a .viv next to it. capa now alw