PAGES
← all tools
◆ Hacking Hardware

Rayhunter

v0.13.0 open-source

Free plan: not checked yet · Open source: yes

A tool that detects cell site simulators (IMSIIMSIA unique 15-digit number that globally identifies a subscriber on a cellular network, stored on the SIM card. Cyber tools target or capture it to track devices or correlate identities across mobile networks. catchers) on a cheap mobile hotspot.

What you can do now

Checking Plays…

Summary

Rayhunter is an open-source detection tool, free to use, that runs on a cheap mobile hotspot device (originally the Orbic RC400L, with community support extended to others) to catch IMSI catchers, also known as cell-site simulators or stingrays. Rather than a piece of software you install on a laptop or phone, it lives on dedicated hardware you carry with you, flagging suspicious cellular behavior as it happens. It's built by EFF with non-technical users explicitly in mind, so it suits privacy-conscious individuals and activists as much as security researchers, not just specialists comfortable with radio-frequency tooling. It sits in the cell-site simulator detection space, a category with few accessible, low-cost options outside law enforcement and research circles. Launched in 2023 and still active, with its most recent release only nine days old.

A tool that detects cell site simulators (IMSI catchers) on a cheap mobile hotspot.

How Rayhunter helps

Is my cellular connection being intercepted by a fake cell tower right now?

it watches the traffic passing through the hotspot as you carry it and flags patterns consistent with a cell-site simulator while you're connected to a given cell, rather than after the fact

Which cell tower my phone just connected to behaved suspiciously?

it logs the cellular behavior it observed for that connection so you can review what triggered a flag and when it happened

Was I near a stingray at some point today without noticing?

it runs continuously in the background on the carried device, so a review of its captured session shows any suspicious behavior recorded across the whole time it was on

Can I trust a flagged event to mean real surveillance rather than a glitch?

it's built to minimize false positives, so a flag is meant to be a stronger signal than raw cellular oddities, though it doesn't claim certainty about who is behind the behavior

Do I need radio-frequency expertise to tell if something suspicious happened?

it presents its findings in a form meant for non-technical users, so reading a flagged event doesn't require RF or telecom background

all 13 features, with the evidence for each →

Languages

Not documented

Features

13 capabilities · 1 backed by code, an API document or a real run

Built from Rayhunter's releases, docs, README and our own runs. “Seen” marks the month we first spotted a release the vendor didn't date. Group names and tags are our labels.

Compare with peers →

What Rayhunter offers you

  • Command-line interface5
  • JSON data export1
  • Web management console1
All capabilities 13 capabilities
IMSI catcher detection shipped Detects IMSI catchers (cell-site simulators/stingrays) by running on a mobile hotspot device. 11 releases · 3 other sources · first seen Oct 2024

release 11 total

  • Re-enables the RRCConnectionRelease classifier for detection coverage. v0.13.0 · Sep 2026 · source · release history
  • Reads the home PLMN from the SIM card to improve accuracy of the imsi_requested heuristic. v0.13.0 · Sep 2026 · source · release history
  • The firewall feature has been removed v0.11.0 · May 2026 · source · release history
  • UI now differentiates warning severity levels visually v0.6.0 · Aug 2025 · source · release history
  • uz801 added as a supported device profile v0.6.0 · Aug 2025 · source · release history
  • New Reanalyze button in the UI to re-run analysis on old recordings v0.6.0 · Aug 2025 · source · release history

docs

  • Detects IMSI catchers (cell-site simulators/stingrays) by running on a mobile hotspot device.

example

  • Use the new Reanalyze button in the UI to re-analyze existing recordings without restarting the capture process. In the rayhunter UI, select a recording and click the 'Reanalyze' button. v0.6.0 · Aug 2025 · source
  • Trigger on-demand analysis for previous recordings via the UI to review past heuristic triggers. In the Rayhunter console, navigate to the recordings list and select 'On-demand analysis' for a past run. v0.2.0 · Oct 2024 · source
UI Diagnostics and Management shipped View system errors, logs, and configuration options directly within the web interface. 9 releases · 4 other sources · first seen Dec 2024

Also counts toward: Web management console

release 9 total

example

  • Reduce noise in your analysis by viewing only runs that triggered warnings. In the Rayhunter web UI, apply the 'warnings' filter to the run list. v0.7.0 · Sep 2025 · source
  • Inspect diagnostic information directly in the browser without using tail or copying logs. In the Rayhunter web UI, navigate to the Log Viewer section to view real-time logs. v0.7.0 · Sep 2025 · source
  • Check recent runtime errors captured by the daemon via the browser interface. Navigate to the Daemon Web UI and select the 'Errors' view/tab v0.6.1 · Aug 2025 · source
  • Remove old recordings directly from the web interface. In the web UI, locate the 'delete buttons' next to your recording entries and click them. v0.2.8 · Apr 2025 · source
Installation Simplification shipped Provide simplified installation methods including graphical installers and custom directory options. 6 releases · 1 other source · first seen May 2025

Also counts toward: Command-line interface

release

  • Adds a graphical installer-gui frontend (MVP) so users can install Rayhunter without the command line. v0.13.0 · Sep 2026 · source · release history
  • Exposes CLI help text and default values inside the installer GUI. v0.13.0 · Sep 2026 · source · release history
  • Adds --data-dir parameter to control the installation directory (defaulting to /cache/rayhunter-data for tplink devices). v0.10.2 · Feb 2026 · source · release history
  • Adds a gui installer framework to simplify desktop installation workflows. v0.9.0 · Jan 2026 · source · release history
  • Captures and displays mount logs during the rayhunter installer process. v0.9.0 · Jan 2026 · source · release history
  • Introduces a new Rust-based installer that supports both TP-Link and Orbic devices across all supported platforms v0.3.0 · May 2025 · source · release history

example

  • Install Rayhunter to a specific custom data directory instead of the default location. rayhunter install --data-dir /custom/path v0.10.2 · Feb 2026 · source
Offline Data Export shipped Export captured cellular data for offline analysis in standard formats. 5 releases · 2 other sources · first seen Jan 2025

Also counts toward: Command-line interface

release

  • Include ndjson in ZIP download v0.13.0 · Sep 2026 · source · release history
  • Includes NDJSON alongside existing files in the ZIP download from the daemon.⁠︀︄︇︀︅︉︀︅︀︀︃︀︀︅︅︀︅︊︀︄︆︀︃︄⁠ v0.13.0 · Sep 2026 · source · release history
  • Adds a GET /zip endpoint (and corresponding UI button) to download QMDL and PCAP files as a single archive v0.4.0 · Jun 2025 · source · release history
  • Adds --inbound and --outbound flags to the --nas option to specify direction for NAS heuristics. v0.2.4 · Jan 2025 · source · release history
  • Adds --pcapify flag to rayhunter-check command to export captured data as PCAP file. v0.2.4 · Jan 2025 · source · release history

example

  • Programmatically retrieve captured QMDL and PCAP files as a zip archive via the API. curl -sSL http://<rayhunter-host>:<port>/zip -o captures.zip v0.4.0 · Jun 2025 · source
  • Export captured data for offline analysis in a standard packet capture format. rayhunter-check --pcapify v0.2.4 · Jan 2025 · source
Hotspot Hardware Support shipped Support for various mobile hotspot devices including TP-Link, Orbic, Wingtech, and Uz801. 7 releases · first seen Apr 2025

release 7 total

  • Implements battery level reading support for TP-Link M7350 modems (v4-v6) in Rayhunter's cellular data monitoring v0.7.1 · Oct 2025 · source · release history
  • Adds support for the Wingtech CT2MHS01 hotspot hardware v0.4.0 · Jun 2025 · source · release history
  • TP-Link hardware compatibility updated with added windows instructions v0.3.1 · May 2025 · source · release history
  • Adds full device support for the TP-Link M7350 hotspot (EU and other regions) v0.3.0 · May 2025 · source · release history
  • Introduces a new Rust-based installer that supports both TP-Link and Orbic devices across all supported platforms v0.3.0 · May 2025 · source · release history
  • Update rayhunter_daemon for TPLINK Compatibility v0.2.8 · Apr 2025 · source · release history
Remote Device Management shipped Capabilities to manage the hotspot device's network settings, status, and configuration remotely. 4 releases · 2 other sources · first seen May 2025

Also counts toward: Command-line interface

release

  • Adds HTTP GET-based device online check for Uz801 devices v0.8.0 · Nov 2025 · source · release history
  • Implements battery level reading support for TP-Link M7350 modems (v4-v6) in Rayhunter's cellular data monitoring v0.7.1 · Oct 2025 · source · release history
  • Adds --admin-password argument to the orbic-network installer for configuring modem admin credentials without interactive prompts v0.7.1 · Oct 2025 · source · release history
  • Add installer util shell command to get shell on orbic v0.3.2 · May 2025 · source · release history

example

  • Check if an Uz801 modem is responding on the network before attempting further actions. curl -s -o /dev/null -w '%{http_code}' http://<uz801-ip>/status v0.8.0 · Nov 2025 · source
  • Run the orbic-network installer with a specific admin password to automate device setup. rayhunter orbic-network --admin-password <your_admin_password> v0.7.1 · Oct 2025 · source
Automated Notifications shipped Deliver real-time push notifications via ntfy.sh for alerts, updates, and diagnostics. 5 releases · first seen Aug 2025

release

  • Makes ntfy_url configurable (nullable) for ntfy notification endpoint v0.11.2 · May 2026 · source · release history
  • Adds software update notifications in the web UI and via ntfy when a new Rayhunter release is available v0.11.2 · May 2026 · source · release history
  • Adds a Test button to the Notification Settings UI for verifying notification delivery. v0.10.0 · Feb 2026 · source · release history
  • notifications for low battery level over ntfy (for users with an active sim plan) v0.7.0 · Sep 2025 · source · release history
  • Integration with ntfy.sh to deliver push notifications from rayhunter v0.6.0 · Aug 2025 · source · release history
Heuristic Analysis Features shipped Detect specific cellular security events and protocol anomalies using advanced heuristics. 4 releases · first seen Dec 2024

release

  • Adds an option to disable or autofix clock drift warnings in the daemon. v0.13.0 · Sep 2026 · source · release history
  • Read the home PLMN from the SIM for the imsi_requested heuristic v0.13.0 · Sep 2026 · source · release history
  • Adds a no-NAS analyzer and a corresponding UI alert to flag when NAS (Non-Access Stratum) traffic is absent. v0.13.0 · Sep 2026 · source · release history
  • Removes the false positive IMSI heuristic from detection logic v0.2.3 · Dec 2024 · source · release history
Configuration Management shipped Control analyzer behavior and device settings via configuration files and UI. 3 releases · first seen Jan 2025

Also counts toward: Command-line interface

release

  • Add option to disable or autofix clock drift warnings v0.13.0 · Sep 2026 · source · release history
  • Allows enabling or disabling analyzers via the configuration file rather than the UI alone v0.4.0 · Jun 2025 · source · release history
  • Adds --inbound and --outbound flags to the --nas option to specify direction for NAS heuristics. v0.2.4 · Jan 2025 · source · release history
Programmatic Analysis Output verified Export analysis results in JSON format for programmatic consumption and automated processing. 1 release · 2 other sources · first seen Aug 2026

Also counts toward: Command-line interface, JSON data export

release

  • check subcommand now supports --json flag to output results in JSON format instead of text v0.12.0 · Aug 2026 · source · release history

command line

example

  • Parse check results programmatically for automated analysis rayhunter check --json v0.12.0 · Aug 2026 · source
Automated Backups shipped Automatic upload of captured recordings to a remote WebDAV server. 1 release · first seen May 2026

release

  • Automatic recordings upload to a WebDAV server using the webdav integration (e.g., for syncing to ownCloud) v0.11.0 · May 2026 · source · release history
Client Mode Operation shipped Allow the tool to connect as a WiFi client on a local network without requiring a SIM data plan. 1 release · first seen May 2026

release

  • client_mode allows connecting orbic and moxee devices as a wifi client on the local network to receive push notifications without a data plan v0.11.0 · May 2026 · source · release history
macOS Build Support shipped Provides pre-compiled release artifacts for both Intel and Apple Silicon macOS architectures. 1 release · first seen Mar 2025

release

  • Builds macOS Intel release artifacts alongside Apple Silicon builds v0.2.6 · Mar 2025 · source · release history

Lines in monospace are the tool's own words: help text parsed from its source, or an endpoint from its API document. Under release, a line is our summary of a dated release. Under docs, it is quoted from the tool's own documentation or website. Each links back to the source it came from.

Score card

  1. Shipping velocity releases a month, last 12 months
  2. Documentation quality release-notes rubric, 0–100
  3. Breaking-change discipline how rarely a release breaks users, and notice given
  4. Maintenance risk quiet time against its own cadence, maintainers
  5. Innovation & surface new capabilities, API and MCP surface
  6. Community health
  7. Contributor trend distinct committers, this year against last
  8. Maintainer concentration bus factor now against a year ago
  9. Issue backlog trend issues closed per issue opened, 12 months
  10. Responsiveness median time to a maintainer’s first reply

Nine scores for Rayhunter, each built from the releases, notes and API history this site tracks — and, on Researcher and Business, where it stands among every measured tool in its category and how that has moved.

Score cards are part of every paid plan.

See plans →

Each score is 0–100 on a published rubric, derived from data this site already shows. A dimension we cannot measure says so — it is never scored 0 and never enters a rank.

How this is scored
  • Shipping velocity — releases a month over the last 12 months, on a log scale where 16 a month scores 100. Needs 3 releases in the window.
  • Documentation quality — the release-notes rubric published on the analytics page, unchanged.
  • Breaking-change discipline — the share of releases carrying a breaking change (none scores 100, half or more scores 0). Only projects that label breaking changes are measured: a clean record cannot be told from an unlabelled one.
  • Maintenance risk — quiet time measured against the tool's own release cadence (quiet longer than 90 days and three typical gaps scores 0), plus the number of active maintainers and whether contributors are growing, where known. Higher is lower risk.
  • Innovation & surface — new capabilities in the feature ledger this year, API and MCP operations added, and the share of commits that are features: the mean of whichever we hold.
  • Community health (open-source tools only) — each is a direction, not a size: contributors this year against last, the bus factor now against a year ago, and issues closed per issue opened, where steady scores 50, doubled 100 and halved 0; plus the median time to a maintainer's first reply (an hour scores about 100, a month or more 0). A commercial card has no repository and carries none of the four.
  • Documented delivery (commercial tools) — when a vendor's documented new capabilities have slowed against its own baseline, that counts against the overall standing as heavily as two low dimensions. Steady delivery, or too little history to judge, leaves the standing alone; it is never a sixth score.
  • Open-source tools are scored on repository signals; commercial tools on their published changelog. Ranks compare tools within one category and one profile and need at least five measured peers; the overall standing needs three ranked dimensions. Best-in-breed or consolidator is a shape, not a quality, and is never scored.

Release-note detail over time

See how much detail Rayhunter puts in its release notes, quarter by quarter, and compare it with tracked tools in the same category. This history uses up to ten retained, reviewed notes per tool; sparse or blank older quarters may reflect that limit.

Checking release-note history…

Explore the full chart →

Releases

Show

22 entries

  1. September 20261
  2. August 20261
  3. May 20262
  4. February 20262
  5. January 20261
  6. November 20251
  7. October 20251
  8. September 20251
  9. August 20252
  10. July 20251
  11. June 20251
  12. May 20253
  13. April 20251
  14. March 20251
  15. January 20251
  16. December 20241
  17. October 20241
    Show

    22 entries

    Project health

    Issue, contributor and maintainer activity in EFForg/rayhunter, 2023-12 – 2026-11, as of 2026-11-03. Twelve-month figures first; the trend lines run the whole window.

    1. Contributors 37 −5 vs prior 12 months
    2. Maintainers 4 +3 joined · −5 left, last 12 months
    3. Bus factor 2 committers behind half the commits
    4. Community-filed 75% of issues opened, last 12 months
    5. Median time to close 20 days first maintainer reply 11 hours
    6. Open backlog 92 of 407 issues ever filed
    1. Issues opened / month 1 · 0 communitymaintainers
    2. Open backlog 92
    3. Contributors / month 0
    4. Commits / month 0
    5. Stars not measured
    Issue themes, last 12 months
    • bugs 50%
    • features 35%
    • questions 1%
    • docs 1%
    • other 13%

    Counts from the project's public repository and git history; no individuals are identified. Maintainers are the committers covering 80% of the last year's commits. how we measure this

    Libraries its release ships

    What its latest release locks, checked against known advisories.

    None of its release's images build from a lockfile we can read.

    Add the badge to your README

    Maintain this project? The badge links readers straight to this page, so they can follow every release here.

    Tracked by Cyber Toolchain Choose a badge style and copy the code →
    Saved in this browser. Sign in to sync your tools.