WhatsApp and Signal leak your daily routine to anyone with your number

10.09.2026 7 min 4

Your messages in WhatsApp and Signal are encrypted and nobody outside the chat reads them. That part works. What still leaks is the small grey tick that says a message arrived: it comes back at a measurable speed, and that speed says whether your screen is on, whether you are on Wi-Fi or mobile data, how many devices you have and when you go to sleep. Anyone who knows your phone number can collect it, and you get no notification at all.

In short

  • Delivery receipts are sent automatically and cannot be turned off by the user. Read receipts are a different setting and do not help here.
  • Specially crafted messages trigger a receipt without ever showing up in your chat list, so the probing is invisible.
  • The round-trip time of that receipt reveals screen on or off, network changes, how many devices are logged in and their operating system.
  • The one real defence today is to stop strangers reaching you by number: Signal has that setting, WhatsApp is rolling out usernames worldwide from September 2026.

How a tick becomes a tracker

Researchers at the University of Vienna and SBA Research published the mechanism in a paper called Careless Whisper. The idea is short enough to explain in four lines.

  1. The attacker sends your number a message that the app processes but never displays, such as a reaction pointing at a message ID that does not exist.
  2. Your phone decrypts it, decides there is nothing to show, and dutifully sends back a delivery receipt anyway.
  3. The attacker measures how long that receipt took to come back.
  4. Repeat every fraction of a second and the timings draw a graph of your day.

Nothing appears on your screen. No notification, no new chat, no unread badge. The paper compares it to a stealth SMS, the technique police use to locate a handset without the owner noticing.

What the timings give away

A phone with the screen on answers faster than one lying face down on a table. A phone on Wi-Fi answers differently from the same phone on mobile data. A desktop client that just came online answers on its own. From that the researchers reconstructed screen-on time to the second, working routines, commuting, and the number of devices logged into the account together with which operating system each one runs.

The same channel works as a weapon rather than a sensor. Because the probing messages can carry arbitrary payload, the team measured what happens when you send big ones continuously.

13.3 GBof traffic per hour pushed at a victim through WhatsApp from a single session
18%battery drained per hour on an iPhone 11, against under 1% idle
50 msshortest probe interval WhatsApp allowed without rate limiting
3 bnusers of the two affected messengers

On Signal the picture is milder. Short bursts go through, but sending several messages a second runs into limits, and the team could not meaningfully drain a test phone's battery. The tracking side channel still works there; the resource exhaustion does not.

What this is not: nobody is reading your messages. End-to-end encryption is intact and the content stays private. What leaks is metadata, the timing around the message rather than the message. Metadata is often treated as the harmless part, and a graph of when someone sleeps, wakes and leaves the house is a good argument that it is not.

Threema behaved differently

The researchers tested three messengers. Threema handles receipts restrictively enough that silent probing does not work: the only way a stranger can trigger anything is to send a normal text message and start a visible conversation, which is the opposite of stealthy. That matters because it shows this is a design decision, not a law of physics. WhatsApp and Signal answer strangers by default; Threema does not.

What the vendors did about it

  1. The researchers report the findings to the security contacts at both Meta and the Signal Foundation.
  2. Meta confirms receipt and says the report went to the development team. No substantive answer follows.
  3. Nearly a year later, Meta again tells the researchers the report has been forwarded to engineering.
  4. No reply at all, according to the paper.

The paper lists fixes that would close it: stop sending receipts to numbers that are not in a conversation, let privacy-minded users switch instant receipts off, add a little random delay to receipt timings, and validate referenced message IDs instead of acknowledging nonsense. None of those has shipped as a protocol change. In December 2025 someone published a working proof of concept on GitHub that turns the technique into a dashboard, which is where most people first heard about it. The underlying behaviour has not changed since.

The number is the weak point

Every version of this attack starts the same way: the attacker types in a phone number. That is also the finding of a second study from the same Vienna group, presented at NDSS 2026, which showed that WhatsApp's contact discovery could be queried at more than 100 million numbers per hour and confirmed 3.5 billion live accounts across 245 countries. Meta has since mitigated that one. The lesson survives the fix: on both platforms your phone number is the address, the login and the search key at once.

What you can actually do today

Worth doing

  • Signal: Settings, Privacy, Phone Number, Who can find me by my number, set to Nobody. A stranger who types your number then cannot message you or even see that you use Signal.
  • Signal: create a username in Settings, Profile, and share that instead of your number.
  • WhatsApp: reserve a username in Settings, Account, Username. The feature started rolling out in July 2026 and is reaching the rest of the world from September.
  • WhatsApp: turn on Settings, Privacy, Advanced, Block unknown account messages. It only reacts to high volume, so treat it as a speed bump rather than a fix.

Does not help

  • Turning off read receipts. Delivery receipts are a separate mechanism and stay on.
  • A VPN. The receipt is generated by your phone, and its timing barely moves whatever route the traffic takes.
  • Blocking one number after the fact. The attacker never appears in your chat list, so there is nothing to block.
  • Airplane mode as a habit. Being offline is itself a data point in the graph.

Usernames are the part worth acting on. They do not patch the side channel, but they take away the thing the attack needs. If nobody outside your contacts can reach you by number, nobody outside your contacts can ping you for timings either.

Can I tell whether someone is doing this to me?
Not from the app. There is no notification and no chat entry. Testers who ran the public proof of concept noticed unexpected battery drain and mobile data spikes, and that is the only symptom on the phone.
Does this break encryption?
No. The content of messages stays encrypted and unreadable. The leak is in the timing of the automatic confirmation your app sends back.
Can I turn off delivery receipts?
Not in WhatsApp or Signal. The setting you can turn off is read receipts, the second blue tick, which is a different thing. Delivery receipts are part of the protocol and the researchers explicitly asked both vendors to make them optional.
Am I safer on Signal than on WhatsApp?
Somewhat. Signal's rate limits blunt the high-frequency probing and the battery drain, and Signal has shipped the setting that stops strangers finding you by number. The timing side channel itself is present in both.
Would a VPN hide me here?
No. Your device answers automatically and the interesting signal is how fast it answers, not where the traffic went. A VPN adds a little latency and no protection against this.

whatsappsignalthreemametaprivacytrackingsurveillancee2eeencryptioncybersecurity

Read also