← Breach analysis by the Dual Vulnerabilities framework

Kyiv residential surveillance cameras hijacking (suspected Russian intelligence services, 2023)

2023 · Ukraine · L - Real estate activities · Hijacking of internet-connected surveillance cameras for enemy reconnaissance

Analysed 2026-11-06 by Hermes

Open this case in the tool →

What happened

Hijacking of internet-connected surveillance cameras for enemy reconnaissance

Dual vulnerability type

Expertise to Execution

Evidence coverage: 2/6 stages, weight 11/60

Decisive stage: entry (clearest evidence) · Alternative: Strategy to Execution

Why this classification

(1) The expectation at the victim side was technical and widely published: owners of online cameras should keep them out of reach and off the public internet - the SBU has blocked about 10,000 IP cameras since 2022, repeatedly calls on owners to stop online broadcasts, and Ukraine criminalises publishing footage of strikes (Article 114-2 CCU). (2) In practice, two residential cameras in Kyiv - a balcony camera run by a condominium and a car-park camera run by residents - stayed publicly streamed; suspected Russian intelligence operators gained remote control, changed the angles, connected the feeds to YouTube and used the live view of air defences and critical infrastructure to prepare and adjust the missile and drone attack on Kyiv of 2 January 2024; neither owner noticed the tampering, and only the SBU's dismantling after the attack ended it. The intrusion vector itself is not disclosed and is not load-bearing. (3) That is a knowing-doing gap within the material column: the remedy (stop the public broadcast, harden the device, verify what the camera is doing) was known, technical and repeatedly stated by the state's cyber specialists, yet never executed by the camera operators; there is no strategic artefact on these private owners' side whose non-execution would make this a Strategy-to-Execution case, and no documented leadership decision that deferred the remedy - the decisive stage is the entry/exposure stage (clearest evidence), with the detection gap pointing the same way. RM27 (Expertise to Execution lens): no one with configuration expertise maintained these devices, so residential cameras stayed insecurely configured and unnecessarily exposed to the open internet - the scale of the condition is evidenced by the roughly 10,000 exposed cameras the SBU has blocked and its appeal to all owners to stop broadcasting, and here the exposed camera let the intruder take remote control and re-route the stream (causal role: Enabling). RM34 (Expertise to Execution lens): no monitoring of the devices was configured at all, so the camera's changed angle and its covert connection to a public YouTube stream were never detected by the owners and only surfaced through the SBU's external intervention after the attack had already been adjusted with this footage (causal role: Obscuring).

Evidence by stage

Risk markers

Sources

Notes

Victim is diffuse: the dataset codes receiver category End user(s) / specially protected groups and names no organisation; the victims are private residents / condominium associations in Kyiv, so sector coding is approximate - L Real estate activities chosen as the closest section for residential-building/condominium operation, though the method spec would prefer blank for a diffuse-population case. Year follows eurepoc_extra.start_date (01.01.2023) per the pipeline convention for EuRepoC rows; all dated events in the record fall in January 2024 (attack on 2 January 2024, SSU statement 2 January 2024, attribution_date 02.01.2024), so the start_date likely reflects EuRepoC's assumed start of the longer camera-access campaign (the SBU reports blocking cameras since February 2022). The SBU claim that the footage aided the 2 January 2024 strike is stated as 'according to available information' and is not independently verifiable. The case file's source_url list also contains unrelated roundup links (Wired 23andMe roundup, BleepingComputer Kyivstar item, Wired interview, Security Affairs newsletter) that describe other incidents and were not relied on. EuRepoC codes intelligence_impact as no data breach/exfiltration while the hijacking field scores 2 points: the live streaming is misuse of the feed rather than bulk data theft. Structural context (not coded for this case): the RFE/RL Schemes investigation found cameras running Russian TRASSIR software relayed footage via Moscow servers linked to the FSB and that Ukraine only began abandoning the software after the invasion; whether these two cameras ran TRASSIR is not documented. No related_rows in the case file. Link check: ssu.gov.ua blocks automated access (HTTP 403); the page was opened and read during research. No consent-gated action was required in this run.