Rayhunter
v0.13.0 open-sourceFree plan: not checked yet · Open source: yes
The section your link pointed to isn't on Rayhunter's page any more, so we've brought you to the top.
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.
rayhunter check --json
rayhunter install --data-dir /custom/path
curl -s -o /dev/null -w '%{http_code}' http://<uz801-ip>/status
rayhunter orbic-network --admin-password <your_admin_password>
curl -sSL http://<rayhunter-host>:<port>/zip -o captures.zip
rayhunter-check --pcapify
What you can do now
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
Languages
Command line
No command matches.
| option | found in | since | description |
|---|
Values are placeholders taken from each option’s declared default. Nothing is executed here — the output shown is a recording of a run that already happened.
Score card
-
Shipping velocity releases a month, last 12 months
-
Documentation quality release-notes rubric, 0–100
-
Breaking-change discipline how rarely a release breaks users, and notice given
-
Maintenance risk quiet time against its own cadence, maintainers
-
Innovation & surface new capabilities, API and MCP surface
- Community health
-
Contributor trend distinct committers, this year against last
-
Maintainer concentration bus factor now against a year ago
-
Issue backlog trend issues closed per issue opened, 12 months
-
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 → Already subscribed? Sign in →Trajectory
Blank means never measured; nothing here is a filled-in zero.
Peer standings are included with Researcher and Business. See how this tool ranks against its competitors, using data we don't publish anywhere else.
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…
Releases
22 entries
No entries match these filters.
- September 20261
- August 20261
- May 20262
- February 20262
- January 20261
- November 20251
- October 20251
- September 20251
- August 20252
- July 20251
- June 20251
- May 20253
- April 20251
- March 20251
- January 20251
- December 20241
- October 20241
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.
- Contributors 37 −5 vs prior 12 months
- Maintainers 4 +3 joined · −5 left, last 12 months
- Bus factor 2 committers behind half the commits
- Community-filed 75% of issues opened, last 12 months
- Median time to close 20 days first maintainer reply 11 hours
- Open backlog 92 of 407 issues ever filed
- Issues opened / month 1 · 0 communitymaintainers
- Open backlog 92
- Contributors / month 0
- Commits / month 0
- Stars not measured
- 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.