r2frida — authorized lab orientation
r2frida (nowsecure/r2frida) connects radare2 workflows to Frida instrumentation. Use it only against processes and builds you are authorized to instrument.
Snapshot
| Field | Value |
|---|---|
| Bridge | r2frida (r2 ↔ Frida) |
| Frida starter | Frida getting started (legal) |
| Frida scripts | Frida scripts overview |
| r2 automation peer | r2pipe, radare2 plugins |
Allowed framing
- Driving a live session on an app your class compiled, using r2 commands you already teach, while Frida provides the inject/attach path your device policy allows.
- Comparing "plain Frida script" vs "r2frida session" ergonomics for the same authorized target.
- Documenting version pins (r2, Frida, r2frida) in the lab image.
Scope we will not cover
- No SSL-pin / root-detect / anti-Frida defeat cookbooks.
- No DRM / paid-feature unlock recipes.
- No unauthorized Play/App Store repackaging guides.
- No credential or token theft scripts.
Beginner path (authorized only)
- Complete Frida getting started (legal) on a process you own.
- Open the same binary in radare2 statically so students know the map before going live.
- Install r2frida per upstream docs matching your r2/Frida versions; attach only under authorization.
- Prefer short, auditable sessions; archive command history as Evidence.
- If the course does not need r2, stay on Frida scripts — do not force the bridge.
- Use r2frida when an authorized lab truly wants radare2 UX on a Frida-instrumented process.
- Prefer plain Frida for script-first courses; r2pipe/plugins for offline r2 automation.
- Refuse DRM, root-hide, anti-Frida defeat and crack framing.
For legal, authorized and educational use only.
FAQ
What is r2frida?
r2frida is a bridge that lets radare2 sessions talk to Frida-instrumented processes — useful when a lab wants r2's analysis UX against a live authorized target. Confirm install steps for your r2/Frida versions in upstream docs; APIs evolve.
Do I need r2frida to use Frida?
No. Most courses start with Frida getting started and Frida scripts. Add r2frida only when the syllabus wants r2-driven live sessions.
Plugin vs bridge?
Treat r2frida as a specialized integration in the r2 ecosystem (see also radare2 plugins). Still requires Frida on the device/host under authorization.
Mobile jailbreak/root requirements?
Device policy is lab-specific. BinBench will not publish jailbreak/root or root-hide cookbooks. Only instrument apps and devices you may test.
Does this teach SSL-pin defeat or pirate unlocks?
No. Authorized instrumentation and education only — no DRM bypass, anti-Frida defeat or crack framing.