Frida core library.
- Lets you inject your own JavaScript instrumentation code into other processes, optionally with your own C code for performance-sensitive bits.
- Acts as a logistics layer that packages up GumJS into a shared library.
- Provides a two-way communication channel for talking to your scripts, if needed, and later unload them.
- Also lets you enumerate installed apps, running processes, and connected devices.
- Written in Vala, with OS-specific glue code in C/Objective-C/asm.
Typically used through one of the available language bindings:
E.g.:
$ pip install frida-tools # CLI tools
$ pip install frida # Python bindings
$ npm install frida # Node.js bindingsOr, for static linking into your own project written in a C-compatible language, download a devkit from the Frida releases page.
For building a shared library suitable for distro packaging:
$ ./configure --enable-shared --without-prebuilds=sdk && makeThis builds libfrida-core-1.0.so against system dependencies,
while frida-agent.so is built using Frida's SDK (with its GLib
fork, needed for the agent's inject/unload lifecycle).
Prerequisites on Fedora:
$ sudo dnf install libgee-devel json-glib-devel \
libsoup3-devel libunwind-devel libdwarf-devel \
libnice-devel ngtcp2-crypto-ossl-develPrerequisites on Ubuntu:
$ sudo apt install libgee-0.8-dev libjson-glib-dev \
libsoup-3.0-dev libunwind-dev libdwarf-dev \
libnice-dev libngtcp2-crypto-ossl-devPrerequisites on macOS:
$ brew install libgee json-glib libsoup libnice capstoneFor a higher level view of the internals, check out the architecture diagram and its links to the different parts of the codebase.