capa-triage

Performs initial triage of unknown native binaries using Mandiant capa and FLOSS.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/warterbili/AUTO_REVERSE --skill capa-triage
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: capa-triage
Source: https://github.com/warterbili/AUTO_REVERSE/tree/main/skills/native/capa-triage
Command: npx skills add https://github.com/warterbili/AUTO_REVERSE --skill capa-triage

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Manually identifying capabilities and deobfuscating strings in unknown native binaries before deep reverse engineering is slow and inefficient, wasting valuable analyst time on irrelevant code paths.

Core Features & Use Cases

  • Automated Capability Identification: Uses Mandiant capa to map binary capabilities (crypto, network, anti-debug, file operations) with exact hit addresses for targeted decompilation in Ghidra or IDA.
  • Obfuscated String Recovery: Retrieves hidden, stack-built, or encoded strings (URLs, encryption keys, C2 endpoints) using FLOSS for PE/shellcode samples and native tooling for ELF/.so files.
  • Use Case: When analyzing an unknown malicious .so library from an Android app, run this triage first to locate all crypto and network-related functions, so you can focus decompiler efforts only on the relevant code sections instead of the entire binary.

Quick Start

Use the capa-triage skill to perform a quick capability and string triage on the unknown native library 'libsuspect.so' extracted from an unpacked Android APK.

Frequently Asked Questions about capa-triage

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I quickly identify capabilities in an unknown native binary before decompiling?

Obfuscated string recovery uses FLOSS for PE and shellcode samples, alongside native tooling for ELF and .so files, to retrieve hidden stack-built or encoded strings. This triage extracts URLs, encryption keys, and C2 endpoints before deep reverse engineering.

Can I perform capability analysis on ARM64 Android native libraries?

Capability analysis fully supports ARM64 Android binaries alongside x86 and x64 ELF files with platform-specific guidance. It applies Mandiant capa rules and ATT&CK or MBC categorization to map functions in unknown native code extracted from unpacked APKs.

What is the best way to triage an unknown malicious .so file from an Android app?

The best way to triage an unknown malicious .so file is running a combined capability and string extraction analysis first. This locates all crypto and network-related functions, allowing you to focus decompiler efforts only on relevant code sections instead of the entire binary.

Does capa capability mapping provide exact addresses for targeted decompilation in Ghidra or IDA?

Capa capability mapping provides exact hit addresses for targeted decompilation in Ghidra or IDA. By categorizing these findings using ATT&CK and MBC frameworks, analysts can quickly prioritize decompilation efforts for unknown native binaries.

Why should I run a binary triage before starting deep reverse engineering?

Running a binary triage before deep reverse engineering prevents wasting valuable analyst time on irrelevant code paths. It rapidly identifies embedded capabilities and recovers obfuscated strings, directing decompiler efforts only toward the relevant code sections.