2023 · Russia · M - Professional, scientific and technical activities · Cyber espionage intrusion without misuse
Analysed 2026-11-06 by Hermes
Open this case in the tool →Cyber espionage intrusion without misuse
No DV evidenced
Alternative: none defensible
(1) The strategic expectation one would assume at a Russian aerospace research institute is protection of its aerospace and defence-relevant research data and detection of intrusion into its networks - but no source documents any actual policy, standard, control, warning or statement of this institute, so no expectation can be evidenced at the doctrinal or material level. (2) What is documented: Microsoft Threat Intelligence reported on 7 September 2023 that in March 2023 Ruby Sleet compromised an aerospace research institute in Russia, as part of North Korean targeting of the Russian government and defence industry that Microsoft assessed was likely for intelligence collection while North Korea supplied materiel support to Russia's war in Ukraine; BleepingComputer noted that Microsoft gave no further detail on what was taken or how. The victim itself never disclosed or commented on the incident, its name was never published, and the EuRepoC row records the incident as hijacking without misuse (empowerment, intensity 1) with no system interference, no confirmed data breach or exfiltration and no economic impact. (3) The reporting confirms impact only: the entry vector, dwell time, containment, egress, recovery and response conduct of the institute are all undocumented. The fact that an outside vendor, not the victim, made the intrusion public does not evidence a detection gap, because no source addresses the institute's own monitoring, detection or notification at all, and the method rejects inferring a victim-side gap from the breach itself or from the attacker's technique. The only richer detail available - Ruby Sleet's documented group-wide pattern of phishing, backdoored software and targeting of aerospace and defence organisations for technology collection - is attacker-side pattern evidence about the actor, not a victim-side lifecycle mechanism at this institute. Hence Unknown: no lifecycle stage yields a defensible victim-side mechanism, and confidence is not assessable.
State-on-state cyber espionage reported only by a third-party vendor: the victim institute is unnamed in every source (searched English and Russian reporting; no Russian follow-up naming it was found) and never spoke publicly. The case file's source_url and attribution_source_url point to the Microsoft report PDF https://query.prod.cms.rt.microsoft.com/cms/api/am/binary/RW1aFyW, which now returns HTTP 404; the same September 2023 report is cited via its live Microsoft Security Insider page and the accompanying Microsoft blogs.microsoft.com post, both opened and read during research. The case file's third source_url (The Hacker News zero-day article) is mainly about a parallel Google TAG campaign against security researchers and only mentions the Russian aerospace institute as context from the Microsoft/SentinelOne reporting on Russian defence targeting. Per the method spec's decision rule, set Unknown because the sources confirm the compromise only and document no victim-side mechanism at any of the six lifecycle stages; entry vector unknown and not load-bearing. Sector taken as research activity (aerospace R&D institute; EuRepoC subcategory Research) - a defence-sector reading (section O) was considered since Microsoft frames the campaign as targeting the Russian defence industry, but the described victim is a research institute. No consent-gated steps were needed in this unattended run.