EFForg/rayhunter

LPP heuristic

Open

#1,072 opened on Jun 22, 2026

View on GitHubContributor guide
 (1 comment) (0 reactions) (0 assignees)Rust (465 forks)github user discovery
enhancementgood first issueheuristic

Repository metrics

Stars
 (5,521 stars)
PR merge metrics
 (Avg merge 5d 12h) (6 merged PRs in 30d)

Description

Prerequisites

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

User jamyla posted on the community mattermost about an IMSI catcher that uses LPP to track UE location. Reporting LPP messages has been previously suggested in #534, but as far as I know nobody's tried it out. This seems like an interesting heuristic to add, even if only in an informational (as opposed to a warning) capacity.

Proposed Solution

Implement an informational heuristic that tracks LTE LPP messages, both the request and the response.

Alternatives Considered

No response

Contributor guide

Research direction
Study the LPP message format and implement an informational heuristic in the Rust decoder to track both LPP requests and responses.
Tech stack
rust
Domain
mobile devsecuritynetworking
Issue type
Feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
2
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
Half day
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
GitRust
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
65