Searches such as “chase data breach lawsuit” followed a statement that Chase posted on its official X account on November 19, 2026. In it, Chase said that third parties who provide services to the firm were the target of a cyber attack. According to the same statement, the company’s investigation so far indicates that the attackers accessed certain marketing data held by those vendors, and that this data may include some customer names and email addresses. The statement adds that there is no disruption to its services, that the company will contact affected customers directly where appropriate and offer support, including complimentary credit monitoring, and that the incident has no connection to the service disruption some customers experienced earlier that week. On November 21, 2026, a search of the CourtListener RECAP archive of federal dockets returned no complaint about this incident. That archive does not hold every federal filing, so the search does not show that none exists.
The legal answer depends less on the name of the company than on the data involved. Federal courts first ask whether a breach created a substantial risk of identity theft or fraud, and the type of data exposed is one of the main factors. Names and email addresses alone have repeatedly been found insufficient; Social Security numbers, account numbers or passwords change the analysis, and so does evidence that the stolen data is already being misused. The discussion that follows is general in scope: it describes checks useful in comparable situations and makes no findings about JPMorgan Chase’s situation.
I. Can a customer sue when a vendor breach exposed names and email addresses?
A. The Second Circuit test: a targeted attack, misuse, and how sensitive the data is
Before a federal court looks at negligence, contract or consumer protection claims after a data breach, it must decide whether the person suing has standing under Article III of the Constitution. That requires an injury in fact that is concrete, particularized, and actual or imminent. In data breach litigation the question is rarely academic: many cases end at this first step, long before anyone examines how a company or its vendors protected the data. For a customer, this means the first question is not whether security was adequate, but whether the exposure itself put that customer at a real and substantial risk of harm.
The leading test in the federal appeals court whose territory includes New York comes from McMorris v. Carlos Lopez & Assocs., LLC, 995 F.3d 295 (2d Cir. 2021), decided by the U.S. Court of Appeals for the Second Circuit on April 26, 2021. The case did not involve hackers at all: an employee of a company that provides mental and behavioral health services to veterans accidentally emailed a spreadsheet containing the Social Security numbers, home addresses and dates of birth of about 130 current and former employees to the company’s roughly 65 staff members. The court held that people whose data is disclosed without authorization may establish standing based on a substantial risk of identity theft or fraud, even before anyone has misused their identity. It then set out three non-exhaustive factors: whether the data was exposed through a targeted attempt to obtain it, whether any portion of the dataset has already been misused, and “whether the type of data that has been exposed is sensitive such that there is a high risk of identity theft or fraud.” Because the spreadsheet stayed inside the company and nothing had been misused, the court affirmed the dismissal despite the sensitivity of the numbers involved. It also held that money and time spent on protective measures do not create standing on their own when the underlying risk is not substantial. Applied to a breach limited to names and email addresses, the third factor points against standing unless more sensitive data or actual misuse is shown.
Each factor maps onto a question a customer can actually check. The first factor usually favors customers in a hacking case. McMorris contrasted an internal, misdirected email with cases in which a malicious third party intentionally targeted a company’s system and took the data stored there, and it noted that courts have been more willing to find standing in the second situation. A cyberattack on a vendor is closer to that description than an accidental email. The second factor depends on facts that often emerge only over weeks or months: whether any part of the stolen dataset turns up in fraud, on a criminal marketplace or in a wave of account takeovers. The third factor is the one that names and email addresses struggle with. McMorris explained that the dissemination of high-risk information such as Social Security numbers and dates of birth, especially together with names, makes future identity theft more likely, while less sensitive or publicly available data does not carry the same risk. A name and an email address are, for most people, already known to friends, employers, retailers and marketing lists.
Two years later, the same court refined the test after the Supreme Court tightened the standing rules for damages claims. In Bohnak v. Marsh & McLennan Companies, Inc., 79 F.4th 276 (2d Cir. 2023), decided by the U.S. Court of Appeals for the Second Circuit on August 24, 2023, a former employee alleged that an unauthorized actor exploited a vulnerability in a third party’s software and accessed her name and Social Security number, which she had entrusted to her former employer and its parent company. The court held that the Supreme Court’s decision in TransUnion governs whether a risk of future harm is concrete, while “the McMorris framework continues to apply in data breach cases like this” on the question of imminence. It found the injury concrete because exposure of private information to unauthorized third parties bears a relationship to the common-law tort of public disclosure of private facts, and it treated out-of-pocket mitigation expenses and lost time as separate concrete harms where the underlying risk was substantial. It reversed the dismissal and sent the case back for further proceedings. The route through third-party software did not prevent the court from finding standing against the companies to which the plaintiff had entrusted her data. For a customer, the decision shows what a strong data breach claim looks like in this circuit: a targeted hack combined with a name and a Social Security number.
The Second Circuit has continued to rely on that reasoning. In Salazar v. National Basketball Association, No. 23-1147 (2d Cir. Oct. 15, 2024), the U.S. Court of Appeals for the Second Circuit, in a decision dated October 15, 2024, cited Bohnak, 79 F.4th 276, for the way courts read the pleadings when standing is challenged, and it relied on the same public-disclosure analogy to hold that a newsletter subscriber who alleged that his video-viewing information had been shared with a third party had pled a concrete injury under the federal Video Privacy Protection Act. The observed citation confirms that Bohnak’s disclosure-of-private-facts analogy remains part of the circuit’s standing analysis. That analogy, however, is built on the disclosure of information that is private. It fits viewing histories, Social Security numbers and medical files far better than it fits a name and an email address that appear in countless ordinary contexts.
District courts in the circuit apply the same factors to recent breaches. In Murray v. Connecticut College, No. 3:24-cv-01099-MPS (D. Conn. Sept. 23, 2025), the U.S. District Court for the District of Connecticut, ruling on September 23, 2025, cited McMorris, 995 F.3d 295, and walked through its three factors for a plaintiff, whom the court inferred had been a student, whose full name and Social Security number were listed in the college’s breach notice letter. The court found the first factor met because the complaint alleged that cybercriminals obtained the data intending to misuse it, found the second factor not met because no misuse was alleged, and found the third factor met because of the Social Security number and other high-risk data; two of three factors were enough for standing. It then dismissed the negligence claim because the plaintiff offered no analysis under Connecticut’s duty framework and the court found no Connecticut case recognizing the duty he proposed, while allowing implied contract and unjust enrichment claims to proceed. Murray shows that the sensitivity of the exposed data can carry a case past the standing stage even without misuse, and that surviving standing does not guarantee that every state-law claim survives.
B. When only names and contact details were taken, courts have dismissed
The closest comparison for a breach limited to names and contact details is In re Samsung Data Security Breach Litigation, No. 1:23-md-03055 (D.N.J. Dec. 11, 2024), decided by the U.S. District Court for the District of New Jersey in an opinion filed December 11, 2024. Sixteen cases from eleven courts had been consolidated there after a July 2022 attack in which an unauthorized third party acquired customer information from the company. By the fourth amended complaint, the information the parties agreed had been accessed was names, addresses, other contact and demographic information, and device information. The court accepted that the attack was intentional enough to weigh in favor of imminence, gave little weight to scattered allegations of misuse that were not tied to the data actually taken, and held that the nature of the information was decisive. In its words, the information was “simply not sensitive enough to give rise to an imminent risk of identity theft or fraud for any Plaintiff.” The court rejected increased phishing and spam as an injury, held that mitigation costs, lost value of personal data and emotional distress could not stand on their own without an imminent risk, and dismissed the consolidated complaint with prejudice. For a customer whose exposure is limited to a name and an email address, this ruling is the closest comparison among the decisions discussed here.
Two features of that opinion matter for anyone reading about a new breach. First, the court applied the Third Circuit’s factors from Clemens, which ask whether the breach was intentional, whether the data was misused and whether the information could subject a person to identity theft. Those questions track the McMorris factors closely, but a District of New Jersey opinion binds no court in New York; it is persuasive authority, not controlling law there. Second, the court explained its conclusion in practical terms. It found no logical explanation for how disclosure of information that was mostly mundane or readily available online would increase the risk of identity theft without significant speculation, and it rejected a theory that hackers could use such data for social engineering because that theory depended on a long chain of possibilities.
The phishing point deserves attention because names and email addresses are exactly what phishing campaigns use. A person whose name and email are in criminal hands can expect more convincing fake messages, including messages that appear to come from a bank or a credit monitoring service. The Samsung court did not deny that risk; it held that phishing attempts alone, without any theft that actually materialized, were not enough for an injury in fact, and it relied on decisions that treated unsolicited calls and emails the same way. That is a legal conclusion about standing, not a statement that phishing is harmless. It means the practical response to this kind of exposure is vigilance, not litigation, unless a message leads to an actual loss.
Traceability is the second hurdle, and the Samsung opinion gives a concrete example. One plaintiff alleged that a credit card had been opened in his name after the breach, but the information disclosed about him in that breach was his name, email address and a device identifier. The court reasoned that opening a credit account requires information that was not taken, so the harm could not plausibly be traced to the breach without speculation. Other plaintiffs had been notified that their information was on the dark web, but the notifications concerned Social Security numbers that were not part of the breach, or predated it. A customer who later suffers fraud should therefore ask a simple question before drawing conclusions: could someone commit that fraud with only the data that was actually exposed?
The opinion also shows what happens to cases filed in state court. Article III limits the jurisdiction of federal courts. In the Samsung litigation, the court remanded the matters that had started in state court back to those courts rather than dismissing them with the federal cases, so its federal standing ruling did not decide how those state courts would proceed. State courts apply their own rules on who may sue, and those rules were not before the federal court. This article does not assume that any particular state court would treat a names-and-email breach differently; it simply notes that the federal standing analysis is not the only forum question.
II. Which laws could support a claim, and what should a customer do now?
A. Federal banking rules, California’s private right of action and New York’s notice law
Federal law imposes privacy and security obligations on financial institutions, but mostly through regulators. Under 15 U.S.C. § 6801, part of the federal Gramm-Leach-Bliley Act, Congress declared that each financial institution has an affirmative and continuing obligation to respect the privacy of its customers and to protect the security and confidentiality of their nonpublic personal information, and it directed the agencies to set safeguards standards against unauthorized access that could result in substantial harm or inconvenience to a customer. The enforcement section, 15 U.S.C. § 6805, assigns enforcement to the Consumer Financial Protection Bureau, the federal functional regulators, state insurance authorities and the Federal Trade Commission, and for national banks to the appropriate federal banking agency under 12 U.S.C. § 1818. The section lists agencies; it does not list individual customers among the enforcers. A customer’s own claim, if any, therefore usually rests on state law, such as negligence, contract or a state consumer statute, which brings the standing and duty questions discussed above back into play.
The federal banking agencies’ guidance explains when a bank is expected to notify customers, and its definitions are useful for anyone reading a breach statement. Supplement A to Appendix B to 12 C.F.R. part 30 (OCC), in the edition revised as of January 1, 2026, interprets the federal safeguards requirement and defines sensitive customer information as a customer’s name, address or telephone number in conjunction with the customer’s Social Security number, driver’s license number, account number, credit or debit card number, or a personal identification number or password that would permit access to the account, as well as any combination of components that would allow someone to log onto or access the account. When an institution becomes aware of unauthorized access to sensitive customer information, the guidance says it should investigate, and if it determines that “misuse of its information about a customer has occurred or is reasonably possible,” it should notify the affected customer as soon as possible. The same guidance says that an institution’s contract with its service provider should require the provider to take appropriate actions to address incidents of unauthorized access and to notify the institution as soon as possible, and it describes what a notice should contain: the incident in general terms, the type of information involved, what the institution has done, and a reminder to remain vigilant over the next twelve to twenty-four months. A name and an email address, standing alone, fall outside that definition. That is why the list of data elements in any notice a customer receives matters more than any headline.
California gives consumers a statutory private right of action for certain breaches, and its text is precise. Under California Civil Code § 1798.150, a consumer may sue when nonencrypted and nonredacted personal information, as defined in a specific part of section 1798.81.5, or an “email address in combination with a password or security question and answer that would permit access to the account” is subject to unauthorized access and exfiltration, theft or disclosure as a result of the business’s violation of the duty to maintain reasonable security. The remedy includes statutory damages of not less than $100 and not more than $750 per consumer per incident, or actual damages if greater, plus injunctive or declaratory relief. Before suing for statutory damages, individually or for a class, the consumer must give the business 30 days’ written notice identifying the provisions allegedly violated, and if the business actually cures the violation within that period and provides an express written statement that it has been cured, no action for statutory damages may be brought; no notice is required for an action seeking only actual pecuniary damages.
The cross-referenced definition in California Civil Code § 1798.81.5 lists the combinations that count: a first name or initial and last name together with a Social Security number, a driver’s license or other government identification number, an account or card number with any required security or access code, medical or health insurance information, unique biometric data or genetic data. A separate paragraph covers a username or email address with a password or security question and answer. A name with an email address, and nothing more, is in neither list. The same section requires businesses that disclose personal information to a nonaffiliated third party under a contract to require that third party, by contract, to maintain reasonable security, which is relevant whenever a vendor holds customer data. The section also excludes certain entities from its own provisions, including financial institutions subject to the California Financial Information Privacy Act, so whether its security duty applies to a particular business is a separate question that turns on that business’s status.
New York’s breach statute works mainly through notice and enforcement by the attorney general. New York General Business Law § 899-aa defines private information as personal information combined with a Social Security number, a driver’s license or non-driver identification number, an account or card number with any code or password that would permit access to a financial account, an account or card number usable without such a code, biometric information, medical information or health insurance information, or a username or email address in combination with a password or security question and answer that would permit access to an online account. A business that owns or licenses computerized private information must notify affected New York residents in the most expedient time possible and without unreasonable delay, and no later than thirty days after discovering the breach, subject to the legitimate needs of law enforcement. If notice is given under the regulations implementing the Gramm-Leach-Bliley Act, the statute does not require an additional notice to the affected persons, although notices to state agencies and consumer reporting agencies still apply. Subdivision 6 authorizes the attorney general to sue to enjoin violations, and in such an action the court may award damages for actual costs or losses incurred by a person who did not receive required notice and may impose civil penalties for knowing or reckless violations. Under these definitions, a breach of names and email addresses without passwords does not involve private information as New York defines it.
B. Practical steps now, and the records that matter if the facts change
The most immediate risk after an exposure of names and email addresses is a more convincing phishing message. Messages that use a customer’s real name and refer to a real incident are designed to be clicked. The safer practice is simple: do not use links or attachments in messages about the incident, and reach the bank only through its official app, the website typed directly into the browser, or the number printed on the card. Requests for a password or a one-time code through an email link are a common feature of fraud, and it is reasonable to treat such a request as suspicious and report it through the bank’s official channels.
Federal law gives consumers two tools that work whether or not a breach involved sensitive data: a security freeze, which must be placed free of charge, and a fraud alert. Under 15 U.S.C. § 1681c-1, a nationwide consumer reporting agency must place a security freeze free of charge upon a direct request with proper identification, within one business day when the request is made by toll-free telephone or secure electronic means and within three business days when it is made by mail. A freeze prohibits the agency from disclosing the consumer report to a person requesting it, and a creditor that cannot access the report may treat a credit application as incomplete. When the consumer asks to lift the freeze by telephone or secure electronic means, the agency must remove it within one hour. The same section allows a consumer who asserts in good faith a suspicion of fraud or identity theft to place an initial fraud alert that lasts at least one year, and the agency that receives it must refer it to the other nationwide agencies. For a person whose name and email address were exposed, a freeze may be more protection than the data strictly requires, but it is the strongest step against new accounts opened in that person’s name.
Keeping records costs little and preserves options. A customer who receives a notice should keep it and note exactly which data elements it lists, since that list drives the analysis under McMorris, Bohnak and the state definitions. Time spent and money paid for protective steps should be logged with dates. The Second Circuit treats such costs as an injury only when the underlying risk is substantial, so the log will not create a claim on its own, but it becomes relevant if later information shows that passwords, account numbers or Social Security numbers were involved, or if part of the dataset is misused. In Murray, the college argued that the plaintiff’s mitigation costs were self-inflicted because it had offered complimentary credit monitoring for 24 months; the court noted that the plaintiff alleged costs beyond that monitoring, including lost wages, and that those costs responded to a risk the court had already found substantial. Accepting an offered monitoring service and keeping a record of other costs are not inconsistent.
Search results for this kind of query also mix different events. Pages titled with a bank’s name and the words breach, lawsuit or settlement can concern earlier incidents, different notice letters or unrelated class actions. A law firm page announcing an “investigation” is not a lawsuit, and a settlement page for an older incident does not cover a newer one. If a complaint is filed about a particular breach, it will name a court and a docket number, and its contents will be allegations made by the plaintiffs, not findings by a judge. The decisions discussed above show how long the road from complaint to any recovery can be: the Samsung litigation reached a fourth amended consolidated complaint, with a special master appointed along the way, before the court dismissed it on standing.
Finally, customers outside New York should not assume that the Second Circuit’s framework controls their own case. McMorris and Bohnak bind federal courts in New York, Connecticut and Vermont, while other circuits apply their own versions of the same questions, as the Samsung opinion’s reliance on the Third Circuit’s Clemens factors shows. The common thread across the decisions read for this article is the same: courts look at what was taken, whether it was targeted and whether anyone has used it. A reader who keeps those three questions in mind can evaluate any new breach statement, including later updates that change the list of data involved.
Conclusion
When a vendor breach is described as involving only names and email addresses, the realistic legal picture is narrow. Federal courts in the Second Circuit ask whether the attack was targeted, whether any of the data has been misused and whether the data is sensitive, and a federal court in New Jersey dismissed a large consolidated case because names, contact details and similar information were not sensitive enough to create an imminent risk of identity theft. Federal banking law operates mainly through regulators, and both California’s private right of action and New York’s notice statute are triggered by more sensitive combinations, such as a name with a Social Security number or account number, or an email address with a password. The analysis changes if later information shows that such data was involved, or if fraud traceable to the stolen data appears. Until then, the useful steps are practical: treat incident-related messages with suspicion, consider a free security freeze or a fraud alert, keep any notice and a record of costs, and distinguish a filed complaint from an investigation page or a settlement for a different incident.