1. [News](/news) 2. TD data breach confirmed – names and social security numbers compromised Toronto-Dominion Bank (TD Bank Group) # TD data breach confirmed – names and social security numbers compromised A data breach involving TD was reported in June 2026. See incident details, impact on customers, and recommended security measures. UpGuard Team June 17, 2026 Table of Contents * [What happened in the TD data breach?](#what-happened-in-the-td-data-breach) * [Who is behind the incident?](#who-is-behind-the-incident) * [Impact and risks for TD customers](#impact-and-risks-for-td-customers) * [How to protect against similar security incidents](#how-to-protect-against-similar-security-incidents) ## Key facts: TD data breach * Date occurred January 7, 2026 - January 30, 2026 * Date reported June 15, 2026 * Target entity TD * Source of breach Insider threat (employee) * Data types Names, addresses, phone numbers, dates of birth, social security numbers, account numbers, and transactional data * Status Confirmed; reported on June 15, 2026. * Severity Medium; the exposure of social security numbers and account data significantly increases the risk of financial fraud and identity theft. ## What happened in the TD data breach? TD (td.com) reported a data breach involving customer information on June 15, 2026. The incident was classified as an insider breach, where an employee accessed sensitive data without authorization between January 7 and January 30, 2026. The compromised information includes highly sensitive details such as names, social security numbers, and bank account numbers. This medium-severity incident is currently being investigated internally, and the bank is implementing measures to enhance its data protection protocols. The exposure of such comprehensive personal and financial data typically increases the risk of identity theft and fraudulent account activity. ## Who is behind the incident? The attacker or cause of the incident has not been identified. ## Impact and risks for TD customers Affected customers face significant risks due to the exposure of social security numbers and account details. This information could be leveraged by malicious actors for identity theft, opening fraudulent accounts, or conducting unauthorized financial transactions. Additionally, the availability of phone numbers and addresses increases the likelihood of targeted phishing or social engineering attempts. Typically, incidents of this nature lead to heightened scrutiny of internal security policies and potential regulatory oversight. Affected individuals should monitor their financial statements closely, consider placing a credit freeze, and remain vigilant against suspicious communications. Transparency regarding the breach helps customers take proactive steps to secure their personal data. ## How to protect against similar security incidents Following the insider breach at TD involving sensitive financial data and social security numbers, customers should take immediate steps to secure their personal and financial information. * **Monitor financial accounts and credit reports.** Review bank statements and credit reports for any unauthorized activity or unfamiliar transactions. Set up real-time transaction alerts on your bank accounts to detect suspicious movements immediately. * **Implement a credit freeze or fraud alert.** Contact major credit bureaus to place a freeze on your credit file, preventing unauthorized accounts from being opened. Alternatively, place a fraud alert to ensure lenders verify your identity before extending credit. * **Strengthen account security with MFA.** Enable multi-factor authentication (MFA) on all financial and personal accounts where available. Use phishing-resistant MFA methods, such as hardware keys or authenticator apps, rather than SMS-based codes. * **Deploy internal security monitoring.** For organizations, implement robust internal access controls and continuous monitoring to detect anomalous employee behavior. Utilize attack surface management tools to identify and mitigate vulnerabilities across the digital infrastructure. > Taking proactive measures is essential to mitigating the long-term risks associated with the exposure of sensitive personal identifiers. ## Frequently asked questions ### What happened in the TD security breach? On June 15, 2026, TD (td.com) disclosed a security breach. According to initial reports, an employee compromised the personal information of customers between January 7 and January 30, 2026, including names, social security numbers, and account details. ### When did the TD breach occur? The TD breach was publicly reported on June 15, 2026. The exact date of the attack has not been disclosed. ### What data was exposed? The breach exposed customer names, physical addresses, phone numbers, dates of birth, social security numbers, bank account numbers, and transactional data. ### Is my personal information at risk? If you have a relationship with TD, there is a risk that your personal data was compromised in this breach. Because the incident involved identifiers like social security numbers and bank account details, it is important to stay alert for suspicious activity and take proactive steps to protect your financial identity. ### What steps should companies take after being breached? TD is investigating the incident internally, notifying affected parties, and taking measures to enhance its data protection protocols and review internal security measures. ## Is your organization exposed to a similar risk? UpGuard continuously monitors vendors for exposed credentials and infrastructure risk, so you can catch the next breach before it becomes a headline. [Start your free trial](https://cyber-risk.upguard.com/register/trial) ## How secure is Toronto-Dominion Bank (TD Bank Group)? Toronto-Dominion Bank is a major Canadian multinational financial services corporation that utilizes td.com as its official online platform to provide retail, commercial, and wholesale banking solutions to millions of customers across North America. * View our free preliminary report on Toronto-Dominion Bank (TD Bank Group)'s security posture * 13 risk factors, including email security, SSL, DNS health, open ports and common vulnerabilities [View Toronto-Dominion Bank (TD Bank Group)'s score View score](/security-report/toronto-dominion-bank) [https://td.com/](/security-report/toronto-dominion-bank) ## Latest news Stay up-to-date with the latest news in cybersecurity. * ### [Hugging Face data breach: key facts and what we know so far](/news/hugging-face-data-breach-2026-07-20) A data breach involving Hugging Face was reported in July 2026. See incident details, impact on customers, and recommended security measures. UpGuard Team July 20, 2026 * ### [EY data breach: what happened and what's at risk](/news/ey-data-breach-2026-07-19) A data breach involving EY was reported in July 2026. See incident details, impact on customers, and recommended security measures. UpGuard Team July 17, 2026 * ### [South Florida Injury & Convenient Care data breach exposes names and Social Security numbers](/news/south-florida-injury-convenient-care-data-breach-2026-07-16) A data breach involving South Florida Injury & Convenient Care was reported in July 2026. See incident details, impact on customers, and security measures. UpGuard Team July 16, 2026 * ### [Park West Psychology data breach: what happened and what's at risk](/news/park-west-psychology-data-breach-2026-07-16) A data breach involving Park West Psychology was reported in July 2026. See incident details, impact on customers, and recommended security measures. UpGuard Team July 16, 2026 * ### [Fall River Municipal Credit Union data breach: what happened and what's at risk](/news/fall-river-municipal-credit-union-data-breach-2026-07-16) A data breach involving Fall River Municipal Credit Union was reported in July 2026. See incident details, impact on customers, and recommended security measures. UpGuard Team July 16, 2026 * ### [NPCIL data breach: World Leaks claims exposure of Kudankulam Nuclear Power Plant files](/news/npcil-data-breach-2026-07-16) A data breach involving NPCIL was reported in July 2026. See incident details, impact on customers, and recommended security measures. UpGuard Team July 16, 2026 [View all news](/news) ## Sign up for our newsletter UpGuard's monthly newsletter cuts through the noise and brings you what matters most: our breaking research, in-depth analysis of emerging threats, and actionable strategic insights.