Fake Signal Support Is Asking Activists for Their Backup Key

Signal's encryption hasn't been broken. The attackers don't need to break it. A new wave of phishing messages, surfaced over May 27 and 28, 2026, asks targets to hand over the one piece of cryptographic material Signal has explicitly said it cannot recover for them: the recovery key for the Secure Backup Archive. Once that key is in attacker hands, every backed-up message—every chat, every photo, every member of every group—can be downloaded from Signal's servers and decrypted offline. The cryptography held. The user got phished.

Key Takeaways

• The phishing wave was first surfaced publicly by Washington Post columnist Josh Rogin on May 27, 2026. By May 28, multiple anti-CCP activists and at least two Access Now Helpline clients had reported the same lure.
• The fake "Signal Support" message warns the target their backed-up chats and media are "at risk of permanent loss due to a sync issue" and asks them to paste their backup recovery key into the chat to "relink" the backup.
• The recovery key encrypts every message and attachment in Signal's Secure Backup Archive. Per Signal: "Without your unique recovery key, no one (including Signal) can read, decrypt, or restore any of the data in your Secure Backup Archive." Hand it over and an attacker can pull the full archive from Signal's servers.
• Signal president Meredith Whittaker said on the record that Signal is "working on mitigations here, and monitoring." Signal had already publicly warned about this exact attack pattern in April 2026, stating it "will never reach out" to users first.
• The lure is engineered for political targets but is being reused against journalists, NGO staff, and dissidents in multiple countries—not only Chinese activists. Anyone with a high-threat threat model and Signal backups enabled is in scope.

What Does the Recovery Key Actually Protect?

Signal's Secure Backup Archive is the optional cloud-backup feature Signal rolled out as an alternative to the older device-local backups. With backups enabled, Signal encrypts the user's messages and attachments on the device, uploads the ciphertext to Signal's servers, and gives the user a recovery key. That key is the only thing that turns the ciphertext back into readable messages. Signal does not store it. Signal does not have a recovery flow for it. Lose it and the archive is irrecoverable. Hand it to an attacker and the archive is theirs.

That asymmetry is the entire reason the phishing works. There is no "log me in" attack against the backup feature—the attacker either steals the recovery key or gives up. Because the key is alphanumeric and the user has been told to "keep it somewhere safe," a believable Signal Support agent asking the user to copy and paste it into a chat sounds like a routine service interaction.

How Does the Phishing Message Look?

Per TechCrunch's reporting and the screenshots shared by Rogin, the lure follows a tight script:

• Inbound message from a contact identifying as "Signal Support."
• Opening line warns that backups are at risk due to a "sync issue."
• Instructs the target to open Settings → Chats → Chat Backups → Recovery Key.
• Asks the target to copy the visible recovery key and paste it into the chat to "relink your existing backup to your account."
• Concludes with a soft urgency push: "Failure to do this may result in losing access to your account and all stored data."

The lure is plain text, no links, no attachments—which means email and link-scanning defenses don't help. The trust is built entirely from the sender label and the routine, technical-sounding instructions.

Who Is Being Targeted?

The first cluster of reports came from anti-Chinese Communist Party activists in the United States and abroad—exactly the demographic the Chinese state has previously targeted with commercial spyware operations. Two additional victims who contacted Access Now's Digital Security Helpline were not Chinese activists, which suggests either multiple groups reusing the same script or a single operator with a broader victim list.

This is the same victim class spyware operators target with Pegasus, Predator, and Graphite—journalists, exiled dissidents, NGO staff, lawyers representing political targets. The difference is the cost. A Pegasus license runs hundreds of thousands of dollars. A phishing script that asks for a backup recovery key costs nothing to deploy, and the only thing it needs to defeat is the user's caution.

How Is This Different From the QR Code Signal Attack?

A separate Signal-targeting campaign from earlier this month attributed to Russian state actors abused Signal's "linked device" QR code flow to silently mirror messages to an attacker-controlled second device. That attack reads new messages going forward without ever needing the encryption keys. The May 28 campaign is the inverse—it reads the historical archive but doesn't give the attacker a live tap.

Both bypass Signal's end-to-end encryption by going around it rather than through it. The cryptography is irrelevant when the attacker can convince the user to paste the key into a chat or scan a QR code that pairs a stranger's device. For a high-threat user, the implication is that "I use Signal" is not a complete answer to "are my messages safe." The two attacks together build a fairly complete surveillance picture: the QR code attack captures the present, the recovery-key attack captures the past.

What Should Signal Users Do This Week?

Four concrete steps for anyone with a meaningful threat model:

1. Never share your Signal backup recovery key with anyone, ever, including someone identifying as Signal Support. Signal has stated, on the record and in advance, that it will never ask for it. Anyone who asks is an attacker.
2. Check Settings → Privacy → Linked Devices. If there is a linked device you did not authorize, unlink it immediately. This is the surface the separate Russian-attributed campaign abused.
3. Decide whether Secure Backup is worth the risk for your threat model. The feature exists because most users want chat continuity across phone replacements. Activists, journalists, and dissidents may be better served keeping backups off entirely and accepting the loss of history when devices change.
4. Treat unsolicited inbound messages from "Signal Support" as adversarial by default. Confirm any operational support request through Signal's published support pages, not through a chat thread.

For journalists and NGOs operating across email and Signal in parallel, the operational threat is no longer the cryptography of any one channel. It is the cumulative attack surface across all of them. Tracking pixels in the email inbox confirm an address is live; phishing on Signal confirms an account is reachable. Gblock closes the email-side telemetry leak by stripping invisible tracking pixels in Gmail, removing one of the cheapest reconnaissance inputs an operator like the one running this Signal campaign uses to build a victim list.

What Happens Next?

Meredith Whittaker has said Signal is working on mitigations. The realistic options are limited: Signal can ship clearer in-app warnings on the recovery key screen ("Anyone who asks for this is impersonating us"), it can add a delay or a second factor before backups can be reactivated from a new device using the key, or it can rate-limit backup download attempts. None of those changes the underlying truth—if the user shares the key, the attacker has the archive.

For the rest of the secure messaging ecosystem, the May 28 campaign is a preview. WhatsApp, iMessage, and Telegram all have variants of the "cloud backup" pattern where a recovery secret unlocks a server-side archive. Every one of those products is now in the same threat surface. The Signal users got hit first because they are the highest-value targets.