← Breach analysis by the Dual Vulnerabilities framework

StarLight Media & Inter TV broadcast hijack (Russian-linked hackers, 2024)

2024 · Ukraine · J - Information and communication · Satellite broadcast signal hijacking and content replacement

Analysed 2026-11-06 by Hermes

Open this case in the tool →

What happened

Satellite broadcast signal hijacking and content replacement

Dual vulnerability type

Strategy to Execution

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

Decisive stage: response (clearest evidence) · Alternative: Expertise to Execution

Why this classification

(1) Strategic expectation: Ukrainian national broadcasters operating in wartime under documented, near-continuous Russian interference on the shared Astra 4A satellite platform were expected to keep their delivery chain protected and resilient - the media regulator's own 9 May 2024 statement records constant monitoring of such interference, SES's report that interventions constantly originate from the aggressor country's territory, and a standing recommendation to use alternative signal-reception paths and to respond promptly. (2) In practice: on 9 May 2024 interference plus content replacement put Moscow's Victory Day parade on the StarLight Media channels from 10:00 to 10:18 (Nacrada: at least 15 StarLight channels affected); the channels promptly launched the shutdown protocol, yet the intrusion returned - interference resumed shortly after the 11:27 restoration (SES cut the signal at 11:29) and a fresh content-replacement attack succeeded at 12:51 after the 12:43 re-enable, forcing another shutdown until 14:20; Inter reported its own channels were hit by interference (its update via SES Astra recorded a 17-second interruption and no content change) but not parade content. (3) The classification rests on the response stage: the expectation to keep the broadcast path secure under repeated attack is doctrinal (regulator statement and incident record), and the chain broke in execution - the security protocol was followed but the exposure was never eradicated from the delivery chain, so each restoration re-opened it; no source shows leadership deferring, under-resourcing or accepting the risk, and the entry technique (RF interference/injection on the shared satellite transponder) is not itself treated as a victim-side DV (attacker-technique reasoning is excluded), nor specified beyond the shared Astra 4A feed. Earlier comparable hijacks at the same victims (Inter, 23 February 2023; StarLight Media, 24 April 2024) show the same weakness recurring without durable architectural change. RM21 (Strategy to Execution lens): the prior hijacks and the regulator's repeated warnings did not become a durable change in the delivery architecture, so the same content-replacement weakness recurred within weeks and three times in one day (causal role: Perpetuating). RM38 (Strategy to Execution lens): after detection the incident was not eradicated - despite the shutdown protocol working as designed, interference resumed within minutes of each re-enabled feed, so access to the broadcast returned instead of being removed (causal role: Amplifying). RM32 (Strategy to Execution lens): availability protection for the sole satellite delivery path was not implemented - no interference-resilient or pre-diversified reception kept services on air, leaving broadcasts repeatedly off-air under attack until late in the day (causal role: Enabling).

Evidence by stage

Risk markers

Sources

Notes

Source caveats: attribution stays at the alleged level - Ukrainian authorities and the regulator point to Russia (SES: interventions constantly from the aggressor country's territory), but no named group was confirmed. The incident's technical mechanism was never published by a forensic investigation, so the victim-side mechanism rests on incident reporting and the regulator's statement. Data quality: the case file states has_disruption=False and functional_impact 'No system interference/disruption' although the same description and the sources report an 18-minute content replacement and several shutdowns on 9 May 2024; the description's second sentence (satellite disruption on Dym and Apostroph-TV) describes channels other than the two listed victims, which were themselves the primary targets (at least 15 StarLight channels, per Nacrada); source_disclosure 'Incident disclosed by attacker' does not fit the record - the broadcasters, Detector Media and Nacrada disclosed it on the same day. Inter's own update via SES Astra recorded a 17-second interruption on its channels with no content change. EuRepoC row 333 / incident_id 3457.