%3Aquality(100)&w=640&q=75){kind=logo}
Russian Intelligence Services Exploit Signal's Consumer Backup Model to Access Encrypted Message Archives of High-Value Government Targets
STATUS: Active. No indication activities have stopped or been disrupted. SEVERITY: 9/10 AUDIENCE: Government, Defense, Critical Infrastructure Security Leads
Jul 29, 2026
·Blog
·Secure Communications
%3Aquality(100)&w=3840&q=75)
The FBI and CISA published a public service advisory on June 26, 2026, naming Russian Intelligence Services groups in an escalating campaign against government and military Signal users.¹ On June 30, 2026, the U.S. Department of State also announced a reward of up to $10 million for information on the group.² The attackers are not breaking encryption. They are social-engineering users into handing over the 64-character Backup Recovery Key that decrypts their entire message archive — persistently, across device changes, and across new accounts.
What This Attack Is Doing — and Why It Works
The FBI and CISA first warned of Russian intelligence targeting commercial messaging applications in March 2026. The June 26 update represents a qualitative escalation in the campaign's objective. Earlier waves aimed to hijack active sessions — enough to monitor future messages.¹ The current tactic steals the Signal Backup Recovery Key: a 64-character credential generated on the user's device and never shared with Signal's servers, which unlocks an encrypted backup containing every private and group message ever stored.¹
The attack mechanism is social engineering, not cryptography. One sample phishing message warns users of a sync issue threatening permanent data loss, then instructs them to navigate to Settings, Backups, View Recovery Key and paste the key directly into the chat. A second variant poses as a mandatory two-factor verification rollout.¹ Both exploit urgency and fear to bypass user scepticism. Signal does not contact users inside the app to request verification codes, PINs, or Backup Recovery Keys.¹ No legitimate credential request arrives through a chat message.
FBI/CISA Advisory — June 26, 2026
RIS cyber threat actors continue to masquerade as automated CMA support accounts in updated phishing messages but have evolved their tactics to attempt to elicit victims’ Backup Recovery Keys.¹ If a targeted user provides their Backup Recovery Key, RIS cyber threat actors can view the account’s historical messages, private and group messages, and take over the victim’s account.¹ The actor could potentially use the compromised key to take over the new account in the future as well.¹ — PSA I-062626-PSA
The key keeps working after the victim changes phones. If a target creates a new account on the same phone number, the old recovery key remains valid for that account's future backups.¹ The compromise is therefore not bounded by the incident date — it is persistent until the user generates a new key and accepts that any backup made before that moment is already in the attacker's possession.
What Attackers Gained – And What They Can Do With It
Attacker Gain | What It Enables | Operational Consequence | Post-Compromise Risk |
Signal Backup Recovery Key¹ | Restore the victim's full encrypted message backup onto an attacker-controlled device. | Attacker gains complete visibility into private and group message history without ever breaking Signal's encryption. | Access persists indefinitely — the key remains valid even after the victim replaces their device. |
Impersonated support-channel trust¹ | Walk targets through enabling backups and handing over the recovery key directly; no malware required. | Victims believe they are following legitimate security guidance while handing over standing access. | Repeatable against any target who hasn't been briefed on this specific lure, since no technical exploit is needed. |
Persistent account access¹ | Monitor ongoing communications and historical context, including group chats and contacts. | Sensitive operational, diplomatic, or military context shared in casual conversation becomes exploitable intelligence. | The account keeps working until the key is manually revoked, even after compromise is suspected. |
A confirmed list of high-value targets¹ | Identify which officials, military personnel, or journalists were successfully compromised. | Successful harvests build a target list for follow-on operations beyond the initial account. | The victim's contacts and known associates become easier targets with confirmed access as a foothold. |
Why This Matters
Old Assumption | Current Reality | BlackBerry Response |
Strong encryption makes government use of Signal safe by default. | The account and recovery-key model, not the encryption, is the exploited layer — one social-engineering success grants standing access to the full archive.¹ | BlackBerry® SecuSUITE® removes the self-custodied recovery key entirely; message history is bound to organization-controlled key infrastructure, not an exportable end-user secret. |
A compromised credential is a one-time loss, resolved by replacing the device. | The stolen key remains valid indefinitely, surviving device replacement and new account creation.¹ | Centralized credential revocation and re-issuance under organizational authority closes the persistence gap. |
Consumer app support channels can be trusted at face value. | Attackers impersonate Signal's own automated support system to harvest the key directly from the user.¹ | Closed, certified environment with no consumer-facing support surface to spoof. |
Recommended Actions
IMMEDIATE | Identify any personnel of intelligence value — officials, military, government-facing staff — still using Signal for official business, and inventory their accounts.¹ |
IMMEDIATE | For personnel who cannot migrate immediately, direct them to generate a new Signal Backup Recovery Key now and never share it, per FBI/CISA guidance.¹ |
SHORT-TERM | Migrate high-value personnel to BlackBerry SecuSUITE for official communications, removing dependency on a self-custodied consumer key model. |
SHORT-TERM | Enroll devices in BlackBerry® UEM to enable centralized credential revocation and continuous compliance monitoring going forward. |
ONGOING | Brief personnel on this campaign's specific social-engineering pattern — fake mandatory two-factor rollout messages — so it's recognized before anyone responds.¹ |
Prevention Architecture: Why Commercial Messaging Apps Cannot Solve a Governance Problem
The attack campaign is not a Signal security failure. It is a governance failure: government and military personnel using a consumer messaging application whose backup credential model was designed for individual user convenience, not for enterprise key custody or adversarial operational environments.
The relevant question is not whether to add security features to Signal. It is whether the communications architecture used by government and military personnel should have a consumer account recovery model at all — one where a single social engineering interaction can yield persistent access to an entire message archive.
Structural Gap Exploited the campaign | Why It Cannot Be Patched in Signal | BlackBerry Secure Communications Response |
Consumer backup recovery model allows single credential to unlock entire message archive¹ | Signal’s backup recovery key is a user-controlled credential by design. The convenience feature that makes it valuable to individual users is the same property that makes it exploitable by adversaries. Removing it would break legitimate use. Restricting it requires enterprise governance Signal does not provide. | BlackBerry SecuSUITE has no equivalent consumer backup recovery flow. Enterprise key custody and device provisioning are governed by the organization, not by a self-service app setting. There is no 64-character credential for an adversary to social-engineer, because the architecture does not place that control in the user’s hands. |
No enterprise policy controls over which communications applications personnel can use on managed devices | Signal is a consumer application. It does not integrate with enterprise mobile device management policy in a way that allows organizations to enforce which users can install it, how it is configured, or whether backup features are enabled. | BlackBerry UEM enforces application-layer policy across the managed mobile estate. Organizations can determine which communications applications are permitted, restrict backup features, and ensure that government and military personnel communicate through approved, policy-controlled channels rather than consumer defaults. |
No organizational visibility into whether personnel accounts have been linked to attacker-controlled devices¹ | Signal does not provide enterprise administrators with visibility into linked devices, account recovery events, or backup key generation across their user population. Compromise is invisible until reported by the user. | BlackBerry UEM provides organizational visibility into the managed device estate. Administrators can monitor device compliance, detect unauthorized application installations, and enforce policy changes across the fleet without relying on individual users to self-report compromise. |
Primary crisis communications channel shares infrastructure with the compromised consumer app environment | If Signal is the primary channel for emergency coordination, its compromise — or even justified user uncertainty about whether it has been compromised — degrades the organization’s crisis communications capability at the moment it is most needed. | BlackBerry® AtHoc® operates as an independent, authenticated, federated crisis communications and mass notification platform that does not share infrastructure with consumer messaging applications. When the consumer channel is compromised or suspected compromised, mission-critical coordination continues through the BlackBerry AtHoc platform's out-of-band channel. |
The encryption worked. The architecture failed. An organization whose sensitive government and military communications run through a platform with a consumer key management model has accepted an adversarial attack surface it cannot patch, train, or policy its way out of. The only structural remediation is an architecture that does not place enterprise communications security in the hands of individual users.
BlackBerry Secure Communications Position
Russian intelligence did not break Signal. The encryption worked exactly as designed. The attack targeted the person holding the key, not the cryptography protecting the channel. End-to-end encryption is a transit control. It does not govern how keys are stored, how backup credentials are managed, or how enterprise communications policy is enforced across an organization’s mobile estate. BlackBerry SecuSUITE removes the consumer account recovery model entirely — there is no backup recovery key for an adversary to social-engineer because enterprise key custody and device provisioning are governed by the organization, not by a self-service app setting. BlackBerry UEM enforces the device and application-layer controls that determine which communications channels government and military personnel can use, making the deployment of consumer messaging apps on managed devices a policy decision rather than an uncontrolled default. BlackBerry AtHoc provides the authenticated, federated crisis communications channel that operates independently of consumer messaging infrastructure — when the consumer channel is compromised, mission-critical coordination continues.
Citations:
Russian Intelligence Services Continue to Target Commercial Messaging Applications (Federal Bureau of Investigation (FBI) and Cybersecurity and Infrastructure Security Agency (CISA), Public Service Announcement I-062626-PSA, June 26, 2026).
Rewards for Justice: Information on Russian Cyber Actors Targeting Commercial Messaging Applications (U.S. Department of State, Rewards for Justice Program, June 30, 2026.)
Russian Intelligence Services Exploit Signal's Consumer Backup Model to Access Encrypted Message Archives of High-Value Government Targets
STATUS: Active. No indication activities have stopped or been disrupted. SEVERITY: 9/10 AUDIENCE: Government, Defense, Critical Infrastructure Security Leads
Jul 29, 2026
·Blog
·Secure Communications
The FBI and CISA published a public service advisory on June 26, 2026, naming Russian Intelligence Services groups in an escalating campaign against government and military Signal users.¹ On June 30, 2026, the U.S. Department of State also announced a reward of up to $10 million for information on the group.² The attackers are not breaking encryption. They are social-engineering users into handing over the 64-character Backup Recovery Key that decrypts their entire message archive — persistently, across device changes, and across new accounts.
What This Attack Is Doing — and Why It Works
The FBI and CISA first warned of Russian intelligence targeting commercial messaging applications in March 2026. The June 26 update represents a qualitative escalation in the campaign's objective. Earlier waves aimed to hijack active sessions — enough to monitor future messages.¹ The current tactic steals the Signal Backup Recovery Key: a 64-character credential generated on the user's device and never shared with Signal's servers, which unlocks an encrypted backup containing every private and group message ever stored.¹
The attack mechanism is social engineering, not cryptography. One sample phishing message warns users of a sync issue threatening permanent data loss, then instructs them to navigate to Settings, Backups, View Recovery Key and paste the key directly into the chat. A second variant poses as a mandatory two-factor verification rollout.¹ Both exploit urgency and fear to bypass user scepticism. Signal does not contact users inside the app to request verification codes, PINs, or Backup Recovery Keys.¹ No legitimate credential request arrives through a chat message.
FBI/CISA Advisory — June 26, 2026
RIS cyber threat actors continue to masquerade as automated CMA support accounts in updated phishing messages but have evolved their tactics to attempt to elicit victims’ Backup Recovery Keys.¹ If a targeted user provides their Backup Recovery Key, RIS cyber threat actors can view the account’s historical messages, private and group messages, and take over the victim’s account.¹ The actor could potentially use the compromised key to take over the new account in the future as well.¹ — PSA I-062626-PSA
The key keeps working after the victim changes phones. If a target creates a new account on the same phone number, the old recovery key remains valid for that account's future backups.¹ The compromise is therefore not bounded by the incident date — it is persistent until the user generates a new key and accepts that any backup made before that moment is already in the attacker's possession.
What Attackers Gained – And What They Can Do With It
Attacker Gain | What It Enables | Operational Consequence | Post-Compromise Risk |
Signal Backup Recovery Key¹ | Restore the victim's full encrypted message backup onto an attacker-controlled device. | Attacker gains complete visibility into private and group message history without ever breaking Signal's encryption. | Access persists indefinitely — the key remains valid even after the victim replaces their device. |
Impersonated support-channel trust¹ | Walk targets through enabling backups and handing over the recovery key directly; no malware required. | Victims believe they are following legitimate security guidance while handing over standing access. | Repeatable against any target who hasn't been briefed on this specific lure, since no technical exploit is needed. |
Persistent account access¹ | Monitor ongoing communications and historical context, including group chats and contacts. | Sensitive operational, diplomatic, or military context shared in casual conversation becomes exploitable intelligence. | The account keeps working until the key is manually revoked, even after compromise is suspected. |
A confirmed list of high-value targets¹ | Identify which officials, military personnel, or journalists were successfully compromised. | Successful harvests build a target list for follow-on operations beyond the initial account. | The victim's contacts and known associates become easier targets with confirmed access as a foothold. |
Why This Matters
Old Assumption | Current Reality | BlackBerry Response |
Strong encryption makes government use of Signal safe by default. | The account and recovery-key model, not the encryption, is the exploited layer — one social-engineering success grants standing access to the full archive.¹ | BlackBerry® SecuSUITE® removes the self-custodied recovery key entirely; message history is bound to organization-controlled key infrastructure, not an exportable end-user secret. |
A compromised credential is a one-time loss, resolved by replacing the device. | The stolen key remains valid indefinitely, surviving device replacement and new account creation.¹ | Centralized credential revocation and re-issuance under organizational authority closes the persistence gap. |
Consumer app support channels can be trusted at face value. | Attackers impersonate Signal's own automated support system to harvest the key directly from the user.¹ | Closed, certified environment with no consumer-facing support surface to spoof. |
Recommended Actions
IMMEDIATE | Identify any personnel of intelligence value — officials, military, government-facing staff — still using Signal for official business, and inventory their accounts.¹ |
IMMEDIATE | For personnel who cannot migrate immediately, direct them to generate a new Signal Backup Recovery Key now and never share it, per FBI/CISA guidance.¹ |
SHORT-TERM | Migrate high-value personnel to BlackBerry SecuSUITE for official communications, removing dependency on a self-custodied consumer key model. |
SHORT-TERM | Enroll devices in BlackBerry® UEM to enable centralized credential revocation and continuous compliance monitoring going forward. |
ONGOING | Brief personnel on this campaign's specific social-engineering pattern — fake mandatory two-factor rollout messages — so it's recognized before anyone responds.¹ |
Prevention Architecture: Why Commercial Messaging Apps Cannot Solve a Governance Problem
The attack campaign is not a Signal security failure. It is a governance failure: government and military personnel using a consumer messaging application whose backup credential model was designed for individual user convenience, not for enterprise key custody or adversarial operational environments.
The relevant question is not whether to add security features to Signal. It is whether the communications architecture used by government and military personnel should have a consumer account recovery model at all — one where a single social engineering interaction can yield persistent access to an entire message archive.
Structural Gap Exploited the campaign | Why It Cannot Be Patched in Signal | BlackBerry Secure Communications Response |
Consumer backup recovery model allows single credential to unlock entire message archive¹ | Signal’s backup recovery key is a user-controlled credential by design. The convenience feature that makes it valuable to individual users is the same property that makes it exploitable by adversaries. Removing it would break legitimate use. Restricting it requires enterprise governance Signal does not provide. | BlackBerry SecuSUITE has no equivalent consumer backup recovery flow. Enterprise key custody and device provisioning are governed by the organization, not by a self-service app setting. There is no 64-character credential for an adversary to social-engineer, because the architecture does not place that control in the user’s hands. |
No enterprise policy controls over which communications applications personnel can use on managed devices | Signal is a consumer application. It does not integrate with enterprise mobile device management policy in a way that allows organizations to enforce which users can install it, how it is configured, or whether backup features are enabled. | BlackBerry UEM enforces application-layer policy across the managed mobile estate. Organizations can determine which communications applications are permitted, restrict backup features, and ensure that government and military personnel communicate through approved, policy-controlled channels rather than consumer defaults. |
No organizational visibility into whether personnel accounts have been linked to attacker-controlled devices¹ | Signal does not provide enterprise administrators with visibility into linked devices, account recovery events, or backup key generation across their user population. Compromise is invisible until reported by the user. | BlackBerry UEM provides organizational visibility into the managed device estate. Administrators can monitor device compliance, detect unauthorized application installations, and enforce policy changes across the fleet without relying on individual users to self-report compromise. |
Primary crisis communications channel shares infrastructure with the compromised consumer app environment | If Signal is the primary channel for emergency coordination, its compromise — or even justified user uncertainty about whether it has been compromised — degrades the organization’s crisis communications capability at the moment it is most needed. | BlackBerry® AtHoc® operates as an independent, authenticated, federated crisis communications and mass notification platform that does not share infrastructure with consumer messaging applications. When the consumer channel is compromised or suspected compromised, mission-critical coordination continues through the BlackBerry AtHoc platform's out-of-band channel. |
The encryption worked. The architecture failed. An organization whose sensitive government and military communications run through a platform with a consumer key management model has accepted an adversarial attack surface it cannot patch, train, or policy its way out of. The only structural remediation is an architecture that does not place enterprise communications security in the hands of individual users.
BlackBerry Secure Communications Position
Russian intelligence did not break Signal. The encryption worked exactly as designed. The attack targeted the person holding the key, not the cryptography protecting the channel. End-to-end encryption is a transit control. It does not govern how keys are stored, how backup credentials are managed, or how enterprise communications policy is enforced across an organization’s mobile estate. BlackBerry SecuSUITE removes the consumer account recovery model entirely — there is no backup recovery key for an adversary to social-engineer because enterprise key custody and device provisioning are governed by the organization, not by a self-service app setting. BlackBerry UEM enforces the device and application-layer controls that determine which communications channels government and military personnel can use, making the deployment of consumer messaging apps on managed devices a policy decision rather than an uncontrolled default. BlackBerry AtHoc provides the authenticated, federated crisis communications channel that operates independently of consumer messaging infrastructure — when the consumer channel is compromised, mission-critical coordination continues.
Citations:
Russian Intelligence Services Continue to Target Commercial Messaging Applications (Federal Bureau of Investigation (FBI) and Cybersecurity and Infrastructure Security Agency (CISA), Public Service Announcement I-062626-PSA, June 26, 2026).
Rewards for Justice: Information on Russian Cyber Actors Targeting Commercial Messaging Applications (U.S. Department of State, Rewards for Justice Program, June 30, 2026.)
%3Aquality(100)&w=3840&q=75)