← Breach analysis by the Dual Vulnerabilities framework

Starlink DDoS outage (Killnet, 2022)

2022 · United States · J - Information and communication · DDoS attack disrupting login and authentication service

Analysed 2026-11-06 by Hermes

Open this case in the tool →

What happened

DDoS attack disrupting login and authentication service

Dual vulnerability type

No DV evidenced

Alternative: none defensible

Why this classification

(1) The expectation at Starlink is implicit rather than documented: as the satellite-internet provider whose service was critical to Ukraine's war effort, and as a target Elon Musk had publicly said had resisted Russian cyber operations so far, its public-facing login and authentication services are expected to stay available under attack. No primary source documents what availability or DDoS-protection posture SpaceX had decided or resourced. (2) What happened: on 18 November 2022 Killnet and five collaborating hacktivist groups claimed on their Telegram channels a collective DDoS attack on Starlink's website, authentication portal and API; Trustwave corroborated the impact the same day from Reddit complaints of users who could not log in for several hours, and a 2024 ETH Zurich research report places the login outage at about three hours, notes the attack reached only the customer-facing interface rather than the space, ground or user segments, and records that Starlink changed its authentication links within roughly 17 minutes; attacks on the website continued on 19 November and service was restored within the day. There was no data breach, no data theft and no reported economic loss. (3) Why this stays Unknown: the reporting confirms impact only. The vector is entirely the attacker's move - low-skill volumetric and application flooding of a public portal - and reasoning from an attacker's technique, or from the few-hour login outage alone, to a victim-side knowing-doing or doctrinal-material gap is the rejected form of inference. Entry is not load-bearing for a DV here because no source shows an expectation or knowledge (doctrinal or material) that was known and not acted on: nothing documents a DDoS-protection policy, capacity decision, expert warning or audit finding at Starlink. Detection and mitigation evidently functioned (authentication links changed within minutes, service restored within hours), egress was not in play (no data breach), recovery is not documented as constrained, and the response stage shows only victim silence - SpaceX is a private company under no incident-notification duty for this disruption and rarely comments on cyber incidents, so silence is not itself a documented gap. At the same time there is no positive evidence of doctrine-execution alignment across the lifecycle (no regulator review, no victim disclosure), which is what 'No DV evidenced' requires, so the case is Unknown: the decision rule's case where reporting confirms impact only. No risk marker is coded; a capacity or availability-protection reading would rest solely on the coder's inference from the outage's existence and duration.

Sources

Notes

Data quality: the Victim column literally holds 'Starlink;Starlink' (a duplicated dataset value); the victim is Starlink, the satellite-internet service operated by SpaceX, United States. Disclosure was by the attacker; no victim, regulator or CERT source exists for this incident, so there is no primary-source route to a victim-side mechanism. Trustwave's corroboration rests on user complaints posted on Reddit, not on its own telemetry; the Downdetector peak for 18 November is documented in the ETH Zurich report via Killnet's own Telegram screenshots, so the impact account is independent of the attacker only in part. The case file's attribution_source_url (https://t.me/killnet_reservs/3565) is the attacker's Telegram channel and was not visited per the security policy; the claim is cited as reported by Trustwave, Dark Reading and the ETH report. Of the case file's other source_urls, darkreading /edge/how-researchers-hijacked-a-satellite is mainly about satellite firmware research and mentions this 18 November attack in passing, and darkreading /ics-ot/space-race-defenses-satellite-cyberattacks covers the satellite-cybersecurity frameworks and repeats the Killnet claim; both were opened and kept as corroborating context. Do not confuse this incident with the separate global Starlink outage of 30 November 2022 (cause not publicly attributed to Killnet) or the February 2022 DDoS campaign against Starlink ground services - neither was used for this row. The dataset labels the victim 'Critical infrastructure / Telecommunications;Space'; the SBI sector follows its primary economic activity (satellite internet service). Country from eurepoc_extra.receiver_country, Year from start_date (18.11.2022). No risk markers coded: DV-Type Unknown with no documented victim-side gap at any lifecycle stage. The case file's trustwave.com article URL now redirects through the Trustwave/LevelBlue merger and ends in a 404; the same SpiderLabs article is cited at its live levelblue.com copy, which was opened and read during research.