← Breach analysis by the Dual Vulnerabilities framework

US airport websites DDoS attack (Killnet, 2022)

2022 · United States · H - Transport and storage · DDoS attack on public-facing websites

Analysed 2026-11-06 by Hermes

Open this case in the tool →

What happened

DDoS attack on public-facing websites

Dual vulnerability type

Expertise to Execution

Evidence coverage: 1/6 stages, weight 6/60

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

Why this classification

(1) Strategic expectation: as operators of critical transport infrastructure, major US airport authorities were expected to keep their public-facing web services available under foreseeable flood traffic - the countermeasure (enrolling public sites in DDoS protection services, capacity and redundancy) was a known, officially recommended remedy; the FBI's PIN on exactly this campaign, coordinated with CISA, tells organisations to enrol in a DoS protection service and states that with DDoS mitigation steps such attacks have minimal operational impact. (2) In practice: on 10 October 2022, following Killnet's open call published a day earlier with a target list of 49 airport-related domains, about 14 public-facing airport websites were knocked offline for several hours, denying travelers booking and flight-status information; in Hawaii the attack hit the single system hosting the landing pages of 15 airport websites including Daniel K. Inouye International Airport; no internal systems were compromised - LAX stated there were 'no operational disruptions' in its public statement and the State of Hawaii reported the attack 'had no impact on internal systems, operations, or traveler safety'; sites were restored within the day (<24h). (3) The gap sits in the material column: the remedy existed at specialist level as a widely known, recommended service, but the impact shows it was not applied to a degree that kept the public web estate up - AP reports that such attacks instead 'tend to reveal insufficient attention by webmasters to adequate bulletproofing of sites, which now includes DDoS protection service'. No source names any airport policy or strategy on web availability that went unimplemented (so no doctrinal origin), and none shows leadership deferring or accepting the protection gap (so no leadership break); the chain broke at web-operations level - Expertise to Execution. The classification rests on the resilience/recovery (availability-protection) stage; there is no intrusion-based entry vector and the other stages are documented as aligned or not in play. The mechanism rests on pattern/sector-level evidence (AP's attribution of these outages to webmaster bulletproofing, official DDoS-mitigation guidance), not on incident-specific confirmation of any one airport's protection posture, which caps confidence at 3. RM32 (Expertise to Execution lens): the availability of the airport web estate could not be sustained under flood traffic because the known protection and scaling remedies were not operationalised on the public hosting - the experts' capacity and protection options were never put under the landing pages (causal role: Enabling). RM04 (Expertise to Execution lens): the dependency could not be reduced at short notice: 15 Hawaii airport websites shared one landing-page hosting platform, so a single flood took down the whole state airport web presence at once, multiplying the visible impact of an availability gap the operators could not architect away (causal role: Amplifying).

Evidence by stage

Risk markers

Sources

Notes

Dataset caveats: the Victim column lists 11 airport authorities plus one 'Not available' entry, while the row's own description and the press coverage count about 14 targeted sites, including Atlanta (ATL) and Chicago O'Hare (ORD) which are not in the Victim list; analysed as one same-day campaign against US airport public websites (10-11 October 2022). Internal row inconsistency: has_disruption is 'False' while the disruption column records 'Short-term disruption (< 24h)' and functional_impact 'Day (< 24h)'. Attribution: Killnet's self-attribution on its Telegram channel was not opened (hacktivist channels are outside the allowed research scope); the self-claim is used only as reported by AP, The Guardian and the FBI PIN. The entry was a flood of public-facing sites, not an intrusion, so there is no victim-side entry vector to assess; the DV mechanism is pattern-level (AP attribution, official DDoS-mitigation guidance), not incident-specific confirmed. No related_rows in the case file. Link check: apnews.com blocks automated access (HTTP 403); the page was opened and read during research. Link check: dod.hawaii.gov blocks automated access (HTTP 403); the page was opened and read during research.