Google's Threat Intelligence Group (GTIG) reported on November 18, 2026, that the Russian state-sponsored threat group Star Blizzard is leveraging previously stolen data to initiate new attacks. The group, also known as Cold River and UNC4057 and linked to Russia's FSB, compromised a U.S. organization in late 2025. They are now using information from that breach, including contact lists, to impersonate an employee and launch phishing campaigns against a new U.S.-based target. The initial intrusion was notable for its use of multi-factor authentication (MFA) fatigue to bypass security controls, highlighting the group's persistent and adaptive tactics against high-value targets in North America and Europe.
Star Blizzard is a sophisticated APT group focused on intelligence gathering for the Russian government. Their targets frequently include government bodies, defense contractors, and non-governmental organizations (NGOs). This latest campaign demonstrates a multi-stage attack methodology where the fruits of one compromise are directly used to enable the next.
The attack chain is as follows:
The group's TTPs are well-documented and demonstrate a high level of operational security and persistence.
T1621): For the initial 2025 breach, the attackers spammed the target's super admin account with MFA push notifications until the user eventually approved one, a technique known as MFA fatigue or push bombing.T1583): The group used a residential proxy network geographically close to the victim to make their login attempts appear legitimate and evade location-based security alerts.T1530): After gaining access, they performed a bulk download of the organization's cloud drive.T1589): The attackers exported employee lists and other domain data, which they later used for reconnaissance and to select their next target.T1566): The core of the second-stage attack involved using the stolen identity and contact information to conduct a highly targeted phishing campaign.T1070.004): The group was observed accessing the admin console to erase logs and evidence of their intrusion.This campaign highlights the cascading risk of a single security breach. A compromise of one organization can directly lead to the compromise of its partners, suppliers, and customers. The impact includes:
No specific file hashes, C2 domains, or IP addresses were provided in the source articles.
To detect activity related to this threat actor, security teams should hunt for the following patterns:
Deploy phishing-resistant MFA, such as FIDO2 security keys or number matching, to defeat MFA fatigue attacks.
Educate users, especially those with privileged access, to identify and report MFA bombing and sophisticated phishing attempts.
Monitor authentication and cloud access logs for signs of MFA fatigue, bulk data downloads, and anomalous administrative activity.
Implement conditional access policies to block or flag logins from untrusted networks, such as residential proxies.
The most direct countermeasure to the MFA fatigue tactic used by Star Blizzard is to upgrade from simple push-based MFA to phishing-resistant methods. Organizations should prioritize the deployment of FIDO2/WebAuthn-compliant authenticators (like YubiKeys or Windows Hello) for all users, especially administrators. Where FIDO2 is not possible, enabling 'number matching' in authenticator apps (like Microsoft Authenticator) provides a significant security uplift. This requires the user to type a number displayed on the login screen into their app, preventing accidental approval from a flood of notifications. This single change breaks the core of the MFA fatigue attack chain.
To detect MFA fatigue attempts in real-time, security teams must configure their SIEM or identity provider to alert on anomalous authentication patterns. A specific rule should be created to trigger an alert when a single user account receives a high number of MFA push requests (e.g., more than 5) in a very short time (e.g., 5 minutes) without a corresponding successful login. This alert should be treated as a high-priority incident, indicating an active attempt to breach an account. The response playbook should include temporarily locking the account and contacting the user through a secure, out-of-band channel to verify the activity.
To detect the data exfiltration that follows a successful compromise, organizations need to monitor for bulk data downloads from their cloud environments. Cloud Access Security Brokers (CASB) or native cloud security tools should be configured to alert on unusual data transfer volumes. For example, an alert should be generated if a user account, particularly an admin account, downloads the 'entire cloud storage drive' or performs a 'domain-wide export of data,' as Star Blizzard was observed doing. Baselining normal data access patterns and alerting on significant deviations is key to identifying when an attacker is stealing the data that will be used to fuel their next attack.
Star Blizzard compromises a U.S. organization using MFA fatigue and begins exfiltrating data.
Google's Threat Intelligence Group reports that Star Blizzard is using the stolen data to attack a new U.S. target.

Cybersecurity professional with over 10 years of specialized experience in security operations, threat intelligence, incident response, and security automation. Expertise spans SOAR/XSOAR orchestration, threat intelligence platforms, SIEM/UEBA analytics, and building cyber fusion centers. Background includes technical enablement, solution architecture for enterprise and government clients, and implementing security automation workflows across IR, TIP, and SOC use cases.
CyberNetSec.io uses automation to assist source monitoring, deduplication, observable extraction, and structured intelligence generation. Published analysis follows human-defined editorial standards and adds defensive context including MITRE ATT&CK, D3FEND, STIX, and Sigma where applicable. Read our editorial policy.
Help others stay informed about cybersecurity threats
Every tactic, technique, and sub-technique used in this threat has been identified and mapped to the MITRE ATT&CK framework for consistent, actionable threat language.
Observables and indicators of compromise (IOCs) have been extracted and cataloged. Risk has been assessed and correlated with known threat actors and historical campaigns.
Detection rules, incident response steps, and D3FEND-aligned mitigation strategies are included so your team can act on this intelligence immediately.
Structured threat data is packaged as a STIX 2.1 bundle and can be visualized as an interactive graph — relationships between actors, malware, techniques, and indicators.
Sigma detection rules are derived from the threat techniques in this article and can be converted for deployment across any major SIEM or EDR platform.