Bank Data Breach Blamed on Insider As Social Security Numbers, Account Information and Addresses of 43 Customers Exposed - The Daily Hodl

GateUser-299f2bac

A US bank is blaming one of its own employees for the exposure of the sensitive data impacting dozens of customers.

According to a new filing with the Office of the Maine Attorney General, an insider at TD Bank wrongfully accessed the data of 43 customers.

The breach is reported to have occurred on June 13th, 2024, but it wasn’t discovered until this year, on March 6th.

Impacted customers are being delivered written notices.

A copy filed with the Office of the Maine Attorney General says the personal information that may have been accessed include names, dates of birth, phone numbers, addresses, account numbers, social security numbers and transactional data.

The bank says its corporate security team has launched an internal investigation in the matter and has also reached out to local law enforcement.

TD Bank is offering those impacted a free two-year enrollment to an identity protection service to affected customers.

With $372.8 billion in assets under management as of December 2024, TD Bank is the 10th largest bank in the United States.

Follow us on X, Facebook and Telegram
Don’t Miss a Beat – Subscribe to get email alerts delivered directly to your inbox
Check Price Action
Surf The Daily Hodl Mix
Generated Image: Midjourney

Disclaimer: The information on this page may come from third parties and does not represent the views or opinions of Gate. The content displayed on this page is for reference only and does not constitute any financial, investment, or legal advice. Gate does not guarantee the accuracy or completeness of the information and shall not be liable for any losses arising from the use of this information. Virtual asset investments carry high risks and are subject to significant price volatility. You may lose all of your invested principal. Please fully understand the relevant risks and make prudent decisions based on your own financial situation and risk tolerance. For details, please refer to Disclaimer.
Comment
0/400
No comments