Months after GOSSAMER BEAR downloaded one American organization’s cloud storage and employee directory, the threat actor returned under the name of someone who worked there. It contacted a person at a second US organization through an encrypted messaging application. The identity belonged to a real employee. GOSSAMER BEAR controlled the account. The first breach had already supplied the pretext before the phishing link arrived.
The earlier intrusion began in late 2025 with stolen credentials for a Google Workspace Super Admin account. The role holds the highest authority across an organization’s Workspace environment. The user accepted one of the threat actor’s repeated authentication requests. GOSSAMER BEAR then registered its own devices, passkeys, and backup codes. It downloaded the organization’s cloud storage, exported its employee directory, synchronized email to external clients, and remained inside for months.
Google Threat Intelligence Group (GTIG) published the linked investigations on November 17 and tracks the activity as COLD RELIC. CrowdStrike tracks the Russia state-nexus espionage threat actor as GOSSAMER BEAR (aka Star Blizzard). CrowdStrike assesses with moderate confidence GOSSAMER BEAR is likely attributable to Russia’s Federal Security Service (FSB). It assesses officers affiliated with the FSB’s 18th Center likely conduct the activity, at least partly from the Komi Republic.
Google identifies both victims only as US-based organizations and names neither sector. Tenant access ended when GOSSAMER BEAR was removed. The stolen names and conversations remained available, along with the projects and relationships needed to approach people outside it.
First Victim Becomes the Next Lure
GOSSAMER BEAR reached the first organization through a residential proxy in the United States near the victim’s location. Residential proxy networks route traffic through consumer internet connections, making a sign-in resemble a local user rather than a server in an overseas data center. The geography helped the log-in avoid impossible-travel detections before the threat actor began changing the account around it.
The stolen Super Admin credentials still needed a second factor. GOSSAMER BEAR generated repeated multi-factor authentication (MFA) push notifications until the user accepted one, a technique known as MFA fatigue. Whatever other protections existed, the organization still allowed its highest-privileged Workspace account to authenticate through an approval prompt. Google identifies security keys as its strongest form of two-step verification, and they would not have presented the user with a request capable of being accepted from the threat actor’s sign-in.
GOSSAMER BEAR registered a device model never before seen in the tenant after the successful log-in. It added passkeys, backup codes, and rogue MFA devices, giving the threat actor several independent ways back in. A passkey is a cryptographic sign-in credential associated with a device or account. Passkeys resist phishing when the legitimate user controls enrollment. After account takeover, a threat-actor-enrolled passkey becomes persistence. GTIG found unrevoked passkeys survived password and session resets and bypassed the victim’s device-registration controls.
The Super Admin account also gave GOSSAMER BEAR access to the organization’s data at tenant scale. The threat actor shared files in bulk with an email address it controlled and downloaded others directly. It initiated a domain-wide export through Google Workspace Customer Takeout, an administrative function able to export an organization’s data. It exported full employee lists and synchronized inboxes through OAuth to external email clients. Google Workspace records third-party application authorization and data access in its OAuth logs. Searches covered credentials, personnel records, email archives, and documents matching its collection requirements.
Google Workspace records a tenant-wide export as CUSTOMER_TAKEOUT_CREATED. Sudden external sharing to a consumer email address creates another trail. Google’s login audit events include the enrollment of a new passkey. Repeated MFA challenges followed by passkey enrollment and device registration form a pattern difficult to explain as routine administration. Any one of those actions can be legitimate on its own.
GOSSAMER BEAR also inspected the records capable of exposing it. The threat actor queried security investigations and email audit logs through the Admin Console. GTIG says it viewed, modified, and deleted Alert Center notifications in an attempt to remove forensic evidence of the initial intrusion. Google does not identify the notification types.
Google’s own documentation says deleted alerts remain recoverable for 30 days, while Alert history records administrative changes. Deletion therefore did not immediately erase every trace. The compromised Super Admin account could still change the primary view defenders relied on while investigating activity performed through the same identity. High-risk administrative actions affecting alert state need an independent record outside the authority of the account performing them.
One Identity System Opened Another
The second organization used Microsoft Entra ID as the federated single sign-on (SSO) provider for Google Workspace. Federation lets one identity system authenticate a user into another. It reduces the number of credentials employees manage, but it also extends the security boundary across both clouds. GOSSAMER BEAR stole Entra ID credentials, then used the established trust to reach data held in Google Workspace. Denmark’s population-register breach exposed the same distinction between a valid identity and a legitimate purpose.
The threat actor approached the target through an encrypted messaging application while impersonating an employee from the first victim. It shared spear-phishing links during the conversation. The links redirected through a compromised website to document lures matching the discussion, while their parameters referenced the first organization. A related redirector submitted to VirusTotal in June 2026 carried the earlier victim’s name inside its query string.
The redirector kept the final credential-stealing domain out of the first message and allowed the server to decide which visitors should continue. Microsoft documented GOSSAMER BEAR using the same broad design with server-side scripts able to identify automated analysis before selected visitors reached Evilginx. Evilginx is an adversary-in-the-middle phishing framework built to capture credentials and authenticated sessions. GTIG does not identify Evilginx in the two new intrusions, so the earlier campaign establishes tradecraft rather than the tool used here.
After the second target authenticated, GOSSAMER BEAR enrolled a new MFA device in the SSO environment. It downloaded files available through the compromised user’s cloud drive. GTIG does not report Super Admin access at the second organization or another tenant-wide export. The messaging profile later changed to the name of a new person, which Google assesses was likely preparation for further targeting. Google does not publicly confirm a third compromise.
The intrusion crossed Entra ID, Google Workspace, a messaging application, and data stolen months earlier from another organization. Entra ID authenticated the user into Google Workspace, while the conversation and lure lived outside both platforms. A defender searching only the second victim’s email gateway would miss the approach because no email delivered it.
A reset inside one platform can also produce false closure. Microsoft warns Entra ID cannot directly revoke a session token issued by another application. Responders have to revoke active sessions, remove unrecognized MFA methods, review application consent, and inspect connected services on both sides of the federation. Forgotten MSP integrations created the same persistence problem at another layer, where approved application identities retained authority after the work justifying them had ended.
Stolen Archives Become Targeting Infrastructure
GOSSAMER BEAR has built believable approaches from public information for years. A joint advisory from eight allied cyber and intelligence agencies describes research across social media and professional networks, impersonation of known contacts, and patient conversations before a malicious link appears. The new reporting shows what a prior compromise adds. The victim has already stored information the threat actor once had to assemble from public sources.
An employee directory supplies names, titles, reporting lines, and email addresses. Resumes reveal careers and former employers. Event schedules show who expects to meet whom. Mail archives preserve writing habits, private references, unfinished work, and relationships never published on LinkedIn. Together, those records identify whom a target trusts and what the trusted person would plausibly ask about now.
My analysis of the Chainalysis breach examined how customer records can map investigators, regulators, and compliance staff working against cryptocurrency crime. Metadata exposed undercover personnel without revealing their assignments directly. GOSSAMER BEAR took the next observable step. It used records stolen from one organization to select an identity, establish a conversation, and deliver a lure against another.
One successful compromise can therefore generate targeting material for another. The second organization can produce another directory, another archive, and another set of professional relationships. GOSSAMER BEAR still has to make contact, sustain the pretext, and obtain authentication. Stolen context improves the approach while leaving success dependent on a reachable target and a convincing lure.
I assess with high confidence GOSSAMER BEAR treats contact and relationship data as operational material. The judgment rests on the linked victims and the threat actor’s longer history of stealing contacts for follow-on targeting. I assess with moderate confidence it collects some documents for their future spear-phishing value as well as their intelligence content. GTIG observed searches for rosters, contact lists, resumes, and event schedules. The public record does not disclose an FSB collection requirement separating those purposes.
Two documented intrusions cannot establish how often this model succeeds. GTIG linked the second approach to information stolen from the first. The same reporting does not measure failed conversations, abandoned lures, or people who recognized the impersonation. The evidence supports a repeatable collection method. Its success rate remains unknown.
Collection Can Become Influence
Government records place GOSSAMER BEAR closer to the Russian state than vendor telemetry can alone. The US Justice Department charged FSB officer Ruslan Peretyatko and Andrey Korinets in 2023 over a campaign targeting US and allied government personnel, defense contractors, researchers, and journalists. The indictment identifies an operational unit inside FSB Center 18 with the Callisto Group. Eight allied agencies separately assess Star Blizzard is almost certainly subordinate to the FSB’s Centre 18.
The historical record also shows two uses for stolen information. GOSSAMER BEAR collected information from targeted accounts, while data from some earlier intrusions later entered public influence activity. The United Kingdom says compromised UK-US trade documents were leaked before its 2019 election. Documents stolen from the Institute for Statecraft and its founder were also released, with selected data amplified in support of Russian confrontation goals.
Nothing in GTIG’s 2026 reporting shows data from either American organization was published, altered, or supplied to an influence campaign. Treating every GOSSAMER BEAR compromise as preparation for a leak would outrun the evidence. The precedent still affects the risk calculation because an archive collected for intelligence can later supply authentic records for selective release.
A release built around authentic documents can still mislead through selective publication, omitted correspondence, and timing. A foreign intelligence service can also mix authentic and altered files. The victim knows an archive was stolen, while an outside audience examining a later release may not know which documents were withheld or changed.
Victims Beyond the Tenant
The first organization removed GOSSAMER BEAR from its tenant and remained useful to the threat actor afterward. GTIG observed accounts impersonating employees of the first victim approach internal staff and people in the same professional circles after the infrastructure access was removed. The linked intrusions add relationships to the systems, accounts, and data an incident response normally scopes.
Every partner represented in the stolen correspondence inherited risk from an incident on someone else’s network. Those partners may not know their names, current projects, or trusted contacts now sit inside GOSSAMER BEAR’s targeting data. The first organization can clean its accounts and devices without removing copies of the data already taken.
TA419 reached American AI policy experts by impersonating a former White House official and an Anthropic employee known inside the targets’ professional circles. GOSSAMER BEAR had a deeper source for the same type of pretext. Private correspondence could show which relationship was active, what the participants were discussing, and which request would fit the conversation.
Most organizations do not maintain a list of everyone requiring a warning after their directory and correspondence are stolen. Breach teams focus on exposed data subjects and direct harms. Security teams focus on users, devices, tokens, and applications under their control. Neither practice naturally identifies the foreign policy expert at another institution whose only exposure was appearing repeatedly in a compromised employee’s inbox.
A useful response would score external relationships for follow-on targeting. Recent correspondents and event participants belong on the list. Government contacts, defense partners, former employees, and people named in collection-sensitive documents do too. Warnings should travel through a previously trusted channel and identify the impersonated person, likely conversation themes, and a separate route for verifying future contact.
The first organization is unnamed, so the public cannot determine whether downstream contacts received a warning. Google also does not say when the two victims connected the intrusions or whether the second knew its lure originated in information stolen from the first. The defensive value of identifying the relationship depends on how quickly the first victim’s professional network learns it has become part of the incident.
Attribution Beyond the Two Intrusions
The techniques inside these cases are not unique to an intelligence service. eCrime threat actors use MFA fatigue, residential proxies, cloud synchronization, and rogue authentication methods. Business email compromise can move through the same identity systems and create similar logs. Those mechanics explain how the intrusions worked, but they cannot attribute them to the FSB on their own.
The attribution draws on a longer record. Google links the activity to a threat actor it has tracked since 2015. CrowdStrike assesses an FSB connection with moderate confidence. A joint assessment from eight allied agencies places Star Blizzard under Centre 18 with an almost-certain judgment. The Justice Department has named an alleged Center 18 officer in the activity. As I argued in Attribution Is a Confidence Game, multiple public assessments may depend on overlapping evidence. The number of government signatories cannot be treated as independent corroboration.
The victimology also fits espionage better than criminal access. GOSSAMER BEAR has targeted government officials, defense contractors, non-governmental organizations (NGOs), and think tanks. Former intelligence officers, journalists, and people connected to Ukraine also appear in its victimology. GTIG describes mass collection and follow-on targeting in the two new cases without reporting extortion, resale, or fraud. Criminal access remains technically possible. The longer targeting record and government attribution weigh strongly toward espionage.
Google’s position shapes the public record. It owns Google Workspace, issued the relevant audit events, investigated the incidents, and published the findings through GTIG. This visibility makes Google’s account unusually detailed inside Workspace. It also leaves activity outside Google’s products dependent on what the affected organizations and their other providers supplied during the investigations.
The same company recommends Workspace controls and its Advanced Protection Program in the remediation section. The recommendations fit the observed failures, especially phishing-resistant authentication, restricted passkey enrollment, and complete session revocation. Google’s commercial role does not invalidate them.
GTIG’s two cases can also create the false impression GOSSAMER BEAR has moved entirely into cloud identity abuse. The threat actor has delivered custom malware before. Google documented the SPICA backdoor in 2024 and LOSTKEYS document-theft malware in 2025. It observed another malware sequence five days after publishing LOSTKEYS, including the MAYBEROBOT PowerShell backdoor. The new reporting documents cloud-focused tradecraft in these intrusions, while the wider activity still includes malware.
Hunting Across the Identity Estate
GOSSAMER BEAR selects residential proxy exit nodes near each victim, so the infrastructure can change while the log-in still appears local. A successful log-in from a familiar city should not suppress scrutiny when it follows repeated MFA challenges and precedes a new device, passkey, backup code, or authentication method.
Privileged accounts deserve alerts for every new authentication method. The same applies to CUSTOMER_TAKEOUT_CREATED, full employee-list exports, sudden external sharing, and bulk downloads from cloud storage. Queries against security investigation logs become more important when the querying account is also under investigation. Modification or deletion of alerts by the affected identity should create a record in a security system the identity cannot alter.
Remediation has to remove every route back in. A password reset does not delete a threat-actor-enrolled passkey. Revoking a browser session does not necessarily remove OAuth access, backup codes, or registered devices. Sessions issued by connected applications require separate attention. Microsoft’s compromised-account guidance calls for disabling the account and revoking active sessions. Responders must also remove unknown MFA methods, review application consent, check roles, and inspect forwarding rules across both identity environments.
Phishing-resistant authentication would have closed the original MFA fatigue route, but enrollment needs protection too. Fast IDentity Online 2 (FIDO2) uses WebAuthn, a browser standard binding public-key authentication to the legitimate service and removing the approval prompt GOSSAMER BEAR exploited. A threat actor holding administrative access can still attempt to register its own method. New enrollment for privileged accounts should require approval from an existing administrator or identity verification through another channel.
The first victim also has to investigate beyond its systems. Employees should search for consumer email accounts, messaging profiles, and domains impersonating their names. Partners should know which identities and projects appeared in the stolen data. Verification has to move to a channel trusted before the incident because replying inside the suspicious conversation leaves the impersonator in control of the answer.
By the time the first organization removed GOSSAMER BEAR, its directory and correspondence had already crossed the boundary defenders controlled. Password resets and session revocation clean the tenant. They cannot withdraw every name, relationship, and unfinished conversation available for impersonation. The second intrusion began with the residue of the first, and every unnotified person represented inside that archive remains part of its unfinished incident response.
Analyst Annex
Evidence status as of November 18, 2026. The records cover the linked late-2025 and 2026 compromises of two unnamed US organizations published by Google Threat Intelligence Group (GTIG), with attribution and historical context from CrowdStrike, the US Department of Justice, the United Kingdom National Cyber Security Centre, and Microsoft. GTIG published no victim domains, phishing domains, IP addresses, email addresses, or file hashes for the two principal intrusions. The mapping therefore stays with reported behavior and excludes session-cookie theft, malware execution, and any third compromise because the public evidence does not establish those procedures. GTIG maps the OAuth inbox synchronization to T1528, Steal Application Access Token. This annex omits that row because GTIG confirms OAuth mail synchronization but does not state that GOSSAMER BEAR stole or acquired the token used to authorize it.
Confirmed marks evidence published by a victim, vendor, regulator, or government authority about its own systems, decisions, or investigation. Reported marks technical findings or attribution assessments published by a third party. Claimed marks statements by a seller or self-identified threat actor that remain unverified. Provisional marks an analytical mapping supported by evidence but not made by the original source.
Indicators
GTIG published no network or cryptographic indicators for the two linked intrusions. The table is capped at 11 Google Workspace audit events and authentication artifacts from GTIG’s detection guidance. None is malicious in isolation. Use them as behavioral pivots only when joined to the affected identity, source network, device history, privilege level, and adjacent activity.
| Indicator | Context | Status |
|---|---|---|
| Google Workspace Audit Events | ||
CUSTOMER_TAKEOUT_CREATED |
Records creation of a tenant-wide Customer Takeout export. GTIG observed GOSSAMER BEAR initiate this export through the compromised Super Admin accountSource: GTIG | Reported |
Authorize |
Google Workspace OAuth event useful for detecting a new client receiving broad mail scopes. GTIG observed inbox synchronization to external email clients, but the report does not identify a specific client or authorization record from the incidentSource: GTIG | Reported |
User Sharing Permissions Change |
Drive audit event associated with changed sharing permissions. GTIG recommends joining spikes in this event to newly external recipients after observing mass file sharing to a threat actor-controlled accountSource: GTIG | Reported |
shared_externally |
Drive visibility value identifying external sharing. It becomes useful when a privileged identity changes many files to this state or shares them with a new consumer email accountSource: GTIG | Reported |
Batch Delete Operation Performed |
Alert Center event associated with deleting alerts. GTIG observed GOSSAMER BEAR view, modify, and delete notifications after querying defensive recordsSource: GTIG | Reported |
User List Download |
Admin event associated with exporting a directory list. GTIG observed the threat actor export full employee lists for collection and follow-on targetingSource: GTIG | Reported |
Investigation Query |
Admin event associated with security investigation queries. Unexpected queries by a newly accessed or reconfigured privileged account can expose counter-investigation activitySource: GTIG | Reported |
Item search performed |
Drive event associated with searching stored files. GTIG recommends reviewing searches for archive and credential terms when joined to abnormal downloads or a newly accessed administrative identitySource: GTIG | Reported |
| Authentication Artifacts | ||
Passkey enrolled |
Google Workspace login event for passkey enrollment. GTIG observed threat actor-enrolled passkeys survive password and session resets when responders left them in placeSource: GTIG | Reported |
Device Registered |
Device-registration event. GTIG observed a device model never before seen in the first tenant after the successful MFA fatigue attemptSource: GTIG | Reported |
Backup code |
Login Challenge Type value for authentication with an MFA backup code. GTIG observed GOSSAMER BEAR use backup codes to retain accessSource: GTIG | Reported |
MITRE ATT&CK Mapping
| Tactic | Technique | Procedure | Status |
|---|---|---|---|
| Linked US Cloud Intrusions | |||
| Reconnaissance | T1598.003Phishing for Information: Spearphishing Link | GOSSAMER BEAR shared links through a secure messaging conversation while impersonating an employee from the first victim. The links were designed to collect Microsoft Entra ID credentials and authentication tokens. The public reporting confirms stolen credentials, but not token theftSource: GTIG | Provisional |
| Resource Development | T1584.004Compromise Infrastructure: Server | The initial link used a compromised website as a redirector before selected visitors reached the credential-phishing infrastructureSource: GTIG | Provisional |
| Initial Access | T1078.004Valid Accounts: Cloud Accounts | GOSSAMER BEAR authenticated to the first victim with stolen Google Workspace Super Admin credentials and later used stolen Microsoft Entra ID credentials to reach the second victim’s federated Google Workspace environmentSource: GTIG | Reported |
| Persistence | T1098.005Account Manipulation: Device Registration | The threat actor registered a previously unseen device, passkeys, backup codes, and rogue MFA devices after compromising the first Super Admin account. It enrolled a new MFA device after compromising the second victim’s federated identitySource: GTIG | Reported |
| Credential Access | T1621Multi-Factor Authentication Request Generation | GOSSAMER BEAR repeatedly generated MFA push notifications until the first victim’s Super Admin accepted oneSource: GTIG | Reported |
| Credential Access | T1552.001Unsecured Credentials: Credentials In Files | GOSSAMER BEAR searched Google Drive for passwords and other credential material stored in filesSource: GTIG | Reported |
| Discovery | T1087.004Account Discovery: Cloud Account | The threat actor exported full employee lists from the first victim’s Google Workspace tenantSource: GTIG | Reported |
| Discovery | T1083File and Directory Discovery | GOSSAMER BEAR searched cloud storage for .pst email archives and other files matching collection termsSource: GTIG |
Reported |
| Discovery | T1654Log Enumeration | GOSSAMER BEAR queried security investigation and email audit logs through the Admin Console to inspect defensive visibility. This replaces GTIG’s published T1082 mapping with the current technique matching the observed actionSource: GTIG | Provisional |
| Collection | T1114.002Email Collection: Remote Email Collection | The threat actor synchronized email inboxes through OAuth to external email clients and searched for email archivesSource: GTIG | Reported |
| Collection | T1119Automated Collection | The compromised Super Admin account initiated Google Workspace Customer Takeout, an administrative export capable of collecting tenant-wide data. GTIG reports the export request but does not state whether every exported object completed transferSource: GTIG | Reported |
| Collection | T1530Data from Cloud Storage | GOSSAMER BEAR downloaded the first organization’s cloud storage and later performed a bulk download of files available through the second victim’s compromised cloud-drive accountSource: GTIG | Reported |
| Stealth | T1684.001Social Engineering: Impersonation | The threat actor impersonated an employee from the first victim while approaching a person at the second organization, then changed the messaging profile to a different person after the compromiseSource: GTIG | Provisional |
| Defense Impairment | T1685.002Disable or Modify Tools: Disable or Modify Cloud Log | GOSSAMER BEAR viewed, modified, and deleted Google Alert Center notifications while attempting to remove forensic evidence. The current ATT&CK release moved this behavior from the retired T1562.008 identifier to T1685.002Source: GTIG | Reported |
| Exfiltration | T1537Transfer Data to Cloud Account | The compromised Super Admin account mass-shared files from the victim’s Google Drive to an email account controlled by GOSSAMER BEAR. T1537 describes transfer through cloud-native sharing to another account more precisely than GTIG’s published T1567.002 mappingSource: GTIG | Provisional |
Entities
| Entity | Role | Status |
|---|---|---|
| Threat Actors | ||
| GOSSAMER BEAR (aka Star Blizzard)Threat actor, nation state | CrowdStrike designation for the Russia state-nexus espionage threat actor linked to credential theft and intelligence collection. CrowdStrike assesses with moderate confidence the adversary is likely attributable to Russia’s FSBSource: CrowdStrike | Reported |
| COLD RELIC (aka COLDRIVER and UNC4057)Threat actor designation | GTIG designation for the activity responsible for the linked late-2025 and 2026 intrusions. GTIG also associates the activity with Star Blizzard, Callisto, and GOSSAMER BEARSource: GTIG | Reported |
| Government Bodies | ||
| Federal Security Service Center 18Government intelligence component | Russian FSB component to which eight allied agencies assess Star Blizzard is almost certainly subordinate. CrowdStrike separately assesses officers affiliated with the center likely conduct GOSSAMER BEAR activitySources: Allied advisory, CrowdStrike | Reported |
| Organizations and Victims | ||
| First Unnamed US OrganizationVictim organization | Late-2025 victim whose Google Workspace Super Admin account was compromised. GOSSAMER BEAR stole cloud data, mail, employee records, and relationship information later used in follow-on targetingSource: GTIG | Reported |
| Second Unnamed US OrganizationVictim organization | 2026 victim using Microsoft Entra ID as the federated identity provider for Google Workspace. GOSSAMER BEAR used an identity from the first victim in the spear-phishing pretextSource: GTIG | Reported |
| Platforms and Services | ||
| Google WorkspaceCloud productivity platform | Principal cloud environment compromised at both victims. The first intrusion reached Super Admin privileges and tenant-wide dataSource: GTIG | Reported |
| Microsoft Entra IDIdentity provider | Federated single sign-on provider for the second victim’s Google Workspace environment. The threat actor stole Entra ID credentials and enrolled a new MFA deviceSource: GTIG | Reported |
| Google Workspace Customer TakeoutAdministrative export service | Tenant-wide export function initiated through the compromised Super Admin account during the first intrusionSource: GTIG | Reported |
| Google Alert CenterCloud security service | Security-notification interface GOSSAMER BEAR viewed, modified, and deleted while attempting to reduce forensic visibilitySource: GTIG | Reported |
Related Activity
The table covers separate historical GOSSAMER BEAR activity, and none of its domains, accounts, charged individuals, seized infrastructure, malware, or leaked data was observed in the two principal intrusions.
| Item | Detail | Status |
|---|---|---|
| Microsoft Star Blizzard Phishing ActivityCredential-phishing activity, 2023 to 2024 | Microsoft documented Star Blizzard using multi-stage redirection, legitimate open redirectors, server-side filtering, and Evilginx for credential and session theft. GTIG reported a compromised redirector in the 2026 intrusion but did not identify Evilginx or the earlier infrastructureSource: Microsoft | Reported |
| Ruslan Peretyatko and Andrey Korinets IndictmentIndictment, 2023 | The Justice Department charged FSB officer Ruslan Peretyatko and Andrey Korinets in 2023 over alleged Callisto Group spear-phishing and account compromise. The indictment does not identify either person in the principal casesSource: US Department of Justice | Confirmed |
| 2024 Callisto Group Infrastructure DisruptionInfrastructure disruption, 2024 | The Justice Department seized 41 domains, while Microsoft pursued 66 additional domains used by the same threat actor. The action confirms disruption of historical infrastructure but does not connect the 2026 redirector or messaging account to either seized setSource: US Department of Justice | Confirmed |
| SPICAMalware, 2024 | Rust backdoor delivered through a fake decryption utility after an impersonation account sent an unreadable PDF lure. Google attributed SPICA to the same threat actor in 2024Source: Google Threat Analysis Group | Reported |
| LOSTKEYSMalware, 2025 | Document-theft malware delivered through a fake CAPTCHA and ClickFix sequence in 2025. GTIG observed it steal selected files and system information from Western targetsSource: GTIG | Reported |
| NOROBOT, YESROBOT, and MAYBEROBOTMalware chain, 2025 | Related malware chain operationalized after GTIG published LOSTKEYS. The sequence expanded from a downloader into Python and PowerShell backdoors, but GTIG did not connect it to either principal cloud intrusionSource: GTIG | Reported |
| UK-US Trade-Document LeakPolitical leak, 2019 | The UK attributed the compromise and leak of UK-US trade documents before the 2019 UK general election to the same broader threat actorSource: UK NCSC | Reported |
| Institute for Statecraft CompromisesHack-and-leak activity, 2018 | The UK reported documents stolen from the Institute for Statecraft and its founder were later leaked and selectively amplified in support of Russian confrontation goalsSource: UK NCSC | Reported |
Intelligence Gaps
| Gap | Why It Matters | What Would Close It |
|---|---|---|
| Initial acquisition of the first Super Admin credentials | The answer would determine whether the linked operation began with an earlier phishing event, credential reuse, infostealer data, insider access, or another compromise not visible in the Workspace record | Original authentication records, credential-reset history, phishing telemetry, endpoint evidence, and the first known malicious session tied to the Super Admin identity |
| Victim identities and sectors | Victim identity would determine the likely Russian collection requirement, the downstream professional network at risk, and whether the two cases represent a narrow intelligence operation or broader targeting | Victim notifications, sector disclosure, government reporting, or incident-response records identifying each organization’s mission and exposed relationships |
| Deleted Alert Center notification types | The notification types would show which detections exposed the intrusion and whether the threat actor specifically targeted government-backed attack alerts or removed generic security events | Alert history, deleted-alert recovery records, administrative audit logs, and case records preserving notification identifiers and severity |
| Volume and categories of stolen data | The answer would bound the intelligence loss, identify which contacts require warning, and separate a successful Customer Takeout request from completed tenant-wide exfiltration | Customer Takeout completion records, Drive and mail download logs, external-sharing history, OAuth client access logs, and a document-level exposure inventory |
| Follow-on use of the renamed messaging profile | Confirmation would show whether the second victim became another targeting platform and measure how quickly the threat actor repeated the model | Messaging-provider records, reports from contacted organizations, reused URL parameters, correlated redirector logs, and authentication events at suspected downstream victims |
| Notification of external contacts and professional partners | Notification timing affects whether exposed relationships remained usable before targets received an independent verification channel | The first victim’s notification plan, recipient list, delivery dates, warning content, and confirmation from downstream organizations |
| Persistence beyond the confirmed passkeys | GTIG confirms unrevoked passkeys survived password and session resets. Whether backup codes, rogue MFA devices, OAuth grants, or active sessions also survived would identify additional remediation failures and the controls requiring redesign | Before-and-after authentication-method inventories, backup-code use, device enrollment logs, OAuth grant history, session revocation records, and post-reset sign-in telemetry |
| Credential theft versus token theft in the second intrusion | The distinction changes the phishing mechanism, the expected telemetry, and whether session replay bypassed controls before the new MFA device was enrolled | Identity-provider sign-in logs, token issuance and replay telemetry, browser or proxy evidence, phishing-kit records, and the first successful Entra ID session |
| FSB collection tasking | Tasking would distinguish documents collected for immediate intelligence value from records retained primarily for follow-on spear-phishing or potential influence activity | Recovered collection requirements, threat actor tasking communications, search-term history, document-access priorities, or later use of specific stolen records |
| Later publication or transfer of stolen data | The answer would change the consequence assessment from covert intelligence collection to influence preparation, operational enablement, or wider dissemination | Leak monitoring, provenance analysis of later releases, government intelligence reporting, threat actor communications, and matches between stolen archives and published data |