| name | frida |
| description | Dynamic instrumentation via Frida - attach to or spawn a process, load a JS hook script, capture send() events into a lifecycle-managed run directory. Supports local, USB-attached, and remote frida-server targets. |
Frida - dynamic instrumentation (alpha)
Hook a target at runtime to confirm LLM-flagged sinks actually execute, trace API calls, bypass SSL pinning, scan memory for secrets.
When to use
/scan or /agentic flagged a sink and you want to confirm it fires at runtime before treating it as exploitable.
- A binary or mobile app is doing something opaque and a few minutes of API-trace would reveal the shape.
- A pinned mobile app is blocking your MITM proxy.
- A crash you can't
rr-record (macOS) needs a function-call trace.
Install
pipx install frida-tools
raptor doctor
For remote / mobile targets, install the matching frida-server on the target side. See docs/frida.md. Note: most frida-server binaries bind to 127.0.0.1 by default - start with -l 0.0.0.0:27042 or SSH-forward port 27042.
Invocation
The slash command surfaces the libexec wrapper; run it as Bash. Lifecycle (output dir, run state) is handled by the wrapper.
libexec/raptor-frida --target <pid|name|bundle-id|binary>
(--template <name> | --script <path>)
[--host HOST[:PORT]] [--usb]
[--duration N] [--spawn] [--unsafe-attach]
Equivalent CLI without a Claude session: raptor frida ....