SOCLYDE logo
Current languageEN
Cybersecurity newscybersecuritycold

Cold Relic reuses stolen data to impersonate contacts

Mandiant describes Cold Relic reusing stolen cloud data to impersonate contacts. Verify unusual requests and review authentication methods added to accounts.

Published on

By Soclyde

A professional verifies a contact by phone beside a colleague holding a folder

In summary

  • Google’s November 17 report links two US intrusions in 2025 and 2026.
  • Stolen contacts and documents provide context for convincing impersonation.
  • For affected accounts, revoke sessions, tokens and OAuth access, then remove unauthorized sign-in methods.

Explore next

Soclyde resources

Article contents

In a report dated November 17, 2026, Google Threat Intelligence Group and Mandiant describe two linked Cold Relic intrusions. Data stolen from a US organization in late 2025 helped attackers approach another organization in 2026 under a convincing professional identity.

Stolen information becomes a pretext

Mandiant links contacts, identities and context from the first victim to lures used against the second. A compromised document repository can therefore supply material for the next fraudulent conversation.

The Record emphasizes that the organizations are unnamed. This is a documented intrusion chain; it does not establish that any business receiving a suspicious message is necessarily being targeted by Cold Relic.

A familiar identity in a reassuring channel

The second approach described used secure messaging. The attacker impersonated an employee of the first organization, built a conversation and then shared a phishing link.

Transport encryption does not establish the sender's real identity. In an interview with Dark Reading, a GTIG investigator recommends confirming unusual messages through a separate, previously established channel. For a small team, calling the contact's usual number provides a straightforward check before entering credentials.

New ways to sign in after initial access

The primary report describes attacker-enrolled MFA devices, passkeys and backup codes. Some access persisted despite password changes and session resets.

That does not make passkeys inherently weak: the issue described is enrollment of an authentication method controlled by an adversary. Response therefore needs to establish who added each method, when and under what circumstances.

Review cloud service permissions

Mandiant provides detection ideas involving new authentication enrollments, exports and unusual external sharing. Administrators should correlate these events with sign-ins and alerts instead of relying only on a familiar IP location.

Dark Reading adds investigator interviews about tightening MFA enrollment and auditing OAuth. For affected accounts, Mandiant recommends resetting passwords and immediately revoking all active browser sessions, refresh tokens and third-party OAuth app permissions. Also remove unauthorized passkeys, backup codes and MFA devices. In an environment connecting Google Workspace to Microsoft Entra ID, apply these controls across both services.

Soclyde keeps distinct passwords in an encrypted vault on your devices and supports access sharing through Premium. That helps limit secrets copied into email or working documents that could be extracted from cloud storage.

The vault does not remove MFA devices or OAuth grants from a compromised tenant. Those controls remain tasks for the cloud services and identity provider.

Key points

Verify the contact before acting on an unusual request, and review every way to sign in after an intrusion. To organize access for your team, contact Soclyde.

Frequently asked questions

Are the victims identified?

No. The report describes two US organizations without naming them. The Record also highlights the limits of public information about the victims and stolen data.

Does encrypted messaging verify a contact’s identity?

No. Mandiant describes an approach through secure messaging while impersonating an employee. Verify unusual requests through a previously established channel.

Does a password reset remove persistence?

No. For affected accounts, Mandiant recommends resetting passwords, revoking all active sessions, refresh tokens and third-party OAuth app permissions, and removing unauthorized passkeys, backup codes and MFA devices. This applies across Google Workspace and Microsoft Entra ID when both are used.

References

Sources and references

Need advice?

Design your password strategy with Soclyde

Schedule a dedicated walkthrough with the team to see how local-first security adapts to your stack.

Talk with us

Keep reading