Russian COLD RELIC Hackers Use Stolen Google Workspace Data to Breach Second U.S. Organization
- ID
- 47687
- Status
- summarized
- Published
- 18 Nov 2026, 1:58 PM
- Fetched
- 18 Nov 2026, 2:18 PM
- Provider
- The Hacker News
- Category
- security
- Original URL
- https://thehackernews.com/2026/11/russian-cold-relic-hackers-use-stolen.html
- Source URL
- https://feeds.feedburner.com/TheHackersNews
Summary
- Score
- 2.0
- Created
- 18 Nov 2026, 2:19 PM
- Tags
- Audience
- developerssaas_founders
What happened
The Hacker News headline reports that a group it calls "COLD RELIC" used data stolen from Google Workspace to breach a second U.S. organization. Beyond the headline and a truncated first line, the supplied text contains only site navigation, category links, and promotional boilerplate — no details on the initial access vector, the Workspace data involved, victim names, timeline, or the attackers' tooling.
Why it matters
There is nothing actionable here yet: the excerpt does not say whether the Workspace data came from token theft, OAuth consent abuse, an insider, or a third-party SaaS integration, so you cannot decide whether to change Workspace sharing defaults, revoke stale OAuth grants, or shorten session lifetimes. Wait for the full report before acting; the only defensible takeaway is that if your SaaS product stores customer Workspace exports or Drive data, that data is now a demonstrated path into a second victim.
Discussion angle
Given how little the excerpt actually specifies, use the segment to ask the room: for your own product, what would an attacker holding a customer's stolen Workspace data be able to reach — and is that a design decision you've consciously made or an accident of default sharing settings?