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.
The link with Soclyde
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.



