Optimizely published a security notice on its service-status page timestamped November 17, 2026, at 01:02 UTC. According to that notice, the company identified a security incident in which an unauthorized party exploited a vulnerability in its Experimentation product and used it to add malicious JavaScript to some customer projects; the component the notice lists as affected is Web Experimentation (Snippet Delivery). The company states that it has fixed the vulnerability, removed the injected code from the affected projects, taken steps to secure affected user accounts and put additional protections in place to prevent unauthorized code from being delivered. The notice does not identify the websites involved, does not describe what the code did, and does not say that any visitor’s payment details were captured. As of this writing, no court or agency has made any finding about how the incident happened or about anyone’s responsibility for it.
In Google Trends data for the United States, “optimizely attack” and “optimizely data breach” were among the fastest-rising related searches on November 17, 2026, and the question behind them is practical. If you typed a card number on a website that may have loaded injected code, who absorbs a fraudulent charge, how fast do you need to act, and can you sue anyone? Federal law answers the first two questions with unusual precision for credit cards, debit cards and bank accounts. The third depends on how federal courts apply the standing doctrine to data-security cases, and on state statutes such as California’s. The discussion that follows is general in scope: it describes checks useful in comparable situations and makes no findings about Optimizely’s situation.
I. If your card details were exposed, how much of a fraudulent charge is yours to pay?
A. Credit cards: a federal $50 ceiling, a phone call and a 60-day letter
Start with the rule that matters most to anyone who paid by credit card. Under the federal Truth in Lending Act, 15 U.S.C. § 1643 limits a cardholder’s exposure for unauthorized use. A cardholder can be held liable only if several conditions are met, including that “the liability is not in excess of $50” and that the unauthorized use occurred before the card issuer was notified. The same section closes the door on anything beyond that: “Except as provided in this section, a cardholder incurs no liability from the unauthorized use of a credit card.” It also puts the burden of proof on the card issuer, not on you, to show either that a use was authorized or, if it was not, that the conditions for charging you the capped amount have been met.
The federal Regulation Z repeats and sharpens the rule. Under 12 C.F.R. § 1026.12(b), “unauthorized use” means “the use of a credit card by a person, other than the cardholder, who does not have actual, implied, or apparent authority for such use, and from which the cardholder receives no benefit.” A charge run by someone who copied your number from a checkout page fits that definition on its face: you gave that person no authority, and you received nothing from the purchase. The regulation caps your liability at the lesser of $50 or the amount obtained before you notify the issuer, and it makes notice easy to give: “Notification may be given, at the option of the person giving it, in person, by telephone, or in writing.” One more sentence is worth reading closely: “If state law or an agreement between a cardholder and the card issuer imposes lesser liability than that provided in this paragraph, the lesser liability shall govern.” If your cardholder agreement promises that you will owe less than $50, or nothing, that promise controls.
The liability cap is only half of the federal toolkit. The federal billing-error statute, 15 U.S.C. § 1666, governs how you get a disputed charge removed from your statement. A billing error includes “A reflection on a statement of an extension of credit which was not made to the obligor,” which is how the statute describes a charge you did not make. The procedure is triggered when the creditor receives your written notice, at the address it discloses for that purpose, within sixty days after it transmitted the statement that shows the charge. The notice must identify your name and account number, state that you believe the statement contains a billing error and its amount, and give your reasons. Once that letter arrives, the creditor must send a written acknowledgment within thirty days, unless it resolves the matter sooner, and within two complete billing cycles, and in no event later than ninety days, it must either correct the account or send a written explanation after investigating.
Two further protections in section 1666 matter while a dispute is open. A creditor operating an open-end consumer credit plan may not restrict or close your account, before it sends its written explanation, solely because you did not pay the amount you identified as an error. And a creditor that fails to follow the procedure forfeits the right to collect the disputed amount and related finance charges, although the statute limits that forfeiture to $50. Those rules give a cardholder leverage, but only if the written notice exists. A telephone call is valid notification for the liability rules of section 1643 and Regulation Z; it does not, by itself, satisfy the written-notice requirement of section 1666.
The practical sequence follows from the texts. Call the issuer as soon as you see a charge you do not recognize, because notification by telephone is valid under the regulation and the federal cap is measured by what was charged before notice. Then send the written billing-error notice to the address printed on your statement for billing errors, not on a payment coupon, so that it reaches the creditor within sixty days after the statement that first shows the charge was transmitted. Keep a copy and proof of when it was sent or submitted. Nothing in section 1643 or section 1666 makes your protection depend on identifying how a thief obtained your number; the statutes ask whether you authorized the use, and section 1643 places the burden of proof on the issuer. That matters after an incident involving third-party code, because a cardholder who used the same card on several websites in the same week is rarely able to say which one exposed it.
B. Debit cards, bank transfers and crypto: the deadlines that change your share
Debit cards and bank accounts are governed by a different federal statute, the Electronic Fund Transfer Act, and its timing rules are stricter. Under 15 U.S.C. § 1693a, an unauthorized electronic fund transfer is “an electronic fund transfer from a consumer’s account initiated by a person other than the consumer without actual authority to initiate such transfer and from which the consumer receives no benefit.” The definition excludes transfers by someone you furnished with your card, code or other means of access, unless you had told the institution that person’s transfers were no longer authorized; transfers initiated with fraudulent intent by you or by someone acting in concert with you; and errors committed by the financial institution. A purchase made by a stranger with a debit card number lifted from a payment form falls within the core of the definition.
How much you can lose depends on when you report. The federal liability section, 15 U.S.C. § 1693g, sets a baseline of the lesser of $50 or the amount obtained before the institution is notified, then adds two later tiers. If you fail to report a loss or theft of a card or other means of access within two business days after you learn of it, your liability can rise, but not above $500. And the statute provides that “reimbursement need not be made to the consumer for losses the financial institution establishes would not have occurred but for the failure of the consumer to report within sixty days of transmittal of the statement” any unauthorized transfer or account error that appears on that statement. In each case the burden of proof is on the financial institution, and the statute allows a longer, reasonable period in extenuating circumstances such as extended travel or hospitalization.
The federal Regulation E, at 12 C.F.R. § 1005.6, spells out the same structure in operational terms. If you notify the institution within two business days after learning of the loss or theft of the access device, your liability cannot exceed the lesser of $50 or the transfers that occur before notice. If you do not, the ceiling becomes $500, with the amounts above $50 limited to transfers the institution shows would not have occurred had you reported within that two-day period. Separately, a consumer “must report an unauthorized electronic fund transfer that appears on a periodic statement within 60 days of the financial institution’s transmittal of the statement to avoid liability for subsequent transfers.” The regulation requires the institution to extend these periods to a reasonable time when the delay was due to extenuating circumstances, and it accepts notice in person, by telephone or in writing.
Read those two triggers separately, because they do not start at the same moment. The regulation measures the first from the day you learn of the loss or theft of the access device and the second from the transmittal of the statement on which the unauthorized transfer appears. Neither text says what counts as learning of a loss when only a card number may have been copied while the card itself stayed in your wallet, so the safe course is to report as soon as you see an unfamiliar transaction or receive a notice saying your card data may be involved. Prompt reporting satisfies every version of the rule; waiting until you are certain does not improve your position.
Once you report, the bank’s own deadlines start. Under 12 C.F.R. § 1005.11, the federal error-resolution procedure covers an oral or written notice received no later than 60 days after the institution sends the periodic statement on which the error is first reflected. The institution must investigate promptly and “shall determine whether an error occurred within 10 business days of receiving a notice of error.” It may take up to 45 days instead only if, among other conditions, it provisionally credits your account for the amount in dispute within 10 business days, and it may withhold up to $50 of that credit when it has a reasonable basis for believing an unauthorized transfer occurred and has met the regulation’s disclosure conditions. The 45-day period becomes 90 days for certain transfers, including those that resulted from a point-of-sale debit card transaction. A bank may require you to confirm an oral notice in writing within 10 business days, and if it requires that confirmation and does not receive it, it need not provisionally credit your account. Our earlier guide on what happens when a thief drains a bank account after a phone compromise walks through the same federal tiers from the account holder’s side.
Cryptocurrency is where the federal safety net is least certain. Section 1693a defines an “account” as “a demand deposit, savings deposit, or other asset account” established primarily for personal, family, or household purposes, as described in the Bureau’s regulations, and it defines an electronic fund transfer as a transfer of funds initiated electronically “so as to order, instruct, or authorize a financial institution to debit or credit an account.” Whether a given wallet or exchange account fits those definitions is not answered by the texts and decisions discussed in this guide. A second problem is structural. Malicious code that swaps the wallet address displayed on a page does not move your funds by itself; it induces you to send them. The federal definition of an unauthorized transfer turns on a transfer “initiated by a person other than the consumer,” and a payment you initiated to an address you believed was correct fits that wording poorly. If you sent crypto from a page that may have been affected, report it at once to the platform you sent from, keep the transaction identifier, the receiving address and screenshots, and do not assume that the card and bank rules described above will reimburse you.
II. Can a visitor sue the business whose website ran the code?
A. Federal courts: a fraudulent charge is an injury, fear of future misuse usually is not
Before a federal court considers whether a business protected its systems adequately, a plaintiff must show standing under Article III of the Constitution: a concrete injury, caused by the defendant, that a court can redress. In data-security cases that threshold decides most of the early fights. The decisions below draw a consistent line between people who have already suffered misuse of their information and people who only fear it, although the federal circuits do not place that line in exactly the same spot.
The closest comparable dispute involves stolen payment card data. In In re SuperValu, Inc., 870 F.3d 763 (8th Cir. 2017), decided on August 30, 2017 by the U.S. Court of Appeals for the Eighth Circuit, sixteen customers sued the operators of grocery stores after cyber criminals accessed the network that processed payment card transactions for 1,045 stores in 2014 and installed malicious software on it. The court accepted, at the pleading stage, that the card information had been stolen, but it held that the plaintiffs had not plausibly alleged a substantial risk of future identity theft, observing that “there is little to no risk that anyone will use the Card Information stolen in these data breaches to open unauthorized accounts in the plaintiffs’ names.” The time those plaintiffs spent monitoring their accounts could not create an injury either. One plaintiff was different: he alleged a fraudulent charge on the credit card he had used at one of the affected stores, and the court held that this misuse gave him standing, while leaving the defendants free to contest later whether the breach actually caused that charge. For a reader, the lesson is direct: a fraudulent charge you can document after using your card on an affected site is the kind of injury the Eighth Circuit recognized, while the bare possibility that a card number might be misused was not enough.
That framework is still being applied. On August 27, 2026, the U.S. District Court for the District of Minnesota decided Nunow v. FEI.COM, Inc., No. 26-cv-1598 (D. Minn. Aug. 27, 2026), a data-security class action about personal information stored on a platform used to assess eligibility for government programs, and cited In re SuperValu, Inc., 870 F.3d 763, repeatedly. Summarizing the case law, the court wrote that “A plaintiff who claims to have suffered identity theft or fraudulent credit charges plausibly alleges Article III injury,” relying on the Eighth Circuit’s treatment of the shopper with the fraudulent charge, and that data which generally cannot be used alone to open new accounts makes a future injury harder to show. Because the plaintiff alleged no fraud and could only speculate about where her information had gone, the court found no Article III injury; and because the case had been removed from state court, it sent the case back to the Minnesota state court in Ramsey County instead of dismissing it. The 2026 decision shows the 2017 rule still in use, and it shows that losing on federal standing can mean a return to state court rather than the end of a claim.
Other circuits draw the line in slightly different places, and the Fourth Circuit’s recent decision shows how much the details matter. In Holmes v. Elephant Insurance Co., No. 23-1782 (4th Cir. Oct. 14, 2025), the U.S. Court of Appeals for the Fourth Circuit reviewed a class action brought after an intrusion into an insurer’s network in 2022 compromised the driver’s license numbers of nearly 3 million people; the plaintiffs alleged that the intruders used the auto-populate feature of the insurer’s online quoting platform. In its decision of October 14, 2025, the court held that the two plaintiffs who alleged they had found their driver’s license numbers listed on the dark web had suffered a concrete injury, by analogy to the common-law tort of public disclosure of private information, and could seek damages because, in the court’s words, “The publicity given to their driver’s license numbers inflicted a concrete harm” sufficient to establish an actual injury. The two plaintiffs who did not allege that their numbers had been made public lacked standing. The court also rejected the risk of future misuse as too speculative under its own precedent, which sets a floor of at least 33 percent for a substantial risk in data-breach cases, and it held that time spent and emotional distress “may serve as the sole basis for standing to recover damages only when incurred in response to a separate imminent harm.” For someone whose card data may have been captured, the practical point is that evidence that your data was actually published or misused changes the standing analysis, while worry and monitoring time alone usually do not.
The Fourth Circuit acknowledged that other federal circuits have found imminent injury in similar situations, including from credit card numbers compromised in a cyberattack, and it explained why it draws a tighter boundary. That divergence has a practical consequence. Federal appeals court decisions bind the district courts within their own circuits, so the same set of facts can be analyzed differently in different parts of the country. When a class action is filed after a widely reported incident, where it is filed, and whether it stays in federal court, can matter as much as the facts of any individual visitor’s loss.
B. State statutes, settlements and the records that make a claim provable
State statutes add their own remedies and conditions, and California offers the most developed example. Under California Civil Code section 1798.81.5, a business that owns, licenses or maintains personal information about a California resident must implement and maintain reasonable security procedures and practices appropriate to the nature of the information, to protect it from unauthorized access, destruction, use, modification or disclosure. For this purpose, personal information includes a person’s name combined with an “Account number or credit or debit card number, in combination with any required security code, access code, or password that would permit access to an individual’s financial account.” That is the combination an online payment form typically asks for.
The private right of action sits in California Civil Code section 1798.150. A consumer whose nonencrypted and nonredacted personal information, as defined in section 1798.81.5, is subject to unauthorized access and exfiltration, theft or disclosure as a result of a business’s violation of its duty to implement and maintain reasonable security may sue for damages “not less than one hundred dollars ($100) and not greater than seven hundred and fifty ($750) per consumer per incident or actual damages, whichever is greater,” with those amounts subject to adjustment under section 1798.199.95, and for 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; if a cure is possible and the business actually cures within those 30 days and says so in an express written statement, no action for statutory damages may be brought. Improving security after a breach does not count as a cure for that breach. The notice step does not apply to every claim: “No notice shall be required prior to an individual consumer initiating an action solely for actual pecuniary damages suffered as a result of the alleged violations of this title.” The statute does not make every exposure actionable. It requires a failure of reasonable security by the business and the kind of unauthorized access and exfiltration, theft or disclosure that the section describes.
California also shapes how a resident is likely to hear about an incident. Under California Civil Code section 1798.82, a person or business that conducts business in California and owns or licenses computerized data that includes personal information must 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. Since an amendment effective January 1, 2026, “the disclosure required by this subdivision shall be made within 30 calendar days of discovery or notification of the data breach,” subject to delays for the legitimate needs of law enforcement or as necessary to determine the scope of the breach and restore the reasonable integrity of the data system. A business that maintains computerized data it does not own must notify the owner or licensee immediately following discovery. Under that structure, the duty to notify residents falls on the business that owns or licenses the data, so a notice, if one is required, will normally come from the business you dealt with. Whether a particular incident meets the statute’s definition of a breach of the security of the system, which turns on the unauthorized acquisition of computerized data, is a question that business has to answer first.
When a California notice is sent, its form is regulated too. It must be written in plain language, titled “Notice of Data Breach,” and organized under headings that include “What Happened?” and “What You Can Do.” At a minimum it must list the types of personal information believed to have been involved and, if that can be determined, the date, estimated date or date range of the breach, together with the date of the notice. A notice that tells you which data elements and which dates were involved is the starting point for matching any charge on your statement to the period at issue.
What does a successful payment-card case actually pay? The most detailed recent answer comes from In re Wawa, Inc. Data Security Litigation, No. 24-1874 (3d Cir. June 25, 2025), decided by the U.S. Court of Appeals for the Third Circuit on June 25, 2025. According to the opinion, malware on a convenience store chain’s payment processing servers began running on March 4, 2019, and the stolen card information was later put up for sale on a dark-web marketplace. The consumer settlement offered three tiers: a $5 gift card for class members who affirmed they spent at least some time monitoring their statements, a $15 gift card for those who saw a fraudulent charge that required some effort to sort out, and up to $500 in cash for those who could show certain out-of-pocket losses caused by the breach, alongside commitments to improve payment security. The court affirmed the approval of class counsel’s fee, upheld the finding that there was no improper side agreement, and noted that the claims rate was about 2.56 percent of roughly 22 million class members, adding that “Class actions involving little overall harm typically have a low claims rate.” The application to anyone worried about card skimming is concrete: the cash tier in that settlement went to people who could document out-of-pocket losses, so receipts, statements and records of fees matter more than a general sense of having been exposed.
The same decision is a reminder of time scales. The Third Circuit’s account runs from the discovery of the intrusion in December 2019, through a settlement reached after a single mediation session in 2020, a preliminary approval in 2021, a final approval in 2022, an earlier appeal and a remand, to the affirmance in June 2025. A class settlement, if one ever comes, is not where an individual visitor recovers a fraudulent charge in the short term. That recovery comes much faster through the issuer or bank under the federal rules in Part I.
Whatever forum you end up in, the same records do the work. Keep the statement that shows any unfamiliar charge and the date you first saw it. Note the date and time of your call to the issuer or bank and any reference number you were given. Keep a copy of the written billing-error or error notice and proof of when it was sent. Save any provisional-credit notice and the institution’s final decision. Keep any notice of a security incident you receive from a business, with its date, and record out-of-pocket costs such as replacement-card fees, late fees caused by a frozen card, or overdraft charges, with receipts. If you used the card on a website during a period that a business later identifies, a dated order confirmation or account history ties your use to that window. None of these steps requires you to accuse anyone; they preserve the facts that the federal liability rules, the California statutes and the courts in the decisions above actually ask about.
Conclusion
A company’s confirmation that malicious code reached some of its customers’ projects is a reason to check your accounts; it does not by itself establish that your data was taken or that anyone is liable. Federal law gives card users the clearest protection. For a credit card, liability for unauthorized use is capped at $50 or less, and a written billing-error notice that reaches the issuer within 60 days after the statement was sent obliges it to investigate. For a debit card or bank account, the amount you can lose depends on reporting within two business days of learning of a loss or theft and within 60 days of the statement, and the bank must then decide within the regulation’s time limits. Crypto sent to a swapped address is not clearly covered by those rules. Suing is a separate question: federal courts have recognized standing for an alleged fraudulent charge or for data alleged to have been posted where many people can see it, but not, on their own, for fear of future misuse or time spent monitoring, and California adds a statutory claim with its own notice-and-cure step. Report quickly, put disputes in writing, and keep the records that tie any loss to the dates and websites involved.