Czech NUKIB confirms Signal accounts compromised via QR-code phishing, not broken encryption

On October 13, 2026, the Czech Republic's National Cyber and Information Security Agency (NUKIB) published a formal threat assessment confirming that actors linked to Russia are running targeted phishing campaigns against Signal users across Europe, with related incidents now recorded inside the Czech Republic itself. NUKIB is the fifth Western agency to publicly confirm the same operation, after the Netherlands, Germany, the United States and Ukraine. As reported in a dev.to analysis, the FBI said in March 2026 that unauthorized access had reached thousands of Signal accounts worldwide, and Der Spiegel, citing German government sources, reported roughly 300 compromised accounts in Germany's political sphere. NUKIB cautions that the true footprint is almost certainly larger than the five countries where the technique has been officially documented.

The finding every agency agrees on: Signal's end-to-end encryption was not broken and the Signal Protocol was not cracked. The attackers route around the cryptography entirely, through a feature that ships in every copy of the app.

How the QR-code trick works

When a user links a laptop to their Signal account, the phone displays a QR code. Whatever scans that code is paired to the account and receives messages in real time. Attackers substitute their own code for the legitimate one.

Google's Threat Intelligence Group documented the technique in early 2025. One variant, attributed to a group tracked as UNC5792, hosts fake Signal group invitation pages that look authentic; the QR code on the page does not encode an invitation but a device-linking address pointing to attacker infrastructure. A second, tracked as UNC4221, embedded malicious QR codes in a phishing kit mimicking Kropyva, an artillery guidance application used by Ukraine's armed forces. Other clusters took simpler paths: Turla used PowerShell scripts to extract Signal messages from compromised Windows machines, and a Belarus-linked group used the Robocopy utility to copy Signal's desktop database files. Once the locally decrypted database is in hand, the encryption no longer matters.

NUKIB also describes a second, simpler vector: messages impersonating legitimate Signal notifications, support alerts or group invitations, containing a link or QR code. Signal's genuine support team never contacts users inside the app and never asks for a PIN or registration credentials, so any message that does is fraudulent.

A structural detail complicates detection. According to Google's researchers, compromises established this way can go unnoticed for extended periods, partly because Signal deliberately keeps no centralized server-side log of device-pairing events, since logging them would create a metadata trail. That privacy-preserving design decision is also why there is no reliable audit trail for a silent pairing.

Law enforcement uses the same opening

The technique is not exclusive to intelligence operations. On September 30, 2026, Privacy Guides reported on documents obtained by Netzpolitik showing that German customs officials have been reading suspects' messages by pairing a device to their accounts, without breaking any encryption. Testing began at the end of 2023, and since August 2025 the approach has been an official, permanent strategy available to agents. The affected messengers include WhatsApp, Telegram, Threema and Signal.

The implementations differ in difficulty. Telegram sends a login code to existing devices, which can be phished. WhatsApp requires linking to be initiated from inside the app, though a victim can still be coached into entering a code. Signal permits linking only through a QR code, which an attacker can still send directly to an unsuspecting user. The dev.to write-up connects this to the Dutch military intelligence director's public position that even end-to-end encrypted apps are not appropriate for classified government information.

What to check, and what won't help

The most actionable advice in NUKIB's advisory is also the simplest: open Settings, then Linked Devices, and remove anything you do not recognize. Regular checks matter precisely because silent pairings can persist.

One correction the dev.to analysis stresses: Signal's Registration Lock does not defend against this attack. Registration Lock prevents someone from re-registering your number on a new phone without your PIN. The QR-code campaign does not re-register anything; it pairs a new device to an account that is already registered. Turning Registration Lock on is still worthwhile, but it addresses a different threat.

Why it matters

None of the protocol-level qualities security debates usually focus on, such as ratchet design, post-quantum key exchange or code audits, saved a single account in this campaign. Accounts were lost at the boundary between the protocol and its user: a QR code that meant joining a group to a human and device pairing to a machine, a pairing nobody noticed, a device list nobody opened.

For messenger builders, the dev.to author argues pairing must be treated as granting full access to the account. That means plainly worded pairing screens, loud and persistent notifications when a new device joins, a confirmation step on the phone showing the device type and what it will be able to do, and a linked-devices list presented as a first-class screen rather than buried in settings. For users of any encrypted messenger, the lesson is shorter: audit your linked devices regularly, because the encryption held while the enrollment flow failed.