When Cold Relic finishes with one cloud tenant, the next company starts receiving emails that already know the right names, the right invoice numbers, and the right shared-project jargon. The first breach is the research phase. The second is the job. If your cybersecurity program treats a contained mailbox incident as closed, you have donated a briefing packet to a Russia-linked crew that now talks like your vendor.

Dark Reading’s reporting on the group is blunt about the method. Stolen cloud data from victim one becomes the impersonation kit for victim two. Contracts, org charts, ticket threads, and shared-drive filenames do more damage in a follow-on campaign than a fresh brute-force spray against a login you already watch.

The Russia-linked threat group is using data stolen from one victim to target others via convincing impersonations and social engineering attacks.

Illustration associated with reporting on a Russia-linked cloud-to-cloud intrusion campaign
Cold Relic’s second victim often meets a message that already sounds like a real partner thread.

A Stolen Cloud Tenant Writes the Next Script

You already built threat detection around noisy stuff. Failed logins. Impossible travel. A firewall dropping a scan. Cold Relic’s second act skips that noise. An operator sitting in a stolen Microsoft 365 or Google Workspace tenant has your partner list, your naming conventions, and the last three weeks of “quick question on the PO” threads. They don’t guess. They quote you back to yourself.

That should rearrange your incident response assumptions. A mailbox compromise is a data-theft event with a delayed blast radius. Every message in that tenant is a future pretext. Every attached spreadsheet is a map of who approves what. Every calendar invite tells them when the real human is offline and a lookalike can answer instead.

Threat-protection stacks that score “external sender” and call it a day will miss this. The second victim often sees a note from a domain they already do business with, or a lookalike standing on details only a real thread would have. Your users can spot urgency and bad grammar. They still approve a supplier who cites last Tuesday’s change window and attaches a PDF that matches the last real invoice layout.

Security hardening still matters on the identity side. MFA, session revocation, app-consent review, forwarding-rule hunts. Those steps close the hole in tenant one. They do nothing for the PDF that already left, or the contact export sitting in a staging share. Defense in depth that ends at your IdP is a fence around a house after the filing cabinet has been photocopied.

Treat the dump as a living capability. If Cold Relic has payroll files, expect payroll-themed lures aimed at your bank contacts. If they have legal holds, expect counsel impersonation. If they have vendor onboarding forms, expect an “updated banking details” pass against accounts payable. The content of the steal predicts the next play. Your job is to warn the people named in those files before the crew does.

If You Only Reset Your Users, the Next Victim Pays

Resetting passwords in your tenant is table stakes. The operational problem is downstream. You need a play that assumes the data is already in hostile hands and that someone else will be the next target. Do this in hours, not in the retro that lands next quarter.

  • Immediate: Export the high-value objects the actor could have touched: vendor lists, invoice templates, executive calendars, shared-mailbox mail, and files marked external. Build a notification list of every third party named in those objects. Tell them the specific artifacts that may be replayed, not a vague “we had an incident.”
  • Immediate: Kill sessions, revoke refresh tokens, audit mailbox rules, consent grants, and app passwords. Hunt for new inbound connectors, forwarding, and OAuth apps. Then assume outbound mail from the window of compromise is tainted, and preserve it for the partner briefings.
  • Ongoing: Put partner-impersonation into threat detection. Alert on replies that continue a real thread from a new domain, on invoice-detail mail that cites real PO numbers from a lookalike, and on voice or chat follow-ups that reference stolen calendar facts. Train AP and help desk on verification out of band, using a number you already have on file, not a number in the email.
  • Ongoing: Shrink standing access to the datasets that make impersonation cheap. Finance shared mailboxes, CRM exports, and legal files should not sit in a general-purpose drive. Log and restrict mass download. Your cyber security control here is data minimization with an audience that includes the next company in the supply chain.

Practice the partner call. Incident response that only pages internal owners leaves accounts payable at a supplier reading a perfect fake. Assign a human who can reach named counterparties the same day. Write the one-pager they are allowed to send so legal does not freeze the warning until the second breach is already in progress.

Cybersecurity That Stops at the Tenant Boundary Already Lost

Cold Relic is the hostile version of a fact every IT buyer keeps postponing: data outlives the incident, the contract, and sometimes the company. A federal bankruptcy judge just signed off on Google taking possession of defunct Spirit Airlines’ data for $10 million, with promised protections, for use in AI projects. Passenger records and operational files that survived the carrier still have a buyer.

Spirit Airlines aircraft on the tarmac, illustrating the carrier whose customer and operational data a court approved for sale
A bankrupt airline’s dataset still moved, this time under a $10 million court-approved sale rather than a stolen-tenant dump.

You should care even if you never flew Spirit. Once a dataset is copied, your original access-control model no longer travels with it. Cold Relic turns a stolen copy into a script for the next intrusion. A bankrupt estate can sell a copy into an AI pipeline under terms the original passengers never saw. Different motives. Same operational fact: people in those files do not get a new vote. Programs that inventory “systems we run” and skip “datasets we created that now live somewhere else” are scoring the wrong asset.

Build the boring controls that make a dump less useful. Tokenize or truncate account numbers in shared mail. Watermark vendor portals so a replayed invoice is obvious. Keep a current counterpart roster with phone numbers that did not arrive in this week’s email. If your threat-protection tools only inspect your own domain’s outbound mail, extend monitoring to the lookalike registrations that appear in the days after you disclose a cloud incident.

The firewall still belongs in the picture. It will not read a partner’s stolen thread and tell you the sender is lying. Put it to work on the callbacks and payload hosts that show up after a convincing human exchange. Defense in depth here means identity, data handling, partner warning, and network controls in that order. Cold Relic already has the conversation. Your remaining job is to make the next login, the next wire, and the next attachment fail anyway.

Sources

Take Control of Your Server Security

Don't let brute-force attacks slow you down. Try IPBan Pro risk-free for 30 days.

Secure. Automated. Lightweight.

Stay up to date with the latest news, releases and more.

Take Control of Your Server Security

Don't let brute-force attacks slow you down. Try IPBan Pro risk-free for 30 days.

Secure. Automated. Lightweight.