# Russian State-Backed UNC5792/UNC4221 Phish EU Officials, Diplomats and Journalists via Signal and WhatsApp Linked-Device and OAuth Account Takeover

> Dutch intelligence services AIVD and MIVD, later joined by FBI/CISA and a $10M US Rewards for Justice bounty, attribute a sustained account-takeover campaign against senior EU/NATO officials, diplomats, military personnel, journalists, and Russia-focused researchers to Russian state actors tracked as UNC5792 (FSB) and UNC4221 (Russian military intelligence), with overlapping Google-tracked clusters UNC6293/UNC7005/UNC5976. Attackers do not break Signal or WhatsApp encryption; they social-engineer victims into approving a malicious linked device or handing over verification codes, PINs, and — since mid-2026 — Signal Backup Recovery Keys, giving real-time mirrored access to messages.

- **Published:** 2026-08-26T00:00:00Z
- **Last reviewed:** 2026-08-26T00:00:00Z
- **Canonical:** https://intel.threadlinqs.com/threat/TL-2026-2170
- **Card image:** https://intel.threadlinqs.com/og/threat/threat-intel-unc5792-signal-whatsapp-takeover-tl-2026-2170.webp?v=c810a3c5 (Threadlinqs threat intel: UNC5792 Signal & WhatsApp Takeover: Detection & IOCs (TL-2026-2170) — High severity, 17 IOCs, 9 detection rules.)
- **ID:** TL-2026-2170
- **Severity:** HIGH
- **Category:** PHISHING
- **Status:** ACTIVE
- **Actor:** UNC5792 (Russia)
- **Detections:** 9 (1 shown free below) · **IOCs:** 17

## Description

Since at least June 2025, Google's Threat Intelligence Group has tracked UNC6293 (a sub-cluster of ICE RELIC/APT29, 'Cozy Bear', linked to Russia's SVR) impersonating US State Department personnel to lure diplomats and Russia researchers into phishing flows. By March 2026 the operation had scaled into a global campaign: Dutch AIVD and MIVD publicly attributed it to Russian state actors, describing attackers who pose as 'Signal Security Support ChatBot' or a similar official-sounding account, warn victims of 'suspicious activity' or a 'possible data leak', and trick them into (a) sharing an SMS verification code and PIN so the attacker can register a new linked device under the victim's account, or (b) scanning a QR code / approving a WhatsApp 'linked devices' request directly. Because the underlying end-to-end encryption is never broken, victims regain access to their own account normally and often have no indication of compromise while the attacker continues to mirror every message in real time.

Google TIG and Microsoft (tracking an overlapping cluster as Storm-2945/UNC7005) documented a parallel, distinct cluster, UNC5976, running hospitality-themed operations: 'CaptiveCrunch' compromised hotel and conference-center Wi-Fi captive portals (~70 victim IPs identified) to redirect traveling diplomats and defense-industry personnel into phishing pages, and used diplomatic-event lures (a GLOBSEC forum spoof and a 'Summit Companion App' theme, May-June 2026) to distribute a rogue Excel plugin (HEADRUSH) that drops an HTA payload, and commodity/custom malware — Vidar (Windows), Atomic/AMOS (macOS), CornFlake RAT (Go-based), and ChocoShell/CHERRYPIE (PowerShell) — for post-compromise credential and file theft, tasked from a web-based C2 panel branded 'FruitStone/CloudSync Console' to blend in as a legitimate cloud-sync product.

From June 2026 the FBI observed the TTP evolve: rather than one-time verification codes, UNC5792/UNC4221 began directly soliciting victims' Signal Backup Recovery Key — the credential that decrypts a user's entire local message history — via chat, framed as a mandatory 2FA rollout or urgent data-recovery request. The FBI/CISA updated advisory (PSA I-062626-PSA, 2026-06-26) and the US State Department's subsequent $10M Rewards for Justice offer (2026-06-29) formally named UNC5792 as affiliated with FSB Border Guards and UNC4221 with Russian military intelligence, confirming thousands of compromised government, military, journalist, and NGO accounts across the US, NATO member states, Ukraine, and allied intelligence partners. In parallel, Google TIG documented the same actor set (August 2026) expanding into OAuth device-code phishing — fake 'Continue with Google/Microsoft' pages that capture a legitimate authentication token after a real login, rather than a stolen password — against academia, aerospace, defense, and think-tank targets. A separate but related Russian FSB (Center 16) group, Secret Blizzard/Turla, was independently found repurposing its long-running Kazuar backdoor (evolved into a modular, ~150-option P2P botnet) specifically to exfiltrate Signal Desktop message-history files from compromised Windows hosts, illustrating a second, malware-based route to the same messaging-app data. The EU Interinstitutional Cybersecurity Board's August 2026 threat-landscape briefing (reported by Euronews) folded this Signal/WhatsApp campaign into its broader count of 190+ threat actors targeting the EU ecosystem and 8 significant incidents logged in H1 2026, confirming Dutch government personnel among the victims and stating the attackers 'likely gained access to sensitive information.' There is no PoC/exploit code involved — the entire chain is social-engineering and legitimate-feature abuse (linked devices, OAuth device-code flow, backup key export), not a software vulnerability. Signal shipped a cryptographic hardening fix to the backup-key flow on 2026-07-27 in direct response to the FBI disclosure.

## MITRE ATT&CK

- T1589 Gather Victim Identity Information
- T1598 Phishing for Information
- T1583 Acquire Infrastructure
- T1584 Compromise Infrastructure
- T1587 Develop Capabilities
- T1566 Phishing
- T1078 Valid Accounts
- T1528 Steal Application Access Token
- T1111 Multi-Factor Authentication Interception
- T1621 Multi-Factor Authentication Request Generation
- T1555 Credentials from Password Stores
- T1550 Use Alternate Authentication Material
- T1123 Audio Capture

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

**Verification-Code/Backup-Key Solicitation Followed by Anomalous OAuth Device-Code Grant** (`TL-2026-2170-SPL-001`)

Detects the UNC5792/UNC4221 account-takeover chain in enterprise identity telemetry: an OAuth 'device code' authorization grant (the flow abused by fake 'Continue with Google/Microsoft' phishing pages) completing for a user, especially when the grant spans multiple countries/IPs in a short window — consistent with an attacker completing an authorization the victim was socially engineered into approving after being asked for a verification code, PIN, or 'mandatory 2FA rollout' confirmation by an actor impersonating Signal/WhatsApp/IT support.

- **Languages:** Splunk SPL, Microsoft KQL, Sigma
- **ATT&CK:** T1598.003, T1621, T1111, T1528, T1078
- **Data sources:** azure_ad_signin_logs, google_workspace_login_audit, identity_provider_oauth_grant_logs
- **Severity:** high
- **Confidence:** high

### Splunk SPL

```spl
index=aad_signin sourcetype="azure:aad:signin" earliest=-24h
| eval authProtocol=coalesce(authenticationProtocol, 'properties.authenticationProtocol')
| eval appName=coalesce(appDisplayName, 'properties.appDisplayName')
| eval userUpn=coalesce(userPrincipalName, 'properties.userPrincipalName')
| eval srcIp=coalesce(ipAddress, 'properties.ipAddress')
| eval country=coalesce('location.countryOrRegion', 'properties.location.countryOrRegion')
| where authProtocol="deviceCode"
| stats count AS grant_count, min(_time) AS first_seen, max(_time) AS last_seen, values(appName) AS apps, values(srcIp) AS src_ips, dc(country) AS distinct_countries, values(country) AS countries BY userUpn
| where grant_count>=1 AND (distinct_countries>1 OR NOT match(mvindex(apps,0), "(?i)^(Microsoft Authentication Broker|Azure CLI|Microsoft Intune)$"))
| convert ctime(first_seen) ctime(last_seen)
| table userUpn, grant_count, apps, src_ips, countries, first_seen, last_seen
```

### Microsoft KQL

```kql
SigninLogs
| where TimeGenerated > ago(24h)
| where AuthenticationProtocol == "deviceCode"
| extend App = tostring(AppDisplayName), SrcIP = tostring(IPAddress), Country = tostring(LocationDetails.countryOrRegion)
| summarize GrantCount=count(), Apps=make_set(App), SrcIPs=make_set(SrcIP), Countries=make_set(Country), DistinctCountries=dcount(Country), FirstSeen=min(TimeGenerated), LastSeen=max(TimeGenerated) by UserPrincipalName
| where GrantCount >= 1 and (DistinctCountries > 1 or Apps !has "Microsoft Authentication Broker")
| project UserPrincipalName, GrantCount, Apps, SrcIPs, Countries, FirstSeen, LastSeen
```

### Sigma

```yaml
title: Anomalous OAuth Device-Code Authorization Grant
id: 7b6f1e2a-4c3d-4f7a-9b1e-2c8a5d3f6e10
status: experimental
description: Detects an OAuth device-code flow grant completing, the mechanism abused by UNC5792/UNC4221 'Continue with Google/Microsoft' phishing pages to steal legitimate authentication tokens without a password.
references:
  - https://www.thehackernews.com/2026/08/suspected-russian-hackers-abuse-google.html
  - https://therecord.media/10million-reward-us-russian-hackers-unc4221-unc5792
author: Threadlinqs Team
date: 2026-08-27
tags:
  - attack.credential-access
  - attack.t1528
  - attack.t1078
  - attack.initial-access
  - attack.t1598.003
logsource:
  product: azure
  service: signinlogs
detection:
  selection:
    AuthenticationProtocol: 'deviceCode'
  filter_known_admin_tools:
    AppDisplayName:
      - 'Microsoft Authentication Broker'
      - 'Azure CLI'
      - 'Microsoft Intune'
  condition: selection and not filter_known_admin_tools
falsepositives:
  - Legitimate CLI/headless device onboarding using the device-code flow from a known corporate egress range
level: high
```

**Known false positives:**

- Legitimate CLI/automation device-code flows (Azure CLI, PowerShell, headless IoT onboarding) from known corporate egress IPs
- Traveling employees legitimately signing in from a new country while an existing session/app is still active elsewhere

**Tuning notes:** Baseline device-code sign-ins per tenant/app and alert only on first-time-seen app IDs or a device-code grant combined with a geographically anomalous, Tor, or VPN-sourced IP; correlate with helpdesk tickets or user reports of a 'Signal/WhatsApp Support' or 'mandatory 2FA rollout' message immediately preceding the grant.

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

- Verification-Code/Backup-Key Solicitation Followed by Anomalous OAuth Device-Code Grant (locked: unlock with TL Creds)
- HEADRUSH/ChocoShell Execution Chain and Non-Signal Process Touching Signal Message-History Storage (locked: unlock with TL Creds)
- FruitStone/CloudSync C2 Beaconing and Vidar Dead-Drop Resolver Callback (locked: unlock with TL Creds)
- Verification-Code/Backup-Key Solicitation Followed by Anomalous OAuth Device-Code Grant (locked: unlock with TL Creds)
- HEADRUSH/ChocoShell Execution Chain and Non-Signal Process Touching Signal Message-History Storage (locked: unlock with TL Creds)
- FruitStone/CloudSync C2 Beaconing and Vidar Dead-Drop Resolver Callback (locked: unlock with TL Creds)
- HEADRUSH/ChocoShell Execution Chain and Non-Signal Process Touching Signal Message-History Storage (locked: unlock with TL Creds)
- FruitStone/CloudSync C2 Beaconing and Vidar Dead-Drop Resolver Callback (locked: unlock with TL Creds)

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

## Sources

- [State actors tried to hack EU officials' messaging apps, cybersecurity body warns](https://www.euronews.com/my-europe/2026/08/26/state-actors-tried-to-hack-eu-officials-messaging-apps-cybersecurity-body-warns)
- [Russia targets Signal and WhatsApp accounts in cyber campaign](https://english.aivd.nl/latest/news/2026/03/09/russia-targets-signal-and-whatsapp-accounts-in-cyber-campaign)
- [Russian government hackers targeting Signal and WhatsApp users, Dutch spies warn](https://techcrunch.com/2026/03/09/russian-government-hackers-targeting-signal-and-whatsapp-users-dutch-spies-warn/)
- [Russian hackers go after high-value targets through Signal](https://www.helpnetsecurity.com/2026/03/23/russian-hackers-signal-phishing-campaign/)
- [Spyware Investigator Exposes 13,500-Target Russian Signal Hijack](https://www.thecybersignal.com/russian-government-hackers-signal-account-hijack-13500-targets-2026/)
- [FBI Warns Russian Intelligence Hackers Target Signal Backup Recovery Keys](https://thehackernews.com/2026/06/fbi-warns-russian-intelligence-hackers.html)
- [US posts $10 million reward over Russian cyber campaign targeting Signal, WhatsApp](https://therecord.media/10million-reward-us-russian-hackers-unc4221-unc5792)
- [Suspected Russian Hackers Abuse Google OAuth and WhatsApp Linking to Hijack Accounts](https://thehackernews.com/2026/08/suspected-russian-hackers-abuse-google.html)
- [Russian snoops add OAuth abuse to targeted phishing campaigns](https://www.theregister.com/security/2026/08/21/russian-snoops-add-oauth-abuse-to-targeted-phishing-campaigns/5290706)
- [Fake Conferences, OAuth and WhatsApp: Inside Russia's New Espionage Tactics](https://securityaffairs.com/197630/apt/fake-conferences-oauth-and-whatsapp-inside-russias-new-espionage-tactics.html)
- [Russian hackers turn Kazuar backdoor into modular P2P botnet](https://www.bleepingcomputer.com/news/security/russian-hackers-turn-kazuar-backdoor-into-modular-p2p-botnet/)
- [Frequent freeloader part II: Russian actor Secret Blizzard using tools of other groups to attack Ukraine](https://www.microsoft.com/en-us/security/blog/2024/12/11/frequent-freeloader-part-ii-russian-actor-secret-blizzard-using-tools-of-other-groups-to-attack-ukraine/)
- [US offers $10M reward for Russian hackers who steal Signal backup keys](https://www.paubox.com/blog/us-offers-10m-reward-for-russian-hackers-who-steal-signal-backup-keys)
- [Cybersecurity Advisory: Phishing via messaging apps Signal and WhatsApp](https://english.aivd.nl/documents/2026/03/09/cybersecurity-advisory.-phishing-via-messaging-apps-signal-and-whatsapp)

## 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-2170
