DataBreaches.Net

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

OK, so you found a skimmer on your ATM. Now what?

Posted on April 13, 2009 by Dissent

James Doran of the New York Post had an article about two Chase Bank branches in NYC and a WaMu branch in West Hollywood that recently detected skimmers (see also The Consumerist coverage). Now that in and of itself may not be particularly newsworthy by now, but do read the story of how Chase responded when one customer discovered the skimmer and tried to protect other consumers. It seems that had it not been for the customer’s savvy, even more customers might have had their information stolen:

Once back on his way to the barber, Siebel remembered from a Web site story he read that the skimmer devices come in two parts — a reader, which he found, and a camera, which is often concealed behind a round mirror on the ATM.

“So I ran back to the bank and not only were there two mirrors on the ATM, but people were still using it, the bank had not even shut it down,” an astonished Siebel said.

He said he tore the fake mirror off the ATM and went inside to ask to speak to Pascuas a second time. She again failed to call the cops and said Chase security would deal with it.

“I was stunned,” Siebel said.

The bank defended its handling of the matter, and some pointed out that leaving the skimmer in situ so that the criminals could be caught might be a better approach. Even if banks do not hold customers responsible for fraudulent charges, though, the grief of having to replace cards and deal with messes is not something most people would relish. So what, if anything, should individuals do if they discover a skimmer, other than notifying the bank?

Ben Popken, co-executive editor at online consumer advocate consumerist.com, the Web site that first revealed the WaMu discovery, cautioned anyone finding a skimmer to call 911 and let the cops deal with it.

Call 911? No way. There’s enough abuse of the 911 system, and calls to 911 should be reserved for emergencies such as fires, accidents, and incidents involving risk to life.

So what would you do if you found a skimmer attached to an ATM?


Related:

  • ModMed revealed they were victims of a cyberattack in July. Then some data showed up for sale.
  • KT Chief to Resign After Cybersecurity Breach Resolution
  • Cyber-Attack On Bectu’s Parent Union Sparks UK National Security Concerns
  • A business's cyber insurance policy included ransom coverage, but when they needed it, the insurer refused to pay. Why?
  • Before Their Telegram Channel Was Banned Again, ScatteredLAPSUS$Hunters Dropped Files Doxing Government Employees (2)
  • Attorney General James Secures $14.2 Million from Car Insurance Companies Over Data Breaches
Category: Breach Incidents

Post navigation

← Penn State reports second breach in 2009
MS: CBIZ Medical Management Professionals computer with patient records stolen →

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

  • 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
  • The Case for Making EdTech Companies Liable Under FERPA
  • NHS providers reviewing stolen Synnovis data published by cyber criminals

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

  • 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
  • Who’s watching the watchers? This Mozilla fellow, and her Surveillance Watch map

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.