Encrypted peer-to-peer mesh VPN for remote mobile forensics, enabling wireless ADB and libimobiledevice acquisition, network monitoring, and intrusion detection across NAT and firewalls.
MESHforensics enables internet-routable wireless debugging for mobile devices over an encrypted, censorship-resistant peer-to-peer mesh network.
Mobile devices are often trapped behind NAT, firewalls, or restrictive carrier networks that block direct inbound access. MESHforensics creates an encrypted peer-to-peer overlay and assigns each node a CGNAT-range address via a virtual TUN interface, so devices behave as if they share a private subnet, with no central VPN, port forwarding, or permanent infrastructure.
This lets analysts run remote mobile forensics over ADB Wireless Debugging and libimobiledevice, using tools like WARD, MVT, and AndroidQF as if the device were local. MESHforensics also supports remote network monitoring, including PCAP capture and Suricata intrusion detection over the same mesh.
Meshes are ephemeral and analyst-controlled: bring devices online, collect, then tear the network down, so nothing is left running to fingerprint.
[!IMPORTANT] Public Beta: under active development. A full penetration test has been completed and major vulnerabilities patched. Breaking changes should be expected, and some technical expertise is required. Report bugs or security concerns via GitHub Issues.
Full documentation: https://docs.meshforensics.org/
Clone the repo first:
git clone https://github.com/BARGHEST-ngo/mesh.git
cd MESH
Then pick how your control plane is reached from the internet.
Run the control plane on your workstation and expose it through the MESHforensics provisioner, a hosted reverse-proxy tunnel. Request a provisioner API key from BARGHEST (see https://docs.meshforensics.org/). The provisioner auto-assigns an ephemeral *.tunnels.meshforensics.app subdomain and issues your API credentials, so task apikey is not needed on this path.
# Choose the "Ephemeral" control plane when prompted
task build
task controlPlane
# Open the web UI at the provisioner-assigned URL and log in
Bring your own ingress (a reverse proxy on an internet-facing server, or a tunneling service such as Cloudflare Tunnel or ngrok), then mint an API key locally.
# Choose the "Persistent" control plane when prompted, and your own domain
# (or the hostname your Cloudflare Tunnel / ngrok endpoint provides)
task build
task controlPlane
task apikey
# Open the web UI and log in with the API key
# Local: https://localhost
# Remote: https://your-domain:8443/login
The web UI uses a self-signed certificate by default. Once logged in, your MESHforensics network is ready to accept nodes. See the docs for node enrollment and forensic workflows.
[!IMPORTANT] The default ACL lets all nodes in a network talk to each other. Production deployments should use restrictive policies, set via the ACL tab.
MESHforensics is a heavily modified fork of Tailscale that does not require Tailscale infrastructure. Peers connect directly via end-to-end encrypted WireGuard using UDP hole punching. When UDP is blocked, traffic fails over to E2EE HTTPS DERP relays, which transport packets without visibility into their contents.
The control plane handles only peer discovery and key exchange, and forensic traffic flows directly between endpoints whenever possible. Operators can run their own DERP servers (the control plane embeds an implementation), making MESHforensics fully self-hostable. Otherwise it falls back to Tailscale's public DERP servers for connectivity.
MESHforensics is built on WireGuard, but a plain WireGuard VPN is the wrong shape for hostile networks. WireGuard speaks only UDP, and UDP is exactly what censored and restrictive carrier networks degrade or block first. When that happens a raw WireGuard tunnel simply fails, which is unacceptable when an analyst needs to reach a device in the field.
MESHforensics keeps WireGuard for its fast, modern, end-to-end encrypted transport, then adds the connectivity WireGuard lacks on its own. Peers attempt a direct UDP connection via hole punching, and when UDP is blocked they fail over to end-to-end encrypted HTTPS DERP relays. HTTPS relaying is the critical piece: it is indistinguishable from ordinary web traffic, so it survives DPI and UDP censorship that would strand a conventional VPN, while the relay still carries packets without visibility into their contents.
Traditional VPN and hub-and-spoke designs also add persistent infrastructure risk, centralized traffic-analysis points, single points of failure, and operational exposure. MESHforensics separates coordination from transport. The control plane carries no forensic traffic, peer connections are direct, relays are fallbacks rather than hubs, and meshes are disposable and task-scoped. It is optimized for transient, high-risk environments rather than permanent enterprise networking.
android-client: Android endpoint APKcontrol-plane: Coordination serveranalyst: Analyst CLI clientmesh-analyst-client.main.
MESHforensics is supported by the Open Technology Fund to support the consensual remote forensics of spyware and surveillance targeting Human Right Defenders.
MESHforensics is licensed under the GNU Affero General Public License v3.0 or later (AGPL-3.0-or-later). All modifications and additions by BARGHEST are Copyright (c) BARGHEST.