Docs / Go deeper

Traffic capture

Capture real traffic from a browser or an Android phone, then replay and change any request from a node.

Traffic capture (Web Tracer and Mobile Tracer)

The engines map a target from the outside. The tracers capture it from the inside: they man-in-the-middle your own live traffic behind a per-session CA and feed every request into the same asset graph, so the endpoints, operations and parameters a real session touches become assets a scan can target.

Modes

Capture is opt-in per workflow. Passive (the default) reduces traffic into assets and holds nothing. Full capture persists complete request and response pairs into a Requests table, and can hold traffic at an intercept gate so you can modify and forward, or drop, each request (manually or auto-approved).

Bench and the Repeater

Send any captured request to Bench to replay and mutate it. Unlike a browser-based repeater, Bench runs the request through a node you choose, so a replay leaves from that node's own address, as a scan on that node does.

Mobile TracerAndroid only

The Crossfyre Tracer app turns a phone into a capture node with no laptop in the loop. It uses Android's VpnService to route the device's own traffic through an on-device MITM, scoped to the apps you pick, and pairs to a workspace by QR code.

Certificate-pinned apps. Android 7+ does not trust user-installed CAs by default, and a pinned app trusts only its own certificate, so ordinary on-device capture sees nothing from it. Tap patch and the phone uploads that app's split APKs with the session CA; the patch service rewrites and re-signs the app so it trusts your session certificate, and returns installable splits that the phone reinstalls (uninstall then install, because the signature changes). No root, no PC, no Frida attach.

App files you upload are processed in a temporary working directory that is deleted when the job finishes, whether it succeeds or fails. Android only. Use it only on apps you own or are authorized to test.

Bench & Repeater

Capture gets you the request. Bench is where you do something with it.

The Requests table holds everything a capture session recorded, with full bodies when full capture is on. Anything in it can be sent to the Repeater, which re-issues a request with whatever you change and shows the response beside it. The Repeater is built around tabs and history, so a series of attempts is a series you can go back through rather than one box you keep overwriting.

Requests execute on the node, not from your browser, so each one leaves from the node's own address, the same address a scan on that node comes from. That shows you what the target sends back to the address your scans use.

A request goes out only when its host is on the workspace's authorised scope list, on any port or on the URL's port.

Interception is a separate switch. With it on, a matching request pauses so you can edit it before it goes out.