# Signal 'Secure Backups' Recovery-Key Phishing — Coordinated Campaign Impersonating Signal Support to Steal Backup Recovery Keys from Journalists, Dissidents & Activists (2026)

> A coordinated social-engineering campaign impersonates 'Signal Support' to trick high-risk users into disclosing the 64-character recovery key that protects Signal Secure Backups. Combined with secondary account/device access, the stolen key lets attackers download and decrypt the victim's entire encrypted message history from Signal's servers. Access Now's Digital Security Helpline confirmed journalists, dissidents, and activists — including anti-CCP activists — are being disproportionately targeted.

- **Published:** 2026-06-01T00:00:00Z
- **Last reviewed:** 2026-06-01T00:00:00Z
- **Canonical:** https://intel.threadlinqs.com/threat/TL-2026-0637
- **Card image:** https://intel.threadlinqs.com/og/threat/threat-intel-signal-secure-backups-phishing-tl-2026-0637.webp?v=9d6920eb (Threadlinqs threat intel: Signal Support Impersonation Phishing: Detection & IOCs (TL-2026-0637) — High severity, 12 IOCs, 9 detection rules.)
- **ID:** TL-2026-0637
- **Severity:** HIGH
- **Category:** PHISHING
- **Status:** ACTIVE
- **Detections:** 9 (1 shown free below) · **IOCs:** 12

## Description

In late May 2026 a coordinated phishing campaign began targeting Signal users with messages impersonating 'Signal Support.' The lure claims the victim's account data is 'at risk of permanent loss due to a sync issue' and instructs the victim to retrieve their 64-character Signal recovery key from the app and paste it into the chat to 'resolve' the problem. The campaign was first publicly flagged on 2026-05-27 by Washington Post analyst Josh Rogin, who posted a screenshot on X/Twitter and noted that many anti-CCP activists had received the message. Access Now's Digital Security Helpline — which investigates cyberattacks against journalists, dissidents, and human-rights activists — independently confirmed the targeting; its director Mohammed Al-Maskati reported that two separate victims submitted near-identical phishing messages, indicating a coordinated operation rather than opportunistic spam, and that targets were not exclusively Chinese activists, suggesting the campaign may be more widespread.

The asset at risk is Signal Secure Backups, a zero-knowledge backup system that stores doubly-encrypted message archives on Signal's servers. Backups are encrypted end-to-end and then again with a backup-specific key, with padding added to obscure file sizes and prevent metadata correlation. The 64-character recovery key is generated on-device, is the sole credential capable of unlocking the backup, and — by design — never leaves the device and is never transmitted to Signal's servers. Because the key is the only thing that can decrypt the archive, its disclosure is catastrophic.

The attack is a two-step compromise chain. Step one is the recovery-key theft via the impersonation phish. Step two, per Malwarebytes, requires the attacker to also gain access to the victim's Signal account (e.g., by linking a secondary/attacker-controlled device). With both the recovery key and account/device access, the attacker can download and decrypt the full message history — not just future messages, but everything stored in the backup. Malwarebytes characterizes obtaining the key as 'a critical first move in a chain that can lead to total account compromise,' and notes this is even more damaging than a simple account hijack (which would only yield future messages). View-once messages and messages set to disappear within 24 hours are excluded from backups and therefore not exposed.

Signal has publicly responded. President Meredith Whittaker stated the team is 'working on mitigations here, and monitoring.' Signal's standing guidance is unambiguous: Signal will never proactively reach out to users first and will never request registration codes, PINs, or recovery keys. The in-app phishing messages also surface a 'Name not verified' label beneath the unknown sender, a key user-visible red flag. No IOCs (IPs, domains, file hashes, or attacker account identifiers) and no threat-actor attribution have been published in the source reporting. The strong skew toward journalists, dissidents, and anti-CCP activists is consistent with an espionage/surveillance-motivated operator, but no formal attribution exists; attribution confidence is LOW.

## MITRE ATT&CK

- T1589 Gather Victim Identity Information
- T1598 Phishing for Information
- T1566 Phishing
- T1684.001 Impersonation
- T1098 Account Manipulation
- T1606 Forge Web Credentials
- T1530 Data from Cloud Storage
- T1567 Exfiltration Over Web Service

## Free detection (Splunk SPL, Microsoft KQL, Sigma)

**Signal Support Impersonation Lure & Recovery-Key Disclosure — Exploitation Phase** (`TL-2026-0637-SPL-001`)

Detects the TL-2026-0637 'Signal Support' impersonation phishing lure and/or disclosure of a 64-character Signal recovery key in monitored chat/DLP content. Keys on the verbatim sync-issue / data-loss lure phrasing and the request to paste the recovery key into chat — Signal never messages users first or asks for recovery keys.

- **Languages:** Splunk SPL, Microsoft KQL, Sigma
- **ATT&CK:** T1566.003, T1656, T1598.001
- **Data sources:** dlp, casb, signal_desktop_logs
- **Severity:** high
- **Confidence:** high

### Splunk SPL

```spl
`comment("TL-2026-0637 Exploitation: Signal Support impersonation lure + recovery-key disclosure in monitored chat/DLP content")`
index=dlp sourcetype="dlp:endpoint:content" (application="Signal" OR channel="messaging" OR file_name="*signal*")
| eval lure_hit=if(match(content, "(?i)at risk of permanent loss due to a sync issue|Paste the key into this chat|This links your existing backup to your account"), 1, 0)
| eval key_hit=if(match(content, "(?i)recovery key") AND match(content, "[A-Za-z0-9]{64}"), 1, 0)
| where lure_hit=1 OR key_hit=1
| stats count min(_time) as first_seen max(_time) as last_seen values(user) as users values(host) as hosts by application, channel
| where count > 0
```

### Microsoft KQL

```kql
CloudAppEvents
| where Timestamp > ago(24h)
| where Application has "Signal"
| extend Body = tostring(RawEventData.Content)
| where Body has_any ("at risk of permanent loss due to a sync issue", "Paste the key into this chat", "This links your existing backup to your account")
    or (Body has "recovery key" and Body matches regex "[A-Za-z0-9]{64}")
| project Timestamp, AccountDisplayName, Application, IPAddress, Body
```

### Sigma

```yaml
title: Signal Support Impersonation Recovery-Key Phishing Lure
id: 0637d001-1a2b-4c3d-8e4f-000000000101
status: experimental
description: Detects the verbatim 'Signal Support' recovery-key phishing lure (TL-2026-0637) in monitored chat/DLP content.
references:
    - https://www.malwarebytes.com/blog/news/2026/05/signal-users-targeted-in-backup-stealing-phishing-attacks
    - https://techcrunch.com/2026/05/28/hackers-are-trying-to-steal-signal-users-backups-in-new-wave-of-phishing-attacks/
author: Threadlinqs Team
date: 2026/06/01
tags:
    - attack.initial-access
    - attack.t1566.003
    - attack.t1656
    - attack.reconnaissance
    - attack.t1598.001
logsource:
    category: file_event
    product: dlp
detection:
    selection_lure:
        Content|contains:
            - 'at risk of permanent loss due to a sync issue'
            - 'Paste the key into this chat'
            - 'This links your existing backup to your account'
    selection_key:
        Content|contains: 'recovery key'
        Content|re: '[A-Za-z0-9]{64}'
    condition: selection_lure or selection_key
falsepositives:
    - Security-awareness training material that quotes the lure verbatim
    - Incident-response notes or threat-intel reports pasted into a monitored channel
level: high
```

**Known false positives:**

- Security-awareness training content quoting the lure verbatim
- Threat-intel or IR reports containing the lure text pasted into a monitored channel

**Tuning notes:** Exclude known security-awareness and IR channels/distribution lists. Tighten the 64-char regex to Signal's recovery-key alphabet to cut overlap with API tokens/hashes. Pair lure_hit with key_hit (both in the same conversation within 1h) to raise confidence.

### 8 more detection rules (Splunk SPL, Microsoft KQL, Sigma), unlock with TL Creds

- 64-Character Signal Recovery Key Disclosed in Chat — Exploitation Phase (locked: unlock with TL Creds)
- Foreign Process Accessing Signal Linked-Device / Message Store — Post-Exploitation Phase (locked: unlock with TL Creds)
- Secure Backup Read Followed by Outbound Exfil — C2/Lateral Movement Phase (locked: unlock with TL Creds)
- Signal Support First-Contact Impersonation — Exploitation Phase (locked: unlock with TL Creds)
- Unrecognized Signal Linked Device Registered — Post-Exploitation Phase (locked: unlock with TL Creds)
- Secure Backup Exfiltration Over Web Service — C2/Lateral Movement Phase (locked: unlock with TL Creds)
- Rogue Signal Linked-Device Registration — Post-Exploitation Phase (locked: unlock with TL Creds)
- Bulk Secure Backup Retrieval & Web-Service Exfil — C2/Lateral Movement Phase (locked: unlock with TL Creds)

Sign up free to unlock the detection rules: https://threadlinqs.com/?modal=signup

## Sources

- [Hackers Attacking Signal Users to Steal Backups in New Wave of Attacks](https://cybersecuritynews.com/hackers-attacking-signal-users/)
- [Hackers are trying to steal Signal users' backups in new wave of phishing attacks](https://techcrunch.com/2026/05/28/hackers-are-trying-to-steal-signal-users-backups-in-new-wave-of-phishing-attacks/)
- [Signal users targeted in backup-stealing phishing attacks](https://www.malwarebytes.com/blog/news/2026/05/signal-users-targeted-in-backup-stealing-phishing-attacks)
- [Signal Phishing Campaign Targets Journalists and Activists to Steal Backup Recovery Keys](https://securityaffairs.com/192899/security/signal-phishing-campaign-targets-journalists-and-activists-to-steal-backup-recovery-keys.html)
- [Signal users targeted by attackers seeking backup recovery keys](https://cyberinsider.com/signal-users-targeted-by-attackers-seeking-backup-recovery-keys/)
- [Signal Secure Backups — Recovery Key & Zero-Knowledge Encryption](https://signal.org/blog/introducing-secure-backups/)

## Full data

The other 8 detection rules (Splunk SPL / Microsoft KQL / Sigma) unlock with TL Creds; a free account includes daily creds: https://threadlinqs.com/?modal=signup
Indicator values unlock with TL Creds, at a lower price on Red and Purple; AI agents can query rules and IOCs through the Threadlinqs MCP server (Purple): https://intel.threadlinqs.com/mcp

Canonical: https://intel.threadlinqs.com/threat/TL-2026-0637
