Published: · Last updated: with original publication · Region: Global · Category: cyber

Source-reported · Independent verification status is not recorded for this article; claims remain attributed to their sources.

Russian ‘Cold Relic’ Hackers Used Google Workspace Breach to Compromise Second U.S. Organization

Google detailed how a Russian group known as COLD RELIC turned a single Google Workspace compromise into a second breach at another U.S. organization by stealing employee data, abusing multi-factor authentication, and phishing trusted contacts.

A Russian-linked hacking group used one breach of Google’s cloud tools to reach a second American victim, according to a disclosure from Google. The case shows how access to workplace accounts and contact lists can be reused to break into other organizations.

Google’s technical account describes how the group, tracked as COLD RELIC, first compromised a U.S. organization’s Google Workspace environment. From there, the attackers stole employee data and took over identities inside that tenant. With those real names and relationships in hand, they moved on to a second U.S. organization.

The report says COLD RELIC abused multi-factor authentication (MFA) processes and exploited trust between contacts to phish the next target. Rather than bypassing MFA technically, the attackers used information from the first breach to persuade or pressure people at the second organization into approving login attempts or interacting with malicious messages.

In this scenario, everyday tools such as email, calendars, and shared documents became the launchpad for further intrusion. Once the group could pose as legitimate users, it was easier to send convincing requests, access sensitive files, and move deeper into the second organization’s systems.

For staff at the affected organizations, the exposure goes beyond passwords. Stolen data can include internal messages, contact directories, and confidential documents. When attackers can convincingly impersonate colleagues, fraudulent activity may only become obvious after money is diverted or sensitive information is taken.

The incident challenges the assumption that putting operations into a large cloud platform automatically limits risk. Google’s account suggests that, even with strong underlying infrastructure, attackers can still chain together access across multiple tenants by exploiting how people treat messages from familiar names and domains.

Security teams reading Google’s findings face questions about how to harden identity and access controls, and how to monitor for suspicious cross-organization activity that looks, on the surface, like ordinary collaboration. They also need to rethink how MFA prompts are used so that users are less likely to approve unexpected requests.

Future responses from Google and other providers will show how seriously they take this pattern. Changes to default Workspace protections, new tools for detecting abnormal behavior across tenants, or official warnings from U.S. authorities about similar Russian operations would all signal that this case is being treated as a template for further campaigns.

Sources