EFForg/rayhunter

New criterions and features

Open

#534 opened on Aug 11, 2025

View on GitHub
 (3 comments) (0 reactions) (0 assignees)Rust (431 forks)github user discovery
Research Questionsenhancementhelp wantedheuristicunplanned

Repository metrics

Stars
 (5,271 stars)
PR merge metrics
 (PR metrics pending)

Description

What problem does this feature solve or what does it enhance?

Criterion system and alert notification.

Proposed Solution

  1. Implement device screen flickering, which immediately attracts the user attention instead of pressing the button and looking the alerts in the past.

  2. Implement new criterions: "Suspicious LAC change detected" When the device is stationary and placed not on the edge on different LAC areas (the rare case), monitoring the LAC value change is a simple and effective way to detect Stingray, which is known for attracting UE by exploiting LAU procedure.

"Empty neighbors in SIB3 and SIB5" Stingray should not translate this info to prevent UE freely camping on that cells and leaving Stingray BTS.

  1. Implement new mode called "Under surveillance" criterions: "Empty Paging" Similar to the Snoopsnitch criterion, when the personal Paging message is detected and not followed by any service (incoming call, sms, data) it looks like a SS7 tracing procedure.

"Silent SMS" SMS Type 0, as stated at 3GPP docs, and it's variants.

"Location Protocols usage" Detect any usage of RRLP and LPP requests, which are used by network to pinpoint device location.

  1. Implement the weight system for all criterions, so that alert is thrown only after the desired threshold. This gives the ability to minimize false positives by tuning the system response.

Alternatives Considered

No response

Contributor guide