Find your next open-source project

Search by name, purpose, or keyword — or paste a GitHub repository URL

firerpa/lamda

Security & Privacy

An Android device control platform for remote access, UI automation, traffic capture, Frida hooking and multi-device operations.

8,745
1,188
Python
MIT
4 years old

What It Is

FIRERPA is an Android full-stack device control platform. A service runs directly on the Android device, and a Python client on the PC drives it through one API. The project targets teams that need repeatable remote control, UI automation, traffic capture, Frida-based reverse engineering, and multi-device orchestration, instead of stitching together Appium, mitmproxy, frida-server, adb, uiautomator2 and separate scripts.

Main capabilities include browser-based remote desktop over WebRTC/H.264/MJPEG, selector-based UI automation with virtual displays, Watchers, OCR and image matching, one-click MITM capture with automatic CA installation, a bundled Frida environment, device-side proxy/VPN/frp/P2P networking, built-in ADB/SSH/terminal, an MCP server and a natural-language agent command.

Getting Started

  1. Install the on-device service using one of the documented options: one-click app (root or Shizuku), Magisk module autostart, manual extraction, or ROM integration. Android 6.0+ is listed as supported, with both root and non-root modes.
  2. Open the device WebUI to check the service is running and, if needed, configure ports, certificates and services through the INI configuration or visual editor.
  3. On the PC, install the Python client (Python 3.6+ is the stated requirement), connect to the device, and exercise the API, for example to list devices or control an app.
  4. Open the remote desktop from a browser to view and control the screen, inspect the layout tree, and start automation or capture work.

Exact installation commands, package names, client setup steps and API call examples are not included in the provided README. Use the English documentation or Chinese documentation for the concrete install and client usage instructions; the repository is the distribution point for builds and source.

Constraints

  • Device-side service and PC-side client are separate components; the PC needs a compatible Python environment (3.6+ stated), and the device must run Android 6.0 or later.
  • Several functions are privileged: system CA installation, SELinux changes, writing ro.* properties and some silent permission operations require an appropriate root or shell identity. The project claims root and non-root modes, but not every feature is available without privileges.
  • Frida, MITM, ADB and system-modification features are intended for security testing, reverse engineering and controlled device management; using them on devices or applications without authorization may violate policies or law.
  • Remote desktop and RPC can use end-to-end TLS and certificate access control, but public-network exposure should be configured deliberately, including optional WebUI login passwords and allow_origin settings.
  • Distributed networking options include a subscription service, self-hosted frp, and OpenVPN mesh; these have different hosting and configuration requirements.

HotRepo's Take

This repository has no recorded GitHub daily-rank, snapshot, star-curve or Hacker News discussion data in the provided HotRepo records, so there is no station-side trend or ranking evidence to add. The useful observation is scope: the project is not a single automation library but a bundled Android control stack, and its value depends on whether a team needs several of these capabilities together. For narrow tasks such as basic UI scripting alone, a lighter tool may be easier to adopt; for multi-device security testing, traffic capture and remote operations in one pipeline, the integrated design is the differentiator to evaluate.

Written by AI from the project's README, updated . The project's own docs are the source of truth.