DataBreaches.Net

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

Is Chase’s (800) 355-5265 really their fraud detection number? (Spoiler alert: yes)

Posted on July 29, 2013 by Dissent

Yesterday morning, I received a call from an 800-number that was only identified on my Caller ID as “Toll-Free.” I didn’t pick up, but Googled the number and found pages of reports, many of which suggested that the number, presumably for Chase Fraud Detection, was a scam. Others claimed it was for real. Not very reassuring.

An hour later, I received another call from the same number. Knowing my husband had made two atypical ATM withdrawals in the past 24 hours, this time I picked up. It was an automated system that knew my husband’s name. It asked me to verify my identity by entering my zip code. I hung up and called the number on the back of my Chase debit card and asked for security and fraud department.

It turns out that the call was for real and they were attempting to verify the charges.  The person I spoke with assured me that the (800) 355-5265  number was their authorized number for such calls.

Given how many phishing scams there are and the possibility of spoofing numbers, the way Chase handles this is not particularly wise, in my opinion.  At the very least, the caller ID should show Chase as the caller and not “Toll-Free.” Even better, they should have an identified number that calls the customer and says, “We are trying to reach you to verify certain unusual charges on your card. Please call the number on the back of your ATM card and ask for the fraud and security department. If you can’t locate your card, call Chase’s main number, which you can verify online, and ask for the fraud and security department.”  Of course, it would help if they actually put a dedicated phone number on the back of the ATM card, too.

I related all of the above to the Chase representative. I somehow doubt it will do any good, but really, their system is not a good one in this day and age.

Update: This seems to be a long-standing problem with Chase: https://www.cs.columbia.edu/~smb/blog/2007-11/2007-11-16.html. So why haven’t they addressed these security concerns?

 

Category: Commentaries and Analyses

Post navigation

← HALOCK Investigation Finds that 25% of Sampled Colleges and Universities Are Putting Student and Parent Private Financial Data at Risk
Walgreens must pay woman $1.44 million over HIPAA violation →

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

  • Ex-NSA bad-guy hunter listened to Scattered Spider’s fake help-desk calls: ‘Those guys are good’
  • Former Sussex Police officer facing trial for rape charged with 18 further offences relating to computer misuse
  • Beach mansion, Benz and Bitcoin worth $4.5m seized from League of Legends hacker Shane Stephen Duffy
  • Fresno County fell victim to $1.6M phishing scam in 2020. One suspected has been arrested, another has been indicted.
  • Ransomware Attack on ADP Partner Exposes Broadcom Employee Data
  • Anne Arundel ransomware attack compromised confidential health data, county says
  • Australian national known as “DR32” sentenced in U.S. federal court
  • Alabama Man Sentenced to 14 Months in Connection with Securities and Exchange Commission X Hack that Spiked Bitcoin Prices
  • Japan enacts new Active Cyberdefense Law allowing for offensive cyber operations
  • Breachforums Boss “Pompompurin” to Pay $700k in Healthcare Breach

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

  • Massachusetts Senate Committee Approves Robust Comprehensive Privacy Law
  • Montana Becomes First State to Close the Law Enforcement Data Broker Loophole
  • Privacy enforcement under Andrew Ferguson’s FTC
  • “We would be less confidential than Google” – Proton threatens to quit Switzerland over new surveillance law
  • CFPB Quietly Kills Rule to Shield Americans From Data Brokers
  • South Korea fines Temu for data protection violations
  • The BR Privacy & Security Download: May 2025

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.