KOHEN AVOCATS · PARIS, FRANCE
iPhone Hacked: Who Pays If a Thief Drains Your Bank Account

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

iPhone Hacked: Who Pays If a Thief Drains Your Bank Account

Speak to a lawyer 06 89 11 34 45

If you think your iPhone has been hacked, the first worry is usually not the phone itself but the bank account it unlocks. A banking app, saved passwords, text-message codes and an email inbox can give an intruder everything needed to move money out of your account in minutes. The legal question is then simple to state and urgent to answer: when someone else empties a personal checking or savings account from a compromised phone or login, who absorbs the loss, you or your bank?

Under federal law, the answer is usually your bank, with a $50 ceiling on your share in most cases, provided you report quickly and in the right way. The protection comes from the Electronic Fund Transfer Act and the Consumer Financial Protection Bureau’s Regulation E, which apply nationwide to accounts held for personal, family or household purposes. Credit cards follow a separate federal rule with a similar $50 cap. The protection weakens when you wait, when the account is a business account, or when you personally sent the money to a scammer.

Apple’s own support page on compromised accounts lists warning signs such as two-factor authentication codes you did not request and devices you do not recognize. Nothing below suggests a defect in any phone: the court cases discussed involved someone else using the account holder’s credentials, and the federal rules turn on who started the transfer, not on which device was used. The discussion that follows is general in scope: it describes checks useful in comparable situations and makes no findings about the situation of any bank or credit union named in the decisions discussed.

I. Is money moved out of your account from a hacked phone treated as an unauthorized transfer?

A. What federal law counts as an unauthorized transfer, and what it leaves out

The starting point is the definitions section of the federal Act, 15 U.S.C. § 1693a. An electronic fund transfer is any transfer of funds, other than one started by check or a similar paper instrument, that is initiated through an electronic terminal, a telephonic instrument or a computer so as to order a financial institution to debit or credit an account. The statute expressly includes transfers initiated by telephone. An unauthorized electronic fund transfer is one “initiated by a person other than the consumer without actual authority to initiate such transfer” and from which the consumer receives no benefit. The same section limits the protected “account” to one established primarily for personal, family, or household purposes, which is why a business account generally falls outside these rules.

The definition contains three exclusions that matter after a phone compromise. A transfer is not unauthorized if it was initiated by someone to whom you furnished the card, code or other means of access, unless you had told the bank that this person was no longer authorized. It is not unauthorized if you, or someone acting in concert with you, initiated it with fraudulent intent. And it is not covered if it is an error committed by the financial institution itself, which is handled under the separate error rules. Regulation E repeats these rules and defines the key term “access device” in 12 C.F.R. § 1005.2 as a card, code, or other means of access to a consumer’s account, or any combination of them, that may be used to initiate electronic fund transfers. Your online banking password and the one-time codes sent to your phone can fit within that description.

The federal regulator has addressed the hacked-phone scenario directly. In its Electronic Fund Transfers FAQs, a compliance aid last updated on January 15, 2025, the Consumer Financial Protection Bureau states that when account access information is obtained through fraudulent means such as computer hacking and a hacker uses it to make a transfer from the consumer’s account, the transfer is an unauthorized EFT under Regulation E. One of its examples is a fraudster who hacks into a consumer’s phone and uses a mobile wallet to move money out of a deposit or prepaid account. The same document addresses the person who was tricked into reading out a login code to a caller posing as the bank: “A consumer who is fraudulently induced into providing account information has not furnished an access device under Regulation E.” That answer matters because banks sometimes treat a shared code as consent. The FAQs are agency guidance, not a statute, and courts interpret the Act for themselves; they are nonetheless the regulator’s published reading of its own rule.

Two limits deserve equal attention. First, the definition turns on who initiated the transfer. If a scammer persuaded you to log in and send the money yourself, the transfer was initiated by you, and the analysis is different from a hacker using your credentials. In Williams v. Patelco Credit Union, discussed below, the court described an earlier ruling in which a plaintiff who claimed only that he had been induced through fraud to authorize a transfer had not described a qualifying error under the Act. Second, the statute excludes certain transfers made by a bank through services designed for transfers between institutions, which has led banks to argue that wire transfers fall outside the consumer protections altogether.

That wire-transfer argument was tested recently in Nelson v. Wells Fargo Bank, N.A., No. 2:25-cv-01106-JNP-DAO (D. Utah Sept. 18, 2026), decided on September 18, 2026 by the United States District Court for the District of Utah. According to the allegations the court accepted at the pleading stage, an unknown actor gained access to a couple’s checking account and to one spouse’s telephone account, then used online banking to move $67,850 out of the account in three transactions between April 16 and April 18, 2025; the couple reported the transfers by telephone on April 19, 2025. The bank argued that the transactions were wire transfers excluded from the Act. The court held that each transaction began with an electronic transfer from the consumer account to a pooled bank account, that this first step falls within the Act, and that the consumer’s liability is measured on that step. It denied the motion to dismiss the federal claim and wrote: “Though courts have yet to come to consensus on this issue, the text of the statute must prevail.” For a reader whose hijacked online banking was used to send a wire, the label on the bank’s denial letter is not the end of the analysis: ask for the internal records showing how the money first left your account. This is a single trial-court ruling that binds no other court, and the opinion itself reports that a federal court in California declined to follow the same reasoning in 2026.

The account-type limit is just as concrete. In Spivak v. JP Morgan Chase Bank, N.A., No. 22-cv-04549 (E.D.N.Y. Sept. 30, 2024), decided on September 30, 2024, the U.S. District Court for the Eastern District of New York dismissed a federal claim, with permission to amend, because the account holder kept one personal and one business account and did not say which of the disputed transfers came out of the personal one. If a compromised phone gave a thief access to both kinds of accounts, separate the transactions by account from the start, because only the personal account carries the federal protections described here.

B. How the $50, $500 and unlimited tiers work, and who has to prove what

The liability rule sits in 15 U.S.C. § 1693g and in 12 C.F.R. § 1005.6. The baseline is that your liability for an unauthorized transfer, or for a series of related unauthorized transfers, cannot exceed the lesser of $50 or the amount taken before the bank is notified or otherwise becomes aware of circumstances suggesting an unauthorized transfer. Two exceptions raise that ceiling. If the transfers followed the loss or theft of an access device and you did not notify the bank within two business days after learning of the loss or theft, your liability can reach $500, but only for amounts the bank shows would not have been taken had you reported within the two days. And if an unauthorized transfer appears on a periodic statement and you do not report it within 60 days of the bank’s transmittal of that statement, you can be liable for later transfers that occur after the 60 days and before notice, again only to the extent the bank establishes they would not have occurred had you reported in time.

Three further rules work in your favor. The regulation requires the bank to extend these time limits to a reasonable period when your delay was due to extenuating circumstances, and the statute gives extended travel or hospitalization as examples. The statute places the burden of proof on the financial institution: it must show that the transfer was authorized or, if it was unauthorized, that the conditions for imposing liability on you have been met. And the statute closes with a blunt default: “Except as provided in this section, a consumer incurs no liability from an unauthorized electronic fund transfer.” If state law or your account agreement imposes less liability than the federal rule, the lower figure applies. The CFPB’s FAQs add that negligence by the consumer cannot be used as the basis for imposing greater liability than is permissible under Regulation E, so a bank cannot raise your share because you kept a weak passcode or wrote down a PIN.

The leading appellate example is Widjaja v. JPMorgan Chase Bank, N.A., 21 F.4th 579 (9th Cir. 2021), decided on December 20, 2021 by the U.S. Court of Appeals for the Ninth Circuit. According to the complaint, identity thieves made more than 100 unauthorized withdrawals from a checking account between November 2017 and March 2019, and the account holder, who was traveling overseas for long periods, reported them only in March 2019. The court agreed that her travel allegation did not plausibly show extenuating circumstances and that a fraud alert the bank had received from another bank did not replace her own report. It nevertheless reversed the dismissal of her federal claim, holding that a consumer who misses the 60-day window is not automatically liable for later losses, because the bank must establish that those later transfers would not have occurred but for the late report. For a reader who discovers months of quiet withdrawals after a phone compromise, Widjaja means a late report hurts but does not end the claim. The ruling binds federal courts within the Ninth Circuit and is persuasive elsewhere. A recent federal trial court opinion, Williams v. Patelco Credit Union, No. 24-cv-03464-LJC (N.D. Cal. Apr. 22, 2026), decided on April 22, 2026 by the U.S. District Court for the Northern District of California, cited Widjaja at 21 F.4th 579 for the $50 baseline cap and its two exceptions, which shows that trial courts in that circuit continue to apply it.

Williams v. Patelco Credit Union, No. 24-cv-03464-LJC (N.D. Cal. Apr. 22, 2026), decided on April 22, 2026 by the U.S. District Court for the Northern District of California, is also the clearest recent illustration of the burden of proof when a phone-linked login was used. According to the opinion, the credit union pointed to multi-factor authentication codes sent to the member’s email address, a device saved to the account as trusted, and an internet address associated with the same provider he used. The court denied summary judgment on the liability claim, observing that a jury could find that someone else had obtained his credentials for both his credit union account and his email account, and that the absence of a reported breach of his email was not conclusive evidence that no breach occurred. It also held that an institution’s investigation is not itself a defense to a claim that it held the consumer liable for an unauthorized transfer: “Nothing in § 1693f provides a defense to liability for violations of § 1693g.” For an iPhone owner whose email or text messages may have been read by an intruder, a bank log showing that your password and your one-time code were used is evidence, not a verdict, because the bank still bears the burden of proving authorization. The decision is a ruling on a pretrial motion and does not decide who will prevail at trial.

Credit cards linked to the phone follow a different statute. Under 15 U.S.C. § 1643, a cardholder can be liable for unauthorized use of a credit card only if several conditions are met, and the liability cannot exceed $50; the card issuer bears the burden of proving that the use was authorized or that those conditions are met, and no liability can arise for unauthorized use occurring after the issuer has been notified. The Ninth Circuit in Widjaja described the debit-account cap as similar, but not identical, to this older credit card protection. In practice, a hacked phone that holds both a debit card and a credit card in its wallet will lead to two parallel disputes under two different federal statutes, each with its own notice process.

II. What should you do in the first days, and which deadlines apply?

A. Report to the bank in a way that triggers its legal duties

The bank’s investigation duties start only with a qualifying notice. Under 15 U.S.C. § 1693f, the notice must reach the institution within sixty days after it transmitted the statement showing the problem, and it must enable the institution to identify your name and account number, indicate your belief that the account contains an error and the amount of the error, and set out the reasons for that belief. An unauthorized electronic fund transfer is expressly listed as an error. The notice may be oral or written, but the institution may require written confirmation within ten business days of an oral notice if it tells you so when you call and gives the address. If you are asked for written confirmation, send it, because a bank that requires it and does not receive it in time need not provisionally recredit your account.

Once a proper notice is received, 12 C.F.R. § 1005.11 sets the timetable. The institution must investigate promptly and determine whether an error occurred within 10 business days, report the results within three business days after completing its investigation, and correct an error within one business day after determining that it occurred. If it needs more time, it may take up to 45 days, but only if it provisionally credits your account within 10 business days of receiving the notice, tells you within two business days after the provisional credit, and gives you full use of the funds during the investigation. The regulation lengthens these periods in defined cases, for example 20 business days instead of 10 when the transfer occurred within 30 days after the first deposit to a new account, and 90 days instead of 45 for point-of-sale debit card transactions and transfers not initiated within a state. If the bank concludes that no error occurred, the statute requires an explanation of its findings within 3 business days after the investigation ends and, on request, copies of the documents it relied on. The CFPB’s FAQs add that an institution may not delay its investigation by first requiring you to contact a merchant.

The wording of the first report can decide the case, as Sundahl v. Comerica Bank, No. 3:25-cv-01473-RBM-DDL (S.D. Cal. Jan. 15, 2026) shows. Decided on January 15, 2026 by the U.S. District Court for the Southern District of California, the case involved an account used for Social Security deposits; the plaintiff alleged that fraudulent transactions totaling about $6,815 were made in November 2024 and that he immediately disputed the loss of the funds. The court dismissed the federal claim, with leave to amend, because the complaint did not show that his notice identified an unauthorized transfer, gave the reasons for his belief, or identified the statement that first reflected the transactions, so it could not infer that he had reported an unauthorized electronic transfer at all. Apply that holding directly: when you call and when you write, say that each listed transfer was unauthorized, that you did not initiate it and received no benefit from it, list the date and amount of each one, and explain why you believe it was not yours, such as a login from a device you do not own or a code you never requested.

Securing the phone and the accounts runs alongside the legal notice, not after it. Apple’s support guidance for a compromised Apple Account tells users to change the password, remove devices they do not recognize, and check with their email provider and cellular carrier that they control every address and number tied to the account, including that text-message forwarding has not been set up. That last step matches the facts alleged in Nelson, where the intruder had also gained access to a telephone account. Each of these steps also creates a record: screenshots of unrecognized devices, carrier confirmations and password-reset emails can become the reasons your notice must state and the evidence a bank must answer when it carries the burden of proof.

Keep a written log from the first hour. Note when you first noticed the problem, every call to the bank with the date, time and the name or employee number given, the reference number of the claim, and every letter or message received. The time limits run from events that you will later need to prove, such as when you learned of a theft, when a statement was sent, and when the bank received notice. The regulation treats notice as given when you take steps reasonably necessary to provide the institution with the pertinent information, whether or not a particular employee actually receives it, and treats written notice as given when you mail it or deliver it for transmission by any other usual means. A dated letter or a secure-message record therefore protects you better than a recollection of a phone call.

B. Police reports, identity theft reports and the deadlines for going to court

A hacked phone that leads to a drained account usually involves a federal crime. Under 18 U.S.C. § 1030, the federal computer fraud statute, it is an offense to intentionally access a computer without authorization or in excess of authorized access and thereby obtain information contained in a financial record of a financial institution, among other conduct. The same section lets any person who suffers damage or loss by reason of a violation bring a civil action against the violator, but only if the conduct involves one of several listed factors, the first being a loss to one or more persons during any one-year period aggregating at least $5,000 in value. Such an action must be begun “within 2 years of the date of the act complained of or the date of the discovery of the damage.” In practice, a civil suit against an unidentified hacker rarely recovers money, but a police report and a federal complaint create a record that banks, card issuers and credit bureaus routinely ask for. A related article explains how federal computer-crime law treats a break-in to a stolen gaming account, which follows the same statute.

The Federal Trade Commission’s recovery checklist at IdentityTheft.gov is government guidance rather than a statute, but it is the practical map for what follows a phone compromise. It explains that the site creates an FTC Identity Theft Report and a recovery plan, that a fraud alert makes it harder for someone to open new accounts in your name, that an extended fraud alert lasts seven years for identity theft victims, and that a credit freeze lasts until you lift it. It also explains that with an FTC Identity Theft Report, credit bureaus must honor a request to block information that resulted from identity theft. If the thief used your phone to open new credit, these steps matter as much as the bank dispute; if the thief only moved money out of an existing account, the bank dispute under the federal transfer rules remains the main path to getting the money back.

If the bank refuses to reimburse you, the federal Act provides a private lawsuit. Under 15 U.S.C. § 1693m, an institution that fails to comply with the Act is liable for actual damages, an additional amount between $100 and $1,000 in an individual action, and the costs of a successful action together with a reasonable attorney’s fee as determined by the court. The institution can avoid liability if it shows the violation was not intentional and resulted from a bona fide error despite procedures reasonably adapted to avoid it. Separately, § 1693f entitles the consumer to treble damages when a court finds that the institution did not provisionally recredit within the ten-day period and either did not make a good faith investigation or lacked a reasonable basis for believing the account was not in error, or that it knowingly and willfully concluded there was no error when that conclusion could not reasonably have been drawn from the evidence available. The deadline is short: an action may be brought in federal court or any other court of competent jurisdiction “within one year from the date of the occurrence of the violation.”

Courts have read that one-year period with attention to which violation is claimed. In the Spivak decision of September 30, 2024, the Eastern District of New York explained, quoting an earlier ruling of that court, that for a failure-to-investigate claim the limitations period begins to run ten days after the consumer provides oral or written notice of the alleged error, and it treated the account holder’s suit, filed on August 2, 2022 after an August 4, 2021 report, as timely on that theory. The same opinion repeated that even without timely notice, a bank remains liable for unauthorized debits that occurred during the sixty-day period, provided the customer brings a claim within the statute of limitations. Those statements come from one federal trial court applying the statute to its facts; they are not a general accrual rule for every type of claim. The safe reading for a hacked-phone victim is to treat the transfer date and the end of the bank’s ten-business-day investigation period as the dates that start the clock, and to calendar the first anniversary of the earliest of them.

Finally, read your account agreement but do not treat it as the last word. The CFPB’s FAQs point to the Act’s anti-waiver provision, under which no agreement between a consumer and any other person may waive a right conferred by the Act, and state that an agreement cannot restrict a consumer’s rights beyond what the law provides. A clause saying that you are responsible for any transaction made with your password, or that sharing a code forfeits your protections, does not override the federal liability limits for a personal account. Where state law gives more protection than the federal floor, the regulation lets the lower liability figure control, so consumers in states with their own funds-transfer rules should ask whether those rules add anything. The account agreement remains relevant to other questions, such as how the bank must be notified, which address to use, and which claims beyond the federal Act may be available.

Conclusion

A hacked iPhone is a security problem first, but the money question is governed by clear federal rules. When someone else initiated the transfer from a personal account without your authority and you received nothing from it, federal law treats it as unauthorized, caps your share at $50 in most cases, and puts the burden on the bank to prove otherwise. The protection shrinks when you wait: two business days matter when a means of access was lost or stolen, and sixty days from the statement matter for later losses. It also depends on the words of your first report, which must name the transfers, say they were unauthorized and explain why. Courts have recently applied these rules to hijacked logins and online banking wires, though not always in the same way. Report each transfer in writing, keep every record, secure the phone and the email accounts tied to it, and mark the one-year deadline for a federal claim on your calendar on the day you discover the loss.

📄 Official circular