Stolen Identities Reused to Breach a Second Victim
The Google Threat Intelligence Group (GTIG) reports that the Russian actor Star Blizzard, which Google tracks as Cold Relic, used data and identities stolen from one US organization in late 2025 to impersonate one of its employees and compromise another US organization months later. Neither victim is named. This is a different activity from the RedFlick/CosmicPulse malware campaign we covered on September 30.
| Attribute | Value |
|---|---|
| Threat actor | Star Blizzard (Google: Cold Relic) |
| Also tracked as | Callisto, Cold River, UNC4057, Gossamer Bear |
| Attribution | Russian intelligence; the US has associated the group with the FSB |
| Victims | Two unnamed US organizations |
| Focus | Cloud identity abuse and social engineering |
| Malware | None named |
First Intrusion: Late 2025
The actor used compromised super-admin credentials and a residential proxy network near the victim. Using MFA push-notification fatigue, it registered a device to the victim's tenant. It then:
- downloaded the entire cloud storage drive;
- accessed the admin console to probe defenses and remove traces of the intrusion;
- exported full employee lists and ran a domain-wide export.
Over several months it kept access through passkeys, rogue MFA devices and MFA backup codes, and exfiltrated email and cloud drive documents.
Second Intrusion: Impersonation
After the first victim removed the actor, Cold Relic used email accounts impersonating that organization's employees to send fresh social engineering messages to staff and associates. It also contacted the second organization through a secure messaging app, posing as a first-organization employee, and shared phishing links that harvested credentials and Entra ID authentication tokens. It then registered a new MFA device on the victim's SSO and bulk-downloaded files from the user's cloud drive. The actor later changed its messaging profile name, likely to reuse the persona in another attack.
Defensive Takeaways
- Audit MFA registrations, including passkeys, devices and backup codes, and alert on new registrations for privileged accounts.
- Use number matching or phishing-resistant MFA to blunt push fatigue.
- Rotate and revoke everything after an incident: sessions, tokens, backup codes and registered authenticators, not just passwords.
- Warn partners and contacts after a breach; attackers reuse stolen identities against your vendors and peers.
- Verify unexpected requests out of band, even when they come from a known contact on a messaging app.
