Urgent.News

What's breaking now, across thousands of outlets.

Tech

Chase confirms cyberattack that may have exposed customer data. Here’s what we know

Chase Bank isn’t doing much to reassure customers. The bank said Thursday that third-party vendors were recently targeted in a cyberattack that resulted in a breach of some customer information. But there is “no connection” between this cyber attack and the outage earlier this week that saw customers unable to log in to their accounts, the bank posted on X. “Based on our investigation so far, we…

Chase confirms cyberattack that may have exposed customer data. Here’s what we know

Chase Bank disclosed on Thursday that a recent cyberattack may have exposed customer data, though they emphasized there is "no connection" between this incident and a previous outage experienced earlier in the week. The bank reported that the attackers accessed certain marketing data held by their vendors, potentially including customer names and email addresses, but did not specify when the breach took place.

The outage earlier in the week, which left many customers unable to log in to their accounts for several hours, has been attributed to a "software bug" by Chase, with no evidence of a cyberattack or systemic issue. This announcement has only increased public concern, with some people doubting Chase's explanation. The ransomware group n0n recently released stolen data of about 16,000 JPMorgan Chase customers and employees after a 48-hour ransom deadline passed, claiming to have obtained information from Chase's premium Reserve credit card program.

Conspiracy theories have been circulating online, leading some Americans to panic-buy items. Secretary of State Marco Rubio, in a speech during a trip to Asia, stated that there is "no evidence" of a link between the outages or that they are the result of cyberattacks, reassuring the public that the incidents are not related to each other or to any malign actors.

Written by urgent.news from Fast Company's reporting — not their text. Machine-written — may contain errors; check the original before relying on it.

Read the original at fastcompany.com →

More in Tech

Your "49 KB" file is actually 50.5 KB. Blame the kilobyte.

A user picks a file. Their computer says 49 KB. Your form says "max 50 KB." The upload gets rejected anyway, and now there's a support ticket that says your site is broken. It isn't broken, exactly.

  • File size discrepancy due to different kilobyte definitions
  • Windows Explorer uses 1,024 bytes, macOS uses 1,000 bytes
  • Inconsistent communication leads to upload issues

Service Worker Keeps Stopping? That's the Contract, Not a Bug

The message in the console is not an error. Service worker registration successful followed by silence is the designed behavior of Manifest V3, and the sooner that stops feeling like a crash, the…

  • Service worker stops idling, not a failure
  • Chrome terminates idle background workers after 30 seconds
  • Logs cleared with each worker restart, store in storage

Day 87: A Redirected Module and a Renamed Publisher

Day 87 of DevOps, Day 37 of Azure. Both tasks today turned on a name that is not the name the system uses. An Ansible task that says yum runs the dnf module, because the first is now a redirect to the…

  • Ansible task installed and started vsftpd service on three CentOS Stream 9 servers
  • Published Percona MySQL image on Azure by Jetware, displayed as jetware-srl
  • Verified publisher name discrepancy before deploying marketplace images

More from Thursday 19 November →