2023 · Canada · K - Financial and insurance activities · DDoS attack with website and mobile-banking outage
Analysed 2026-11-06 by Hermes
Open this case in the tool →DDoS attack with website and mobile-banking outage
No DV evidenced
Alternative: none defensible
(1) Strategic expectation: as a systemically important Canadian bank, TD Bank was expected to keep its public web and mobile channels available under adversarial load, and the threat was explicitly on the table days before the attack - the Canadian Centre for Cyber Security alerted organisations on 23-24 February 2023 to possible disruptive attacks by Russia-aligned actors against Ukraine-aligned nations, citing the CISA alert of 23 February 2023, and the case description itself names Canada's 24 February announcement of a $32.5 million Ukraine support package as the suspected motive. (2) In practice: on 26 February 2023 a group calling itself 'We Are Russian Hackers Community' claimed a DDoS attack on TD Bank on Telegram; Le Journal de Montreal, quoting security researchers (Cyberknow; Alexis Rapin of the UQAM observatory), confirmed this was not an empty claim - the bank's Canadian websites and mobile services really were unavailable for several hours, the first verified hit on a Canadian bank since the start of the war - while EuRepoC records short-term disruption (< 24h) and no data breach, exfiltration or corruption; service was restored the same day. (3) Why the DV cannot be established: the record confirms impact only. It does not document why availability protection could not keep the services online (no account of TD's DDoS mitigation, capacity or architecture), nor any other victim-side gap - entry here is a volumetric flood of a public service with no intrusion; containment and egress are not in play (no breach or theft of data, per EuRepoC impact coding); detection is not load-bearing (the attacker disclosed the attack himself, which is also how the incident entered the public record); recovery is reported as completed within hours, not as a failing; and TD Bank made no public statement that could be tested against the facts, so the response/disclosure stage yields no documented gap either (silence about a short, data-free outage is not evidence of a disclosure failure). Under the method's decision rule this is the textbook 'reporting confirms impact only' case, so DV-Type is Unknown; the entry technique (Network Denial of Service) is attacker-side context and was not used for classification. The one visible victim-side condition is recorded as a marker rather than a DV-Type: the outage timeline (services unavailable for several hours on 26 February 2023) shows that availability protection did not keep the public channels up under attack, but no source states why, which is exactly what a DV-Type would require.
RM32 — Capacity / availability-protection gapAttribution rests on the attacker's self-claim on Telegram and on IT-security-community attribution (Cyberknow alert, Alexis Rapin); the Telegram channel was not opened (research boundaries) - the claim is cited as reported by Le Journal de Montreal. Disclosure was attacker-side (EuRepoC: 'Incident disclosed by attacker'); no TD Bank public statement about the 26 February 2023 attack was found despite targeted searches, which is itself a data-transparency caveat, not coded as a DV. Context: the CCCS/CISA vigilance alerts of 23-24 February 2023 and a CSE/Cyber Centre heightened-vigilance notice to critical infrastructure (23 February 2023) show authorities expected exactly this wave; no source shows TD received a specific warning. Data-quality caveat: TD has several distinct lookalike incidents that were checked and excluded from this classification - a September 2012 DDoS ('targeted attack', ~4h outage, covered by The Globe and Mail/CBC) and an April 2023 DDoS claimed by NoName057(16); only the 26 February 2023 event described in the row is classified. Link check: journaldemontreal.com blocks automated access (HTTP 403); the page was opened and read during research.