MESH
Open sourceActive
Two documentation pages at v0.2.1-beta (overview/platform-support and setup/endpoint-client) describe a 'public alpha', and setup/endpoint-client says the app is not on Google Play or F-Droid, while the README calls the project public beta and shows Google Play and F-Droid badges. This entry reports each page as stated. The main branch is 12 commits ahead of v0.2.1-beta (dependency bumps, rootless Podman support, exit-node fixes, two docs pages); the README is identical at the tag and on main, and docs claims here cite the tag.
MESH is a self-hostable, encrypted peer-to-peer overlay network from the non-profit BARGHEST, built to give an analyst a network path to a remote phone for ADB wireless debugging, network monitoring and logical acquisition. The README states it is not itself the acquisition tool and bundles AndroidQF and MVT for that. It is in public beta, and the documentation lists Android as the only supported endpoint, with iOS planned.
Facts
| Website | barghest.asia |
|---|---|
| Vendor | BARGHEST (non-profit, UK-registered) and contributors |
| Licence | Open source (AGPL-3.0-or-later (README; the LICENSE file is the GNU Affero General Public License v3). Contains derivative code from Tailscale (BSD-3-Clause) and AmneziaWG/WireGuard (MIT).) |
| Category | Utilities and libraries |
| Functions | Acquisition |
| Targets | Android |
| Runs on | Linux, macOS, Windows |
| Pricing | Free (open source, self-hosted); the README says the Automatic-domain setup needs an API key provided by the BARGHEST team on request [github.com] |
| Users | Civil society, Research, Open-source DFIR community |
| Last activity | 2026-10-22 · Latest commit on main; latest release v0.2.1-beta published 2026-09-17 [github.com] |
| GitHub activity | BARGHEST-ngo/MESH · 210 stars · last push 2026-11-10 · latest release v0.2.1-beta (2026-09-17) · checked 2026-11-10 |
Capabilities
- The README describes MESH as a networking tool that supports remote logical forensic acquisition on mobile devices: it gives analysts an encrypted path to devices for wireless debugging, network monitoring and acquisition, including devices behind NAT, firewalls or restrictive mobile networks, without port forwarding or central VPN servers. [github.com]
- The README states transport is WireGuard peer to peer where a path exists, with optional AmneziaWG obfuscation against deep packet inspection and automatic fallback to encrypted HTTPS relays when UDP is blocked; meshes are described as ephemeral and analyst-controlled, to be torn down after collection. [github.com]
- The README lists remote network monitoring with PCAP capture and Suricata intrusion detection over the mesh, and running WARD, MVT, AndroidQF and other ADB tooling against a remote device as if it were local. [github.com]
- The features page says AndroidQF collection is built into the analyst command-line client and that MVT is installed in the analyst container; Android access is through ADB over Wi-Fi to a mesh address. [github.com]
- The acquisitions guide says the analyst container stores evidence in one bind-mounted host directory, so collected files appear on the host immediately. [github.com]
- The BARGHEST home page describes MESH as 'consent-based remote evidence collection' for cases where an investigator cannot reach the device, designed to be self-hosted by the communities using it. [barghest.asia]
- The use-cases page gives a remote-forensics scenario in which the device holder installs the MESH app and enables ADB over Wi-Fi on their own device before the investigator connects. [github.com]
Limitations
- The README states MESH provides the networking for remote acquisition but is not the acquisition tool; AndroidQF and MVT are included in the suite for that. [github.com]
- The README labels the project public beta, says breaking changes should be expected and that it currently requires some technical expertise, and lists Docker Engine with Compose V2 and go-task as prerequisites. [github.com]
- The README warns that the default ACL lets nodes in each network talk to each other and that production deployments should use restrictive policies. [github.com]
- The platform-support page lists the endpoint client as Android 8.0 and later only, with an iOS endpoint client planned for Q4 2026. [github.com]
- The features page says libimobiledevice integration is planned and not yet installed, although the README lists libimobiledevice compatibility. [github.com]
- The features page marks AmneziaWG obfuscation as still in development. [github.com]
Links
Related tools
- androidqf · Acquisition
- MVT · Spyware detection
- ADB · Acquisition
- libimobiledevice · Utilities and libraries
Sources
- MESH README (v0.2.1-beta; identical on main) (github.com)
- MESH LICENSE (GNU AGPL v3) (github.com)
- MESH docs: features (github.com)
- MESH docs: platform support (github.com)
- MESH docs: use cases (github.com)
- MESH docs: acquisitions and evidence handling (github.com)
- MESH docs: endpoint client setup (github.com)
- BARGHEST home page (barghest.asia)
- MESH documentation site (docs.meshforensics.org)
- MESH releases (github.com)
- MESH commits on main (github.com)
- MESH docs: About (non-profit company limited by guarantee registered in the United Kingdom) (github.com)
Reviewed . Spotted an error? See the corrections policy.