KOHEN AVOCATS · PARIS, FRANCE
cyber attacks: can you sue after a data breach if no money was stolen yet?

Hassan Kohen is a Paris-based lawyer admitted to the Paris Bar (Avocat au Barreau de Paris). Initial strategic analysis: €80 incl. VAT, personal reply within 24 hours.

100% confidential · Legal professional privilege · No obligation

Article generated by artificial intelligence, through a process designed and supervised by the firm

Sources: U.S. court opinions and official U.S. government publications, read for this article

Maître Hassan KOHEN, avocat au Barreau de Paris
Hassan KOHEN
Attorney at the Paris Bar

cyber attacks: can you sue after a data breach if no money was stolen yet?

Speak to a lawyer 06 89 11 34 45

A data breach notice often arrives before any money disappears. It may say that an unauthorized person viewed or copied files containing a name, a Social Security number, a birth date, a driver license number, health information, or account information, and it may offer monitoring for a stated period. That letter raises a practical legal question that a definition of a cyber attack does not answer: can a person sue the organization that held the information before a fraudulent charge, a false tax return, or a new account appears? In federal court, the first answer is procedural. A plaintiff must plead a concrete injury that is fairly traceable to the defendant and likely to be redressed by a court order, and recent district courts have separated three different ideas that readers often merge: exposure of information, loss of control over private information, and actual or attempted misuse. Passing that doorway does not establish negligence, a contract claim, or a statutory claim, each of which is tested under the law that governs it. The discussion that follows is general in scope: it describes checks useful in comparable situations and makes no findings about any company named in the court decisions discussed below. The useful first step is to read your own notice for what was taken, when access occurred, when it was discovered, and what has happened since.

I. Can you sue after a cyber attack if no money was stolen yet?

A. Federal standing separates exposure, loss of control, and attempted misuse

Start by identifying the right defendant for the claim you have in mind. The intruder who entered a system without authorization and the business, employer, insurer, school, or provider that stored the information occupy different legal positions. A claim against the intruder concerns the unauthorized access itself. A claim against the organization that held the data usually concerns whether that organization used reasonable safeguards, what it promised, when it notified affected people, or whether a state consumer statute was violated. Those questions do not prove each other. Proof that a criminal entered a network does not, without more, prove that the holder of the data was negligent, and proof that security could have been stronger does not identify the intruder. Keeping the two tracks separate helps you send each record request and each legal question to the party that can actually answer it.

The federal doorway is Article III standing. A reader who received a notice but has seen no misuse should expect the holder of the data to argue that a risk of future identity theft is too abstract, that monitoring costs were voluntary, and that anxiety alone is not the kind of injury a federal court can redress. Recent orders show why the details in the notice and the events after it matter, and why courts in different districts can describe the same doorway in different words. Each order below was decided at the pleading stage unless the paragraph says otherwise, which means the court tested whether the complaint alleged enough to proceed and did not make a final finding that any security practice was reasonable or unreasonable.

In Barnes v. Key Tronic Corporation, No. 2:25-CV-0081-TOR (E.D. Wash. August 19, 2025), the UNITED STATES DISTRICT COURT EASTERN DISTRICT OF WASHINGTON considered an employee who alleged that his name and Social Security number were stolen from his employer and that he had spent time monitoring his credit and had experienced fear, anxiety, and stress. The opinion states that the plaintiff had not alleged actual or attempted identity theft in the year since the breach, and the court treated that absence as a problem for a theory based only on a future risk. The court nevertheless concluded that the plaintiff had satisfied Article III standing on a narrower theory: the alleged loss of control of his personal information bore a sufficient relationship to a harm protected in tort, by analogy to disclosure of private information. The court then dismissed the negligence claim without prejudice, dismissed unjust enrichment and fiduciary duty with prejudice, retained the breach of implied contract claim, and allowed an amended complaint within twenty-one days of the order. For a reader whose notice says name and Social Security number were taken but who has seen no attempted identity theft yet, the first check is whether the complaint can plead loss of control of private information with specific facts, not fear alone.

Barnes also shows why a Social Security number is not interchangeable with every other data element. A name paired with a Social Security number, a birth date, a passport number, health information, or financial account information can support a different factual argument from an email address standing alone, because the combinations differ in how they can be used and in how easily the reader can replace them. Do not copy another person’s list of compromised elements into your own complaint or claim letter. Copy the list printed in your notice, then list separately anything you later observed, such as a password reset you did not request, a credit inquiry you did not authorize, a tax filing rejection, a medical bill for care you did not receive, or a bank alert. A court reading a pleading needs to know which facts come from the notice and which facts come from your own dated experience.

A different pleading-stage analysis let a broader group of claims proceed to discovery in Massachusetts. In In re Sensata Technologies Data Breach Litigation, No. 1:25-cv-11726-JEK (D. Mass. September 30, 2026), the UNITED STATES DISTRICT COURT DISTRICT OF MASSACHUSETTS addressed former employees who alleged that ransomware activity between March 28, 2025 and April 6, 2025 allowed an unauthorized actor to view and obtain files that could include names, addresses, Social Security numbers, tax and government identification numbers, financial and payment card information, medical information, health insurance information, and birth dates. The court held that the plaintiffs had standing to pursue monetary and equitable relief because they had sufficiently alleged a material risk of future misuse of their data and a separate concrete injury caused by exposure to that risk. It allowed claims for negligence, breach of an implied contract, unjust enrichment, and violations of California privacy and unfair competition laws to proceed to discovery, while dismissing a Massachusetts Chapter 93A claim by former employees against their former employer and a standalone declaratory judgment count. For a reader deciding whether to act before any account is drained, the useful check is whether the notice and later events show a material risk of misuse plus a separate cost or other concrete effect tied to that risk.

Read the contrast carefully. Barnes did not hold that every notice creates a damages case, and the Massachusetts order did not hold that every person named in a ransomware notice will recover money. One court found standing through loss of control while dismissing several claims; the other found standing through material risk plus a separate concrete injury and allowed several claims to reach discovery. Both orders were written before a full factual record on security measures, causation, and damages. A reader in Washington, Massachusetts, California, Texas, or another state should therefore avoid treating a single district order from a different state as a prediction. It is a checklist for the facts a court in the reader’s own forum is likely to ask for: what data, what access, what later misuse or attempted misuse, what concrete cost or other effect, and what connection ties each effect to this breach rather than to an earlier unrelated disclosure.

Attempted misuse changes the standing conversation because it moves the dispute from a purely hypothetical sequence toward events that can be dated. A dark-web alert by itself should be saved with the service that issued it, the date it arrived, and the data element it identifies. An attempted account access should be saved with the bank or provider alert, the time, and whether the attempt succeeded. A rise in spam calls is weaker standing alone than a new credit inquiry, a changed mailing address, a benefits claim, or a medical bill, because spam has many causes. None of those later events should be described as caused by a particular breach unless the record supports that link. Write what happened, when you learned it, and what document proves it; causation can then be argued from records instead of from sequence alone.

B. Standing is only the doorway: the underlying claim must still be pleaded

After standing, the court asks a second set of questions. For negligence, the governing state law supplies the duty, breach, causation, and damages elements, and the economic loss and duty rules of that state can matter. For an implied contract claim, the reader needs to identify the exchange from which a promise to safeguard information is said to arise, such as employment records required as a condition of a job or information supplied to obtain a service. For unjust enrichment, the reader needs a benefit retained under circumstances that the governing law treats as unjust, not only a disappointing security outcome. A complaint that repeats the words reasonable safeguards without factual content about the relationship, the information entrusted, the access, and the injury invites the same pleading attack that succeeded in part in the orders above.

That separation is clear in a Texas insurance and health information case. In In re New Era Enterprises Inc. Data Incident Litigation, No. H-25-732 (S.D. Tex. February 4, 2026), the IN THE UNITED STATES DISTRICT COURT FOR THE SOUTHERN DISTRICT OF TEXAS HOUSTON DIVISION considered customers and a former employee who alleged that files copied in December 2024 included names, Social Security numbers, addresses, birth dates, health insurance and Medicare identifiers, and information about medical treatment and diagnoses, and who also alleged dark-web posting, attempted access to financial accounts, and increased spam. The court held that the plaintiffs had standing, but it dismissed without prejudice the request for damages based on emotional harm, the negligence per se claim subject to later choice-of-law analysis, and the implied contract claim, and it granted leave to amend within fourteen days of the memorandum and opinion. The negligence and unjust enrichment analysis proceeded on different terms under the law discussed in the opinion. For a reader whose information later appears in attempted account access or dark-web warnings, those dated attempts should be preserved because they help separate a substantial risk from a purely hypothetical one.

California readers have a specific statutory route that must be read on its own terms instead of being treated as a national data breach claim. Under California Civil Code § 1798.150, a consumer whose nonencrypted and nonredacted personal information, as defined by the cross-reference in that section, or whose email address combined with a password or security question and answer permitting account access, is subject to unauthorized access and exfiltration, theft, or disclosure as a result of a business violation of its duty to implement and maintain reasonable security procedures and practices appropriate to the nature of the information may bring a civil action for the relief stated in the section. The section states a range for statutory damages per consumer per incident or actual damages, whichever is greater, and it also lists injunctive or declaratory relief and any other relief the court deems proper. Those words do not answer whether a particular business is covered, whether the information falls within the definition, whether the data were encrypted or redacted, or whether the access resulted from the alleged violation. A California reader should work through each element from the notice and the business relationship instead of assuming that any California residence plus any breach notice completes the claim.

The same California section contains a pre-suit step for statutory damages that should be calendared from the text. Section 1798.150(b) provides that before initiating an action for statutory damages on an individual or class-wide basis, a consumer provides the business thirty days written notice identifying the specific provisions alleged to have been or to be violated, and it addresses the effect of an actual cure with an express written statement within that period where a cure is possible. Do not treat a general complaint email as that notice unless it identifies the specific provisions and can be proved as sent and received. Keep the exact notice, the address or service agent used, the delivery record, any cure statement, and the date the thirty days run. The Massachusetts order discussed this California notice issue on the pleading before it; it did not create a national thirty-day rule for negligence claims in other states.

Federal regulator law is relevant in a different way. Section 5 of the Federal Trade Commission Act, codified at 15 U.S.C. § 45, declares unlawful unfair methods of competition in or affecting commerce and unfair or deceptive acts or practices in or affecting commerce, and it empowers the Federal Trade Commission, subject to the exceptions stated in the text, to prevent covered persons, partnerships, or corporations from using them. That federal text is often invoked in argument about industry expectations or as a predicate theory under a separate state claim, but § 45 itself should not be described in a claim letter as if it automatically supplied every reader with a private damages action. The orders above treated state negligence, contract, unjust enrichment, and named California claims as separate counts with separate elements. A reader who wants a regulator to examine a practice and a reader who wants a court to award damages are using different instruments, even when both begin with the same breach notice.

Class action language in a notice or in news coverage needs the same discipline. The three district orders discussed putative or consolidated class complaints at the motion-to-dismiss stage; none of the paragraphs above should be read as a certification decision, a settlement approval, or a finding that every affected person suffered the same injury. If a reader later receives a class notice, the operative dates and choices will come from that court-approved notice and the docket in that case, not from a general article. Until then, an individual file should be built as if the reader may need to prove individual notice, individual data elements, individual later events, and individual costs. Shared access to a network does not erase those individual proof questions.

II. What should you preserve, request, and calendar after a breach notice?

A. Build the file from the notice, the access dates, and dated later events

Preserve the notice exactly as received, including the envelope or email header, every page, and any enrollment code page, even if you do not enroll in monitoring on the first day. The legally useful fields are usually the dates of access, the date of discovery, the date of the notice, the categories of information, whether files were only viewed or were copied or acquired, whether encryption is mentioned, what the sender says it has done, and where questions are to be sent. If a later corrected notice arrives, keep both versions and note what changed. Do not write on the only copy. Make a separate chronology with four columns in your own notes: the access period stated by the sender, the discovery date stated by the sender, the date you received notice, and each later event you personally observed. That chronology will be more useful than a folder of screenshots without dates.

California notification timing illustrates why those dates must be checked under the state law that applies rather than under a national slogan. California Civil Code § 1798.82 requires a covered individual or business that conducts business in California and owns or licenses computerized data including personal information to disclose a breach of the security of the system to a California resident whose unencrypted personal information was, or is reasonably believed to have been, acquired by an unauthorized person, with an additional encrypted-information clause stated in the text. The current text states that the disclosure shall be made within thirty calendar days of discovery or notification of the data breach, subject to delay to accommodate legitimate law-enforcement needs or as necessary to determine the scope of the breach and restore the reasonable integrity of the data system. It also prescribes a plain-language notice format with stated headings. A California reader who wants to test timing should therefore compare the discovery or notification date in the sender’s own account with the disclosure date and ask which statutory delay ground, if any, the sender claims, instead of arguing only that the interval felt long.

Health information can be governed by a federal notification rule with a different trigger and a different outer period. The federal regulation at 45 C.F.R. § 164.404 applies to a covered entity following discovery of a breach of unsecured protected health information and requires notification to each individual whose unsecured protected health information has been, or is reasonably believed to have been, accessed, acquired, used, or disclosed as a result of the breach. The timing paragraph states that the notification shall be provided without unreasonable delay and in no case later than sixty calendar days after discovery of a breach, subject to the law-enforcement delay cross-reference in the regulation. That sixty-day federal health rule does not replace a state consumer notice rule for a retailer, an employer payroll file, or a school record, and a state period does not replace the health rule for a hospital or health plan acting as a covered entity. Identify the sender’s role first, then read the period that belongs to that role.

Protection of credit should begin from the federal text that governs consumer reporting agencies, not from a monitoring advertisement. Under 15 U.S.C. § 1681c-1(i), a security freeze is defined as a restriction that prohibits a covered consumer reporting agency from disclosing the contents of a consumer report subject to the freeze to a person requesting the report. The placement paragraph states that, upon a direct request from the consumer and proper identification, the agency shall place the freeze not later than one business day after a request by toll-free telephone or secure electronic means, or three business days after a request by mail, and the confirmation paragraph states a five-business-day period for sending confirmation and removal information. Save the confirmation for each agency, the authentication mechanism, and the date each freeze was placed. A fraud alert and a security freeze are not the same instrument in that section; record which one you requested, with which agency, and what confirmation you received.

Change credentials in an order that protects the account used to reset everything else. If the notice involves an email address with a password or a security question and answer, secure that email account, then financial, health, tax, employment, and government accounts, using unique passwords and the strongest authentication the provider offers that you can maintain. Keep a dated log of accounts changed without writing the new passwords into the claim file. If a password was reused elsewhere, the date you changed each reuse is a mitigation fact; the old password itself does not need to be circulated. Where a notice says only that information may have been viewed, do not upgrade that sentence in your own notes to a certainty that it was copied. Where a notice says files were copied or acquired, do not downgrade it by assuming deletion unless a later document you have read states a deletion fact and identifies its basis.

Request records in writing and keep the request narrow enough to be answered. Ask the sender to confirm the exact data elements attributed to you, the access and discovery dates used for your notice, whether your information was in a file that was viewed, copied, acquired, or encrypted by ransomware, whether a substitute notice or regulator notice was issued, and the claim or incident reference that should be used in later correspondence. If the relationship was employment, ask which former-employer record system held the information and why it was retained, because retention and deletion were factual issues in the negligence arguments in the district orders. If the relationship was health care or health insurance, ask whether the sender treated the event as a breach of unsecured protected health information under the federal health rule. A vague request for every document about cyber security is easier to deflect than five dated questions tied to your notice.

Keep money records with the same care as medical or account records. Mitigation costs should be tied to receipts, bank records, employer leave records, postage, notary charges, replacement document fees, or other documents that show amount and date. Time spent should be logged close to when it occurred, with the task and approximate duration, rather than reconstructed as a round number months later. Emotional distress should not be exaggerated in a letter; if sleep, concentration, or health were affected, contemporaneous notes and any care records are more reliable than adjectives. The Texas order shows that emotional-harm damages can be separated from standing and tested on their own terms. The Massachusetts order shows that a separate concrete injury caused by exposure to a material risk can matter at the doorway. Both points reward a file that separates each asserted effect and documents it, instead of a single paragraph that blends worry, time, cost, and attempted misuse into one undated assertion.

B. Choose the correct track and do not let an express period expire unnoticed

A civil claim against the intruder is a separate track from a claim against the holder of the data. The federal Computer Fraud and Abuse Act text at 18 U.S.C. § 1030(g) states that a person who suffers damage or loss by reason of a violation of that section may maintain a civil action against the violator for compensatory damages and injunctive or other equitable relief, only if the conduct involves one of the factors listed in the cross-reference stated there, and it further states that no action may be brought under that subsection unless begun within two years of the date of the act complained of or the date of discovery of the damage. That provision is directed to the violator; it does not convert every negligence allegation against a business whose network was entered into a § 1030(g) claim. In most consumer files the intruder is unknown, outside practical reach, or both, so the immediate value of reading § 1030(g) is to avoid naming the wrong defendant under the wrong statute and to calendar its stated two-year period only for a claim that actually invokes that subsection.

For the holder of the data, work backward from the claim you intend to file. A California statutory-damages claimant must address the thirty-day written notice and cure language in § 1798.150(b) before initiating that statutory-damages action. A negligence claimant must identify the state whose duty and damages law governs and the filing period supplied by that law; the district orders in Part I do not supply a national negligence limitations period, and this article does not invent one. A contract claimant must find the promise, whether in a signed document, an employee record exchange, a privacy notice incorporated into the relationship, or another source that a court can read. A reader who cannot yet name the claim, the defendant, the governing state, and the source of the duty or promise is not ready to choose a deadline. That sequencing matters because a breach notice, a regulator complaint, a class claim form, and a filed court action are different acts with different effects.

Do not assume that monitoring, negotiation, a regulator inquiry, or a sender investigation pauses a filing period. The sources read for this article state specific periods for specific acts: thirty calendar days for the California disclosure discussed above subject to its stated delays, sixty calendar days as the outer federal health notification period after discovery under § 164.404, thirty days for the California written notice before a § 1798.150 statutory-damages action, one or three business days for covered consumer reporting agencies to place a security freeze after the stated kinds of direct request with proper identification, and two years for a § 1030(g) action measured as that subsection states. None of those sentences, read alone, supplies a general tolling rule for an unrelated negligence or contract suit. A conservative calendar therefore lists the access date, discovery date, notice date, each attempted-misuse date, the date any required pre-suit notice was delivered, and the earliest filing date the reader can support from a read source for the claim actually contemplated.

Settlement and claim forms require the same source discipline as a complaint. Read whether a payment is reimbursement for a documented expense, settlement of all claims arising from an incident, or enrollment in a service. Check which entities are released, whether unknown claims are mentioned, whether a class claim requires proof of a particular loss, and whether accepting a service changes any right stated in the form. Keep the blank form you received, the completed form you submitted, and the confirmation. If a form asks for a Social Security number or account information, confirm that the address or portal is the one printed in a court or sender document you already trust before sending the very identifiers the breach exposed. That verification step is part of mitigation, not a delay tactic.

Employers, insurers, schools, and providers will examine traceability. Expect questions about earlier breaches, public information, password reuse, phishing messages you answered, and accounts that used the same identifiers. Those questions do not make a later attempt irrelevant, but they mean the chronology should be candid. If the same email and password combination appeared in an earlier incident, say so in your private notes and preserve that earlier notice as well. If an attempted account access used a credential you had already changed, record the change date. If a tax or benefits agency rejects a filing, keep the agency notice rather than summarizing it from memory. A file that acknowledges alternative exposures and still ties specific dates and elements to the incident under review is more credible than a file that attributes every unwanted message after the notice to a single cause.

Finally, separate three outcomes that are often confused after a widely reported attack. A sender may notify and offer services without a court deciding that it was negligent. A regulator may examine a practice under § 45 or a health or state notification rule without awarding an individual reader damages. A civil court may find standing and still dismiss a particular claim, or deny standing on one theory while allowing amendment on another. None of those outcomes is a substitute for the others. The reader who identifies the correct defendant, the correct state or federal claim, the injury that can be documented before money is stolen, and the express period that belongs to that claim has converted a frightening notice into a set of questions that a court, a regulator, or the sender can actually answer.

Conclusion

No money stolen yet does not end the legal analysis, but it does change the proof. In federal court, plead and document the injury with precision: the data elements in your notice, whether they were viewed or acquired, any loss of control you can allege with specific facts, any material risk shown by the sensitivity of the data and the circumstances of access, any attempted misuse with dates, and any separate cost or other concrete effect tied to that risk. Then test the underlying claim separately, whether it is negligence under a named state law, an implied contract arising from the relationship that required the information, unjust enrichment, or California Civil Code § 1798.150 with its definition, reasonable-security element, and thirty-day written notice for statutory damages. Calendar only periods you have read for the act in front of you, protect credit and accounts from the confirmations you receive, and keep the intruder track under 18 U.S.C. § 1030(g) distinct from a claim against the holder of the data. A breach notice is the beginning of a record, not a judgment; the record you build in the first weeks is what allows the standing question, the merits question, and any settlement question to be decided on facts rather than on fear or on a headline.

📄 Official circular