Skip to main content

Possible SS7 + WhatsApp metadata surveillance – need expert input

High
Published: Fri Sep 05 2025 (09/05/2025, 18:54:35 UTC)
Source: Reddit NetSec

Description

Hi everyone, I’ve been a victim of targeted cyberstalking for years and I need to share my experience to understand if what happened to me points to SS7 abuse alone, or if there had to be someone with privileged access inside Meta (WhatsApp). Here are the facts: • I used two numbers: • One SIM only for data. • A different number for WhatsApp, but the SIM itself was not in the phone (still active with the carrier, not blocked). • I was never disconnected from my WhatsApp. • This means my account was never fully cloned using SS7 (since that would disconnect me). • Still, my stalkers somehow knew all the new contacts I talked to on WhatsApp, including people I met on Tinder. • They didn’t know those numbers beforehand. • So simple correlation at the carrier level seems impossible. • My suspicion: 1. They were using SS7 for surveillance (location, SMS interception, monitoring my SIM’s traffic patterns). 2. At the same time, they had access to WhatsApp metadata (number A ↔ number B, timestamps). • This would explain how they knew all my new contacts, without prior knowledge of their numbers. • Important detail: • I always had 2FA (PIN) enabled. • I even tested registering my number on another phone, intercepted the SMS, but without the PIN the session never completed. • Despite that, I once saw real messages appear on the second phone — which left me wondering about some kind of “silent pre-login” bug. ⸻ My questions for the community: 1. Is it technically possible to access WhatsApp metadata (who talks to who) without insider or official Meta access? 2. Could SS7 + carrier-level monitoring alone explain how they mapped all my new contacts? 3. Have there been documented cases of “silent pre-login” where WhatsApp sessions were duplicated without disconnecting the victim? 4. From a defense standpoint, am I correct that moving to Signal (with usernames) and Session fully mitigates this kind of metadata exposure? ⸻ I’d really appreciate insights from anyone who works with telecom security, SS7, or has deep knowledge of WhatsApp’s metadata handling. Thanks for reading.

AI-Powered Analysis

AILast updated: 09/05/2025, 19:58:15 UTC

Technical Analysis

This report describes a complex surveillance scenario involving potential abuse of the SS7 (Signaling System No. 7) telecommunications protocol combined with unauthorized access to WhatsApp metadata. SS7 is a set of protocols used by telecom operators worldwide to manage signaling and control of phone calls and SMS. It is known to have vulnerabilities that allow attackers with network access to intercept SMS messages, track location, and manipulate calls. The victim used two separate phone numbers: one SIM dedicated to data and another number for WhatsApp, with the WhatsApp SIM not physically present in the phone but still active. Despite no session cloning or disconnection occurring (which would typically happen if SS7 was used to clone the WhatsApp session), the attackers somehow obtained detailed metadata about the victim’s WhatsApp contacts, including newly added contacts unknown to the attackers beforehand. This suggests that SS7 abuse alone cannot fully explain the surveillance. The victim suspects a combination of SS7-based carrier-level monitoring (for location, SMS interception, and traffic patterns) and insider or privileged access to WhatsApp metadata (such as contact mappings and timestamps) within Meta. The victim also observed anomalous behavior resembling a “silent pre-login” where messages appeared on a second device without the victim’s session being disconnected, hinting at a possible WhatsApp client or server-side vulnerability allowing session duplication without triggering standard security controls. The victim had 2FA enabled, which prevented full session hijacking, but did not prevent metadata leakage or partial session duplication. The questions raised include whether WhatsApp metadata can be accessed without insider access, if SS7 alone can explain the contact mapping, documented cases of silent pre-login or session duplication without disconnect, and whether switching to privacy-focused messaging apps like Signal or Session (which use usernames and stronger metadata protections) would mitigate such risks. Overall, this case highlights the intersection of telecom protocol vulnerabilities and potential insider threats or advanced exploitation of messaging platform metadata, raising concerns about metadata privacy and the limits of current security controls in widely used encrypted messaging services.

Potential Impact

For European organizations, this threat poses significant privacy and security risks, especially for high-profile individuals, journalists, activists, and corporate executives who rely on WhatsApp for confidential communications. The ability to correlate metadata across telecom and messaging platforms can reveal social graphs, communication patterns, and potentially sensitive relationships without decrypting message content. This undermines confidentiality and can facilitate targeted cyberstalking, corporate espionage, or state-sponsored surveillance. The risk is amplified in Europe due to strict data protection regulations (e.g., GDPR) and the high adoption rate of WhatsApp as a primary communication tool. Organizations may face reputational damage and regulatory penalties if employee or executive communications are compromised. Additionally, the possibility of session duplication without user notification threatens the integrity of user sessions and trust in messaging platforms. The combination of SS7 vulnerabilities and potential insider access to metadata creates a complex threat landscape that is difficult to detect and mitigate using traditional security measures. This could lead to long-term exposure of sensitive metadata, enabling persistent surveillance and profiling.

Mitigation Recommendations

1. Telecom operators and regulators in Europe should accelerate the deployment of SS7 security enhancements such as Diameter protocol for LTE networks, SS7 firewalls, and anomaly detection systems to prevent unauthorized signaling access. 2. Organizations should educate users about the risks of SS7-based attacks and encourage the use of encrypted messaging apps that minimize metadata exposure, such as Signal or Session, which use privacy-preserving protocols and usernames instead of phone numbers. 3. Enable all available security features on WhatsApp, including two-factor authentication and security notifications for new device logins, and monitor for suspicious session activity. 4. Advocate for transparency and stronger metadata protection from messaging service providers, including audits and independent verification of insider access controls. 5. For high-risk individuals, consider using separate devices and SIMs for sensitive communications and avoid linking personal phone numbers to messaging accounts. 6. Implement network-level monitoring for unusual signaling traffic patterns indicative of SS7 abuse. 7. Engage with telecom providers to understand and limit metadata sharing and access within their infrastructure. 8. Encourage European regulatory bodies to mandate stricter controls on telecom signaling protocols and require messaging platforms to minimize metadata retention and access.

Need more detailed analysis?Get Pro

Technical Details

Source Type
reddit
Subreddit
netsec
Reddit Score
0
Discussion Level
low
Content Source
reddit_link_post
Domain
privacyaffairs.com
Newsworthiness Assessment
{"score":23,"reasons":["external_link","newsworthy_keywords:rce","non_newsworthy_keywords:question,meta,community","established_author","recent_news"],"isNewsworthy":true,"foundNewsworthy":["rce"],"foundNonNewsworthy":["question","meta","community"]}
Has External Source
true
Trusted Domain
false

Threat ID: 68bb40c1535f4a97730de680

Added to database: 9/5/2025, 7:57:53 PM

Last enriched: 9/5/2025, 7:58:15 PM

Last updated: 9/5/2025, 7:58:15 PM

Views: 1

Actions

PRO

Updates to AI analysis are available only with a Pro account. Contact root@offseq.com for access.

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