DataBreaches.Net

Menu
  • About
  • Breach Notification Laws
  • Privacy Policy
  • Transparency Report
Menu

Keylogger captured Sovereign Bank customer data

Posted on December 31, 2010 by Dissent

By letter dated December 22,  Sovereign Bank’s Chief Privacy Officer notified the New Hampshire Attorney General’s Office of a security breach:

On October 15, Sovereign Bank… became of aware of unusual activity based on IP traffic.  Upon discovery of the issue, the Bank launched an investigation, and performed due diligence which was completed on December 15.

It was determined that an unknown entity placed a keylogger on a laptop that allowed the information of two New Hampshire customers to be viewed inappropriately. The accessed information included the customer name, address, and Social Security Number.

The total number of customers whose data were accessed was not indicated. Nor is it clear how the keylogger was installed on the laptop and whether it was one of the bank’s laptops or if an employee had connected using a personal laptop.

Sovereign offered those affected free credit monitoring, but the letter did not tell them that the data had been accessed by a keylogger. I suspect, but have no proof, that if people were informed that their data were captured by a keylogger as opposed to being told more generically that there had been “unauthorized access by a third party,” they might be more concerned and more likely to enroll in free credit monitoring. They might also be more diligent about checking their accounts and credit report. But maybe I’m just projecting from what my own reaction would be.

Category: Breach IncidentsFinancial SectorMalwareU.S.

Post navigation

← Law firm’s credentials misused to access Experian database
Blue Cross Blue Shield Applications Found in Trash →

Now more than ever

"Stand with Ukraine:" above raised hands. The illustration is in blue and yellow, the colors of Ukraine's flag.

Search

Browse by Categories

Recent Posts

  • Why Dumping Sensitive Data on Network Shares is a Liability
  • A militarily degraded Iran may turn to asymmetrical warfare – raising risk of proxy and cyber attacks
  • Pro-Russian hackers disrupt Dutch government websites ahead of NATO summit
  • Iran-Linked Threat Actors Leak Visitors and Athletes’ Data from Saudi Games
  • UK: Oxford City Council still investigating cyberattack from earlier this month
  • Steelmaker Nucor Says Hackers Stole Data in Recent Attack
  • People’s Republic of China cyber threat activity: Cyber Threat Bulletin
  • Ukrainian Web3 security auditing company Hacken suffered an attack that allowed a hacker to create 900 million HAI tokens
  • McLaren provides written notice to 743,131 patients after ransomware attack in July 2024 (1)
  • A state forensics lab was leaking its files. Getting it locked down involved a number of people.

No, You Can’t Buy a Post or an Interview

This site does not accept sponsored posts or link-back arrangements. Inquiries about either are ignored.

And despite what some trolls may try to claim: DataBreaches has never accepted even one dime to interview or report on anyone. Nor will DataBreaches ever pay anyone for data or to interview them.

Want to Get Our RSS Feed?

Grab it here:

https://databreaches.net/feed/

RSS Recent Posts on PogoWasRight.org

  • Sky Views Personal Data as a Potential Weapon in IPTV Piracy War
  • Florida Used a Nationwide Surveillance Camera Network 250 Times To Aid in Immigration Arrests
  • Federal Court Strikes Down HIPAA Reproductive Health Care Privacy Rule
  • The Markup caught 4 more states sharing personal health data with Big Tech
  • Privacy in the Big Sky State: Montana’s Consumer Privacy Law Gets Amended
  • UK Passes Data Use and Access Regulation Bill
  • Officials defend Liberal bill that would force hospitals, banks, hotels to hand over data

Have a News Tip?

Email: Tips[at]DataBreaches.net

Signal: +1 516-776-7756

Contact Me

Email: info[at]databreaches.net

Mastodon: Infosec.Exchange/@PogoWasRight

Signal: +1 516-776-7756

DMCA Concern: dmca[at]databreaches.net
© 2009 – 2025 DataBreaches.net and DataBreaches LLC. All rights reserved.