← Breach analysis by the Dual Vulnerabilities framework

WMATA Website DDoS attack (Unattributed, 2024)

2024 · United States · H - Transport and storage · Distributed denial-of-service attack on public website

Analysed 2026-11-06 by Hermes

Open this case in the tool →

What happened

Distributed denial-of-service attack on public website

Dual vulnerability type

No DV evidenced

Alternative: none defensible

Why this classification

(1) As a US critical-infrastructure transit authority, WMATA was expected to keep its public web front (wmata.com) available under attack and to disclose incidents accurately. (2) On the evening of 7 May 2024 a denial-of-service attack made the website unreachable; Metro tweeted at 7:51 p.m. local time that the site was temporarily down, restored it within about two hours, stated that no customer or employee data was compromised and that wmata.com was not breached, and that customer-facing services including the SmarTrip app and mobile transactions were not impacted; the agency notified the TSA, and the FTA and CISA were made aware. The actor was never identified, no one claimed the attack, and no investigation outcome on the incident was published: the WMATA OIG semiannual report covering January-June 2024, opened during this research, does not mention it. (3) The entry vector is known (a DDoS flood) but is not load-bearing for the DV assessment, and it is the only stage where a victim-side condition could even be suspected: the two-hour outage is reported purely as impact, with no source describing WMATA's DDoS protection, mitigation capacity or whether the site was taken down deliberately as a countermeasure, and the reporting itself is inconsistent on that point (the CSIDB summary says the attack 'forced' WMATA to take the site offline, while the victim's own statements give no such detail). Detection and disclosure were prompt and accurate the same evening, restoration took about two hours, there was no data at risk at the egress stage, and containment was not in play because the site was not breached. With no documented gap at any lifecycle stage and no formal investigation finding to lean on, the decision rule applies: the reporting confirms impact only, so the case is set to Unknown rather than forcing a DV-Type that would reason from the attacker's technique succeeding. No risk marker is coded for the same reason; the suspected availability condition is described here rather than coded, because no evidence shows the protection was materially insufficient rather than overwhelmed by a strong flood or bypassed by a deliberate takedown. A separate earlier incident at the same victim (January 2023, a former contractor's unrevoked credentials used from Russia) is a different mechanism and not comparable to this disruption, so no recurring-weakness reading applies.

Sources

Notes

EuRepoC row; description matches the stated victim. Evidence base: victim's own tweet (opened) and statements carried by NBC4 Washington and WUSA9 (both opened, 14 May 2024); no attribution ever followed and no attack claim. WUSA9 reported the TSA was investigating; no public outcome of that investigation was found, and the WMATA OIG Semiannual Report No. 34 (Jan-Jun 2024, opened as text) does not mention this incident, so there is no formal finding to support 'No DV evidenced' either. The two-hour downtime is not coded as a capacity gap: no source describes WMATA's DDoS protection or whether the site was taken offline deliberately as mitigation. The tweet displays 11:51 PM May 7 2024 in X's UTC rendering; NBC4 reports 7:51 p.m. local time for the same post. Metro told NBC4 it deals with cyberattacks 'pretty frequently', but no specific earlier comparable DDoS incident at WMATA was found, so RM21 was not coded. A distinct January 2023 incident (former contractor's credentials used from Russia; WMATA OIG Management Assistance Report, May 2023) was found in research and noted only as context, not part of this classification. Unattended run: no consent-requiring actions were taken; only public news, the victim's public statement and public OIG documents were read. Link check: wusa9.com blocks automated access (HTTP 403); the page was opened and read during research.