Skip to navigation

Threat reportPhishingTL-2026-0637

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

highACTIVE

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.

Key facts

IdentifiersTL-2026-0637
Also known asSignal Secure Backups Recovery-Key Phishing, Signal Support Impersonation Campaign, Signal Backup-Stealing Phishing Wave
SeverityHIGH
Affected productsSignal Foundation Signal Private Messenger (Secure Backups feature)
Weaknesses (CWE)CWE-1391, CWE-522
MITRE ATT&CK techniquesT1098 Account Manipulation, T1530 Data from Cloud Storage, T1566 Phishing, T1567 Exfiltration Over Web Service, T1589 Gather Victim Identity Information, T1598 Phishing for Information, T1606 Forge Web Credentials, T1684.001 Impersonation
MotivationESPIONAGE
Target sectorsmedia, journalism, civil-society, human-rights, ngo, political-dissidents, activism
Target regionsGlobal, North America, Asia, Europe
Detection rules9 (1 shown free)
Sources6 cited sources

Detection coverage

As of 2026-06-01, Threadlinqs Intelligence publishes 9 detection rule(s) for TL-2026-0637 across Splunk SPL, Microsoft KQL and Sigma, covering 12 indicator(s) of compromise. The whole corpus is readable without an account. Every threat comes with one complete detection in Splunk SPL, Microsoft KQL and Sigma, free for everyone; a free account adds daily TL Creds to unlock the rest. Paid plans add a larger daily allowance, correlation and the MCP server. Threadlinqs MCP server · View plans.

Free detection: Signal Support Impersonation Lure & Recovery-Key Disclosure — Exploitation Phase

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

`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

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

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. Sign up free to unlock the detection rules or query them with the Threadlinqs MCP server (Purple)
  • 64-Character Signal Recovery Key Disclosed in Chat — Exploitation Phase · unlock with TL Creds
  • Foreign Process Accessing Signal Linked-Device / Message Store — Post-Exploitation Phase · unlock with TL Creds
  • Secure Backup Read Followed by Outbound Exfil — C2/Lateral Movement Phase · unlock with TL Creds
  • Signal Support First-Contact Impersonation — Exploitation Phase · unlock with TL Creds
  • Unrecognized Signal Linked Device Registered — Post-Exploitation Phase · unlock with TL Creds
  • Secure Backup Exfiltration Over Web Service — C2/Lateral Movement Phase · unlock with TL Creds
  • Rogue Signal Linked-Device Registration — Post-Exploitation Phase · unlock with TL Creds
  • Bulk Secure Backup Retrieval & Web-Service Exfil — C2/Lateral Movement Phase · unlock with TL Creds

Indicators of compromise

As of 2026-06-01, Threadlinqs Intelligence tracks 12 indicators of compromise for TL-2026-0637.

12 indicators of compromise · unlock with TL Creds. Compare plans

Technical analysis

Access Now's Digital Security Helpline confirmed journalists, dissidents, and activists — including anti-CCP activists — are being disproportionately targeted.

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 techniques by tactic:

Persistence

T1098 Account Manipulation

Collection

T1530 Data from Cloud Storage

Initial Access

T1566 Phishing

Exfiltration

T1567 Exfiltration Over Web Service

Reconnaissance

T1589 Gather Victim Identity Information; T1598 Phishing for Information

Credential Access

T1606 Forge Web Credentials

Defense Evasion

T1684.001 Impersonation

Remediation

Immediate actions

  • Never share your Signal recovery key, PIN, or registration code with anyone — Signal never asks for them and never messages users first
  • Treat any inbound message claiming to be 'Signal Support' as fraudulent; verify the 'Name not verified' label under unknown senders
  • If you already pasted your recovery key, immediately rotate/regenerate the backup recovery key and review linked devices in Signal Settings > Linked Devices, removing any unrecognized device
  • Enable Registration Lock (Settings > Account > Registration Lock) to block attacker re-registration/relinking of your number

Workarounds

  • Consider not enabling Secure Backups, or disabling it, if the threat model does not justify server-side archive storage
  • Disable message preview and restrict who can message you to reduce unsolicited contact

Longer-term hardening

  • Enable device-change and linked-device alerts and review linked devices periodically
  • Use disappearing messages by default to minimize the volume of history retained in any backup
  • Store recovery keys/PINs only in a reputable password manager, never in plaintext or in any chat
  • For high-risk users (journalists, activists, dissidents), conduct periodic security checkups with organizations such as Access Now's Digital Security Helpline

Affected and fixed versions

  • Signal Foundation — Signal Private Messenger (Secure Backups feature)
    Vulnerable versions: All versions with Secure Backups enabled (Android, iOS, Desktop)
    Fixed in: N/A — social-engineering campaign, no software fix; mitigations and user awareness

Timeline

  • Signal launches Secure Backups: zero-knowledge, doubly-encrypted message archives stored on Signal servers, unlockable only by an on-device 64-character recovery key that never leaves the device.
  • Washington Post analyst Josh Rogin posts a screenshot on X/Twitter flagging the in-app phishing message and noting many anti-CCP activists received it.
  • Signal President Meredith Whittaker states the team is 'working on mitigations here, and monitoring.'
  • TechCrunch reports the campaign; Access Now Digital Security Helpline director Mohammed Al-Maskati confirms two victims submitted near-identical messages and that targeting is not exclusively Chinese activists.
  • Malwarebytes publishes technical analysis detailing the verbatim lure, the two-step recovery-key + account-access chain, and defensive guidance (registration lock, linked-device review).
  • Security Affairs and additional outlets corroborate the coordinated targeting of journalists, dissidents, and activists.
  • Cyber Security News reports an ongoing 'new wave' of attacks; campaign assessed ACTIVE with no published IOCs or attribution.

Sources cited

Previous and next in phishing

Drafted by the Threadlinqs research pipeline from 6 sources; published ; last updated —.

Threadlinqs Intelligence — Real-Time Threat Detection Platform

// threat_feed
$ sort --newest
Showing all threats

Live intelligence console

Threat level

Latest Threats