Skip to main content
Press slash or control plus K to focus the search. Use the arrow keys to navigate results and press enter to open a threat.
Reconnecting to live updates…

How (almost) any phone number can be tracked via WhatsApp & Signal – open-source PoC

0
High
Published: Sun Dec 07 2025 (12/07/2025, 16:33:23 UTC)
Source: Reddit NetSec

Description

A side-channel tracking technique leveraging WhatsApp and Signal allows an attacker to infer a target phone's device activity state (screen on/off, offline) by sending silent probe reactions to invalid message IDs and measuring delivery receipt round-trip times. This method does not generate visible notifications or messages on the victim's device, making it stealthy. Over time, attackers can profile user behavior such as when they are home, sleeping, or mobile. The attack requires the ability to send messages to the target number, which can be mitigated by restricting unknown contacts in privacy settings. Although no direct data breach occurs, this privacy-invasive tracking poses significant risks. The threat is relevant to European users given WhatsApp and Signal's widespread adoption. No known exploits in the wild exist yet, but the proof-of-concept is publicly available.

AI-Powered Analysis

AILast updated: 12/07/2025, 16:39:29 UTC

Technical Analysis

This threat exploits a side-channel vulnerability in WhatsApp and Signal messaging platforms, demonstrated through an open-source proof-of-concept called “Careless Whisper.” The attacker uses an unofficial WhatsApp API to send tiny probe reactions to special or invalid message IDs. Although these probes do not produce visible messages or notifications on the victim’s device, WhatsApp still returns silent delivery receipts. By measuring the round-trip time (RTT) of these receipts, the attacker can infer the device’s activity state: low RTT indicates the screen is on and active (often on Wi-Fi), higher RTTs correspond to screen on with mobile data, and very high RTTs or timeouts indicate the device is offline or in standby. This timing side-channel allows an attacker to build a behavioral profile of the target, such as typical home presence, sleep patterns, and mobility. The same class of leak exists for Signal, as noted in the original research paper. The attack’s stealthiness stems from the absence of any visible interaction on the victim’s side and the use of silent delivery receipts. However, the attack requires the ability to send messages or reactions to the victim’s phone number, which can be limited via privacy settings. The technique may be detectable through unusual network traffic patterns and causes slight additional battery and data usage on the victim device. The open-source PoC and the original academic paper provide detailed technical insights, but no known active exploitation campaigns have been reported. This vulnerability highlights a privacy risk rather than a direct compromise of message content or device integrity.

Potential Impact

For European organizations and individuals, this threat primarily impacts privacy and operational security rather than direct system compromise. The ability to remotely and covertly track device activity states can enable adversaries to infer sensitive behavioral patterns, such as when employees or key personnel are likely at home, asleep, or traveling. This could facilitate targeted social engineering, physical surveillance, or timing of attacks to coincide with periods of reduced vigilance. Organizations relying on WhatsApp or Signal for secure communications may face increased risks of metadata leakage, undermining confidentiality assurances. Privacy-conscious sectors such as government, defense, legal, and finance could be particularly affected. Additionally, the stealthy nature of the attack complicates detection and response. While no direct data breach or remote code execution is involved, the erosion of privacy and potential for profiling represents a significant threat vector in the European context, where data protection regulations like GDPR emphasize user privacy. The attack also raises concerns about the security of widely used encrypted messaging platforms and their metadata handling.

Mitigation Recommendations

European organizations and users should immediately review and tighten privacy settings on WhatsApp and Signal to restrict or block messages from unknown numbers, effectively preventing unsolicited probes. Specifically, in WhatsApp, navigate to Settings → Privacy → Advanced and disable or limit message reception from unknown contacts. Organizations should educate employees about this threat and encourage cautious sharing of phone numbers. Network monitoring tools can be configured to detect unusual, repetitive probe-like traffic patterns targeting messaging services, aiding early detection. Where possible, use alternative communication channels with stronger metadata protection or enterprise-secured messaging platforms. Developers and platform providers should be urged to address this side-channel by modifying delivery receipt behaviors or implementing rate limiting on reactions to invalid message IDs. Regular audits of messaging app permissions and network activity on corporate devices can help identify anomalous behavior. Finally, organizations should incorporate this threat into their privacy risk assessments and incident response plans, emphasizing metadata leakage risks.

Need more detailed analysis?Get Pro

Technical Details

Source Type
reddit
Subreddit
netsec
Reddit Score
2
Discussion Level
minimal
Content Source
reddit_link_post
Domain
arxiv.org
Newsworthiness Assessment
{"score":39.2,"reasons":["external_link","newsworthy_keywords:rce,hacked,hotfix","established_author","very_recent"],"isNewsworthy":true,"foundNewsworthy":["rce","hacked","hotfix","ttps"],"foundNonNewsworthy":[]}
Has External Source
true
Trusted Domain
false

Threat ID: 6935adb3551a24bb8cca3466

Added to database: 12/7/2025, 4:39:15 PM

Last enriched: 12/7/2025, 4:39:29 PM

Last updated: 12/8/2025, 3:51:17 AM

Views: 35

Community Reviews

0 reviews

Crowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.

Sort by
Loading community insights…

Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.

Actions

PRO

Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.

Please log in to the Console to use AI analysis features.

Need enhanced features?

Contact root@offseq.com for Pro access with improved analysis and higher rate limits.

Latest Threats