As reported by The Hacker News, Google's Mandiant and Threat Intelligence Group has detailed a deeply concerning operational pattern from the Russia-linked espionage actor Cold Relic (also tracked as COLDRIVER, UNC4057, Callisto, Gossamer Bear, and Star Blizzard). The group compromised a U.S. organization's Google Workspace environment in late 2025, then weaponized the stolen data—staff directories, internal emails, and identities—to breach a second U.S. organization in 2026. This is not isolated espionage; it is a deliberate daisy-chain methodology.

Threat Intelligence: As reported by The Hacker News, Google's Mandiant and Threat Intelligence Group has detailed a deeply concerning operational pattern from the Russia-linked espionage actor Cold Relic (also tracked as COLDRIVER, UNC4057, Callisto, Gossamer Bear, and Star Blizzard).

The Attack Pattern: Compromise, Harvest, Pivot

What makes Cold Relic's latest campaign notable is not technical sophistication but operational patience and abuse of trust. The initial compromise followed a now-familiar playbook: stolen Super Admin credentials paired with MFA push-notification fatigue. Once the victim accepted a prompt—likely out of annoyance rather than intent—the attacker registered their own device within the tenant, effectively creating a persistent backdoor through legitimate authentication channels.

From there, Cold Relic exfiltrated the organization's entire cloud storage and then did something that distinguishes capable espionage actors: they queried the Admin Console security and email audit logs to assess the defender's visibility. This is tradecraft. They wanted to know whether anyone was watching before proceeding to the next phase.

Why the Daisy-Chain Matters

The most significant takeaway is the second-order compromise. By harvesting internal communications and staff directories from the first victim, Cold Relic gained something that external phishers can never replicate: authentic context. When they reached out to employees at the second organization, they could reference real people, real projects, and real relationships. This dramatically increases the success rate of social engineering attempts.

One cloud compromise is no longer just one breach—it is a supply chain of trust that adversaries can exploit across an entire sector.

This pattern should alarm any organization that shares information with partners, contractors, or aligned NGOs. Your security posture is now partially a function of who has your emails and what they are doing to protect them.

Who Is Most at Risk

Why the Daisy-Chain Matters
NGOs and think tanks with high-trust, low-security cultures—Cold Relic's historical sweet spot
Government contractors and defense-adjacent organizations that communicate with multiple agencies
Any organization using Google Workspace with Super Admin accounts protected only by push-based MFA
Organizations in the social graph of prior victims—if your partner was breached, you are the next target

Shield53 Recommendations

Immediate Actions

  • Phish-resistant MFA: Replace push-based MFA with number-matching prompts or hardware security keys (FIDO2/WebAuthn). Push fatigue is a solved problem—stop accepting the risk.
  • Super Admin hardening: Require hardware tokens for all privileged accounts. Consider dedicated admin workstations that cannot receive MFA prompts on personal devices.
  • Admin log monitoring: If Cold Relic checked your logs, you should check them first. Monitor for anomalous Admin Console queries, mass file sharing, and new device registrations—especially outside business hours.
  • Conditional access policies: Block authentication from residential proxies and unexpected geographies. Require device compliance for all admin actions.

Strategic Actions

  • Assume your communications are compromised: If you are a high-value target, treat outbound emails as potentially public. Establish out-of-band verification protocols for sensitive requests.
  • Partner breach notification: Develop a framework where trusted partners notify you of compromises that may expose your staff or communications. Information sharing is now a defensive imperative.
  • Tabletop the daisy-chain scenario: Run an exercise where a partner's email is compromised and used to target your organization. Most organizations have never rehearsed this.
  • Audit device registrations quarterly: Review all enrolled MFA devices, passkeys, and backup codes. Remove anything you cannot attribute to a known, current employee.

Cold Relic's evolution from credential phishing to cloud-native daisy-chain operations reflects a broader shift in Russian espionage tradecraft: why break into every door when you can steal the keys from the first one and copy them. The defensive response must be equally adaptive—treating identity, not the network perimeter, as the primary attack surface, and recognizing that trust itself is now a vulnerability.