DataBreaches.Net

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

Another processor breached!? (nope – see update 1)

Posted on May 22, 2009 by Dissent

WBZ is reporting that hundreds of bank customers are starting their holiday weekend off without their debit cards after a breach at the bank’s card processor, Metavante, forced the Winthrop Federal Credit Union to deactivate some customers’ MasterCards. At least one case of fraud has already been tentatively linked to the breach.

No one was immediately available at Metavante to confirm or clarify the report and there is no statement on their web site. Metavante is listed as PCI-DSS compliant on MasterCard’s listing dated May 19. They are also listed as compliant by Visa as of their May 19th listing, and completed a review this year where TrustWave was the assessor.

This post will be updated as I find out more or as more is reported in the mainstream media.

Update 5-23-09:

WBZ subsequently edited their story without issuing any actual correction to the story or pointing out how their reporting changed. Their most recent version at the same url reports that:

Credit union officials say its card processer (sic), Metavante, noticed suspicious activity on three of its MasterCard debit cards and notified the credit union about them. While it was not a security breach, the Winthrop Federal Credit Union decided to freeze a block of cards as a precaution, something that Metavante did not advise them to do.

Okay, that is significantly different than their original coverage which stated that Metavente had itself had a security breach. Being notified that three cards had suspicious activity on them is radically different than Metavante itself being breached. I wonder if Metavante called the CU after I left a voicemail with Metavante and if they insisted the CU get the story corrected.

Today, the credit union posted this notice on their web site:

Updated Information about your debit card.

WFCU has learned that the debit card situation affecting members’ cards has been resolved. The actual compromised cards have been identified and have resulted in zero dollar losses to the members’ accounts. As a precaution, however, WFCU placed restricted access on a larger block of cards to minimize the potential exposure to our debit card base. We will reissue cards that have had actual compromises immediately and apologize for the inconvenience.

We remind members to always check their accounts, be vigilant in monitoring activity and reconciling your monthly statements. POSTED 5/23/09

So within a few hours we went from the CU claiming that a processor had been breached (if the reporter got the story correctly) to the CU explaining that they had been called about 3 compromised cards and decided to block a much larger group of cards to be safe.

Sheesh.


Related:

  • ModMed revealed they were victims of a cyberattack in July. Then some data showed up for sale.
  • Protected health information of 462,000 members of Blue Cross Blue Shield of Montana involved in Conduent data breach
  • Resource: NY DFS Issues New Cybersecurity Guidance to Address Risks Associated with the Use of Third-Party Service Providers
  • TX: Kaufman County Faces Cybersecurity Attack: Courthouse Computer Operations Disrupted
  • KT Chief to Resign After Cybersecurity Breach Resolution
  • Cyber-Attack On Bectu’s Parent Union Sparks UK National Security Concerns
Category: Breach IncidentsFinancial SectorU.S.

Post navigation

← Bits ‘n Pieces
Maine Requires Breach Notice within Seven Days of Go-Ahead from Law Enforcement →

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

  • District of Massachusetts Allows Higher-Ed Student Data Breach Claims to Survive
  • End of the game for cybercrime infrastructure: 1025 servers taken down
  • Doctor Alliance Data Breach: 353GB of Patient Files Allegedly Compromised, Ransom Demanded
  • St. Thomas Brushed Off Red Flags Before Dark-Web Data Dump Rocks Houston
  • A Wiltshire police breach posed possible safety concerns for violent crime victims as well as prison officers
  • Amendment 13 is gamechanger on data security enforcement in Israel
  • Almost two years later, Alpha Omega Winery notifies those affected by a data breach.
  • Court of Appeal reaffirms MFSA liability in data leak case, orders regulator to shoulder costs
  • A jailed hacking kingpin reveals all about the gang that left a trail of destruction
  • Army gynecologist took secret videos of patients during intimate exams, lawsuit says

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

  • As shoplifting surges, British retailers roll out ‘invasive’ facial recognition tools
  • Data broker Kochava agrees to change business practices to settle lawsuit
  • Amendment 13 is gamechanger on data security enforcement in Israel
  • Changes in the Rules for Disclosure for Substance Use Disorder Treatment Records: 42 CFR Part 2: What Changed, Why It Matters, and How It Aligns with HIPAAs
  • Always watching: How ICE’s plan to monitor social media 24/7 threatens privacy and civic participation

Have a News Tip?

Email: Tips[at]DataBreaches.net

Signal: +1 516-776-7756

Contact Me

Email: info[at]databreaches.net
Security Issue: security[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.