# Kenneth Baylor v. Ledger SAS - Filed Class Action Complaint Canonical: https://hallattorneys.com/dockets/ledger-spyware Source PDF: https://hallattorneys.com/dockets/ledger-spyware/01-complaint.pdf Filed: October 30, 2026 Docket entry: ECF No. 1 Case number: 3:26-cv-12867 Court: U.S. District Court for the Northern District of California, San Francisco Division Defendant: Ledger SAS The following is extracted text of the original 51-page complaint. Allegations are not findings. No class has been certified. The PDF controls if extraction differs. Case 3:26-cv-12867 Document 1 Filed 10/30/26 Page 1 of 51 PageID #: 1 1 CHRISTOPHER FROST (SBN 200336) chris@frostllp.com 2 KEVIN S. DICKER (SBN 179315) kevin@frostllp.com 3 FROST LLP 10960 Wilshire Boulevard, Suite 2100 4 Los Angeles, California 90024 Telephone: (424) 254-0441 5 Facsimile: (424) 600-8504 6 Attorneys for Kenneth Baylor 7 8 UNITED STATES DISTRICT COURT 9 NORTHERN DISTRICT OF CALIFORNIA, SAN FRANCISCO DIVISION 10 11 KENNETH BAYLOR, individually and on behalf of all others similarly situated, 12 Plaintiff, 13 vs. 14 LEDGER SAS, 15 Defendant. 16 17 Case No. 26-12867 CLASS ACTION COMPLAINT 1. Breach of Express Warranty 2. CLRA (Injunctive Relief Only) 3. Negligence 4. Strict Liability—Design Defect 5. Strict Liability—Failure to Warn 6. UCL (Injunctive Relief Only) DEMAND FOR JURY TRIAL 18 19 20 21 22 23 24 25 26 27 28 Case No. 26-12867 CLASS ACTION COMPLAINT Case 3:26-cv-12867 1 Document 1 Filed 10/30/26 Page 2 of 51 PageID #: 2 Plaintiff Kenneth Baylor, individually and on behalf of the proposed Class, brings this action 2 against Defendant Ledger SAS. Plaintiff alleges matters concerning his own conduct and 3 experiences on personal knowledge and other matters on information and belief, based on the 4 investigation of counsel, purchase and transaction records, manufacturer publications, and the other 5 facts alleged below. 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 I. NATURE OF THE ACTION Ledger sells hardware wallets to protect the secrets that control its customers' cryptocurrency. It designed the hardware, prescribed the packaging and setup process, selected the official distribution channels, and supplied the authentication on which consumers were told to rely. This action arises from Ledger's failure to secure that system against a known threat: concealed spyware that captures recovery information during legitimate setup while the device passes Ledger's Genuine Check. A product purchased to prevent theft instead exposed the information that made the theft possible. Plaintiff Kenneth Baylor is a California citizen and resident of San Mateo County who purchased his first Ledger device in the United States and used Ledger products from San Mateo County, California, for nearly a decade. Ledger deliberately served that California market, publicly identified San Francisco as a headquarters location, and promoted the Flex product family in this District. In 2026, he followed Ledger's Official Reseller Network to acquire two new Ledger Flex devices from CryptoBilis, which Ledger identified as an official reseller. He used Ledger's official application, received successful Genuine Check results, and generated new recovery information on the devices before committing his assets. His reliance arose from Ledger's continuing security relationship with a California customer and Ledger's own product, distribution designation, and authentication. Ledger's official designation induced Baylor to obtain the products through the channel Ledger presented as protecting their integrity; Genuine Check supplied a separate assurance during setup. Baylor kept the recovery information offline and did not authorize the transfers at issue. Nevertheless, in October 2026, Bitcoin and Ether with a contemporaneously estimated value of approximately $1.05 million were taken. On information and belief, an unauthorized modification 2 CLASS ACTION COMPLAINT Case No. 26-16867 Case 3:26-cv-12867 Document 1 Filed 10/30/26 Page 3 of 51 PageID #: 3 1 to one or more of the devices acquired recovery information generated during legitimate setup while 2 leaving the authentic Secure Element able to pass Genuine Check. 3 Ledger controlled the original hardware design, packaging specifications, authentication 4 protocol, setup instructions, and official reseller designation, including its representations about the 5 integrity of products obtained through that network. It failed to protect the complete recovery6 information path, detect and respond to pre-delivery tampering before sensitive operation, provide 7 effective evidence of interference, and disclose the material limits of its successful authentication. 8 Those manufacturer-level failures allowed an altered product to reach a consumer, pass Ledger's 9 prescribed check, and expose newly generated secrets. The identity of the person who installed an 10 implant does not eliminate the causal role of Ledger's original design and its own security 11 assurances. 12 The challenged failures extend beyond a single reseller. They concern the protection of 13 Ledger hardware throughout manufacturing and assembly, storage, shipping, retail distribution, and 14 returns handling, and the security determination presented when the device reaches its user. 15 Published Nano X implant examinations, Karpelès's reported finding of an implant in a Flex 16 purchased at Singapore Airport, the apparent Stax report, and successive reports from separate 17 MediaMarkt locations support investigation across device families, retailers, and upstream 18 inventory sources. Ledger has also acknowledged a coordinated suspension of MediaMarktSaturn 19 sales while the investigation proceeds. Ledger possesses the product and distribution records needed 20 to identify the affected configurations and points of unauthorized access. Plaintiff seeks relief for 21 one Class of consumer purchasers who lost cryptocurrency through spyware installed in their Ledger 22 hardware wallets before delivery. The Class reaches all Ledger models and sales channels; model23 specific examination protocols can account for technical differences without dividing the Class. 24 Plaintiff seeks compensation for deficient security functionality and the theft of his 25 separately owned cryptocurrency, and preliminary and permanent injunctive relief requiring Ledger 26 to stop the continuing deceptive practices and establish a protective recall, professional inspection, 27 and secure-replacement program. The program must protect Class members against further exposure 28 through their retained or replacement Ledger devices across sales channels. Access must not require 3 CLASS ACTION COMPLAINT Case No. 26-16867 Case 3:26-cv-12867 Document 1 Filed 10/30/26 Page 4 of 51 PageID #: 4 1 Class members to open their own devices or independently identify an implant before receiving 2 professional assistance. Plaintiff seeks present injunctive relief under the CLRA and California's 3 Unfair Competition Law. He will provide the separate CLRA notice and corrective demand 4 contemporaneously with filing and seek CLRA damages and other remedies subject to Civil Code 5 section 1782 by amendment after compliance with that statute. 6 7 II. PARTIES Plaintiff Kenneth Baylor is a natural person, a United States citizen, and a citizen of 8 California. He is domiciled in and resides in San Mateo County, California. 9 Baylor purchased the devices for personal use in securing cryptocurrency that he owned. His 10 claim is not brought on behalf of a business. He seeks relief for his own purchases and property 11 losses and for similarly situated members of the Class defined below. 12 Defendant Ledger SAS is a citizen of France organized under French law. On information 13 and belief, its present principal place of business is in Paris, France. Ledger identifies its address as 14 106 rue du Temple, 75003 Paris, France. 15 Ledger designs, manufactures, markets, and distributes Ledger hardware wallets, including 16 the Flex, and supplies the official companion application and Genuine Check. The application is 17 referred to in Plaintiff's records as Ledger Live and in current Ledger publications as Ledger Wallet. 18 This Complaint uses 'Ledger application' for the official companion application and 'Genuine Check' 19 for the authentication at issue. 20 CryptoBilis sold the two Flex devices to Baylor after Ledger identified that business in its 21 Official Reseller Network as CryptoBilis PH. Ledger SAS supplied the products' original security 22 architecture, packaging specifications, official authentication, and reseller designation. Plaintiff 23 challenges Ledger SAS's own conduct in designing, authenticating, promoting, and distributing the 24 products through the system it created and maintained. 25 26 27 28 III. JURISDICTION, VENUE, AND DIVISIONAL ASSIGNMENT Jurisdiction. This Court has original jurisdiction under 28 U.S.C. § 1332(a)(2) (2024). Plaintiff is a citizen of California, Defendant is a citizen of France, and the amount in controversy on Plaintiff's individual claims exceeds $75,000, exclusive of interest and costs. His 4 CLASS ACTION COMPLAINT Case No. 26-16867 Case 3:26-cv-12867 Document 1 Filed 10/30/26 Page 5 of 51 PageID #: 5 1 contemporaneous estimate of the cryptocurrency loss is approximately $1.05 million. The Court has 2 supplemental jurisdiction under 28 U.S.C. § 1367 (2024) over related class claims within its scope 3 because those claims form part of the same case or controversy. 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 Ledger purposefully cultivated and served California consumers through direct hardwarewallet sales, delivery to California addresses, collection of California sales tax, and the software, authentication, and security communications accompanying its products. The Ninth Circuit has already recognized that Ledger's California sales, tax collection, and delivery practices constitute purposeful availment of this State: the record before that court included approximately 70,000 wallets sold directly to Californians, generating millions of dollars in revenue. Ledger's own San Francisco headquarters representations and its subsequent promotion of Flex and Stax in this District further demonstrate its deliberate development of the California market. On information and belief, Ledger continues serving that market with the Flex product family and associated product-security services challenged here.1 Ledger publicly held itself out as "Headquartered in Paris and San Francisco." In February 2015, Ledger announced the opening of its U.S. subsidiary and San Francisco offices as part of its consumer-product expansion. Its January 18, 2018 financing announcement described an operating team developing cryptocurrency-security products, including its hardware-wallet line, across San Francisco, Paris, and Vierzon. The announcement identified Ledger SAS in its corporate notices. Ledger's 2018 headquarters representation coincided with Baylor's continuing California use of its products. Ledger's California presence was part of its deliberate effort to develop the market for the security products and services at issue. 2 1 Baton v. Ledger SAS, No. 21-17036, 2022 WL 17352192, at *1 (9th Cir. Dec. 1, 2022) 24 (unpublished memorandum; describing the California sales record in that action). See also Ford Motor Co. v. Mont. Eighth Jud. Dist. Ct., 592 U.S. 351, 362–67 (2021). 25 2 Ledger, Ledger Raises USD 75 Million to Secure Cryptocurrency Assets (Jan. 18, 2018), 26 https://www.ledger.com/ledger-raises-usd-75-million-secure-cryptocurrency-assets (About Ledger and Disclaimers). See also Ledger, Ledger Raises a 1.3M€ Seed Round to Accelerate the 27 Development of Its Bitcoin Security Solutions (Feb. 19, 2015), https://www.ledger.com/ledger28 raises-a-1-3me-seed-round-to-accelerate-the-development-of-its-bitcoin-security-solutions 5 CLASS ACTION COMPLAINT Case No. 26-16867 Case 3:26-cv-12867 1 Document 1 Filed 10/30/26 Page 6 of 51 PageID #: 6 Ledger expanded its U.S. operations before Baylor's 2026 purchases. On March 20, 2026, 2 Ledger announced the opening of a New York City office as part of a multimillion-dollar investment 3 in its U.S. presence, creating dozens of positions across Ledger Enterprise and marketing. Ledger 4 identified the United States as its largest global market, described the office as a strategic hub for 5 its institutional business, and announced John Andrews's appointment as Chief Financial Officer. 6 Chairman and Chief Executive Officer Pascal Gauthier described the initiative as deepening 7 Ledger's U.S. presence. Ledger published a corresponding announcement on its own website on 8 March 23, 2026.3 9 Publicly displayed professional profiles corroborate Ledger's U.S. operating presence. 10 LinkedIn listings reviewed on October 11, 2026 identify Sebastien Badault as SVP Enterprise at 11 Ledger and Andrew Chauvin-DeCaro as Enterprise Marketing Lead at Ledger, each listing the New 12 York City metropolitan area. They identify Dan Panagacos as Senior Technical Account Manager 13 at Ledger, listing New York, New York. The identified executive, marketing, and technical-account 14 functions are consistent with Ledger's announced expansion of its U.S. organization. 4 Ledger also identifies Portland among its office locations on its official company website. 5 15 16 The professional-profile materials identify Isaac Aranda as Wallet Operations Senior Associate at 17 Ledger, listing the Portland, Oregon metropolitan area; Steven Chiboucas as Quality Analyst at 18 Ledger, listing Portland; Jacob Thompson as User Feedback Project Manager at Ledger, listing 19 Beaverton, Oregon; and Quintin Boatwright as Operations Manager and Salesforce Architect at 20 21 22 (announcing a U.S. subsidiary and San Francisco offices). 3 Ledger, Ledger Appoints New Chief Financial Officer and Opens NYC Office to Scale U.S. Expansion, Business Wire (Mar. 20, 2026); see also Ledger, New CFO & Opening of NYC Office 24 to Scale U.S. Expansion (Mar. 23, 2026), https://www.ledger.com/blog-nyc-office-new-cfo (corresponding announcement). 25 4 LinkedIn, search-result listings for Sebastien Badault, Andrew Chauvin-DeCaro, and Dan 26 Panagacos (screenshots reviewed Oct. 11, 2026, and preserved in counsel’s source file). 23 27 5 Ledger, The Company, https://www.ledger.com/the-company (Our History) (last visited Oct. 11, 28 2026). 6 CLASS ACTION COMPLAINT Case No. 26-16867 Case 3:26-cv-12867 Document 1 Filed 10/30/26 Page 7 of 51 PageID #: 7 1 Ledger, listing Vancouver, Washington. Those identified wallet-operations, quality, feedback, and 2 business-systems functions further corroborate Ledger's U.S. operating presence. 6 3 Ledger has directed promotion of the product family at issue to San Francisco. In a 4 November 14, 2024 announcement, it identified San Francisco as a planned stop on a tour featuring 5 executive presentations and demonstrations of Ledger Flex and Ledger Stax. Ledger also built a 6 U.S. retail and activation network: its July 18, 2024 announcement described integration of 7 Ledger.com purchases with same-day pickup at Best Buy, in-store educational displays, and 8 guidance through Ledger's own activation materials. Those activities connect Ledger's consumer 9 marketing, authorized distribution, and manufacturer-prescribed setup into the security system it 10 supplies to its U.S. customers.7 11 Baylor acquired his first Ledger hardware wallet in 2017. Ledger supplied the hardware- 12 security functions used in that continuing California relationship. The relationship included the 13 manufacturer-controlled security system through which Ledger's servers perform its cryptographic 14 genuineness check through the official application. Baylor's 2026 Flex purchases continued his use 15 of that system: he returned to Ledger's own website, followed its official reseller directory, and 16 relied on Ledger's own authentication before entrusting his assets to the new devices. Plaintiff 17 challenges Ledger's own product-security and authentication conduct, not a failure to perform an 18 obligation created by an application-license agreement. 19 This Court has specific personal jurisdiction over Ledger under Federal Rule of Civil 20 Procedure 4(k)(1)(A) and California Code of Civil Procedure section 410.10. Baylor's claims arise 21 out of and relate to Ledger's sustained California business in the same hardware wallets, 22 manufacturer-supplied authentication, and security assurances challenged here. Ledger developed 23 24 25 6 LinkedIn, search-result listings for Isaac Aranda, Steven Chiboucas, Jacob Thompson, and Quintin Boatwright (screenshots reviewed Oct. 11, 2026, and preserved in counsel’s source file). 7 Ledger, Global Tour announcement (Nov. 14, 2024), https://www.ledger.com/ledgers-global26 tour-celebrating-10-years-of-secure-digital-ownership (last visited Oct. 11, 2026). See also Ledger, Ledger and Best Buy Launch Same-Day Pickup for Online Customers in the US (July 18, 27 2024), https://www.ledger.com/blog-ledger-and-best-buy-launch-same-day-pickup-for-online28 customers-in-the-us. 7 CLASS ACTION COMPLAINT Case No. 26-16867 Case 3:26-cv-12867 Document 1 Filed 10/30/26 Page 8 of 51 PageID #: 8 1 and served a California market for Flex devices and its official application, promoted Flex in this 2 District, and maintained the continuing hardware-security relationship with Baylor described above. 3 Baylor obtained the two Flex devices to continue using Ledger's security products and relied on 4 Ledger's official reseller designation and Genuine Check. His claims challenge Ledger's own design, 5 packaging, authentication, warnings, and distribution controls supplied through that continuing 6 consumer relationship. 7 The exercise of jurisdiction accords with fair play and substantial justice. Ledger deliberately 8 built a substantial California consumer business, publicly identified San Francisco as a headquarters 9 location, and promoted the Flex product family here. Its announced U.S. expansion and publicly 10 identified executive, marketing, technical-account, wallet-operations, quality, and customer11 feedback functions demonstrate a substantial U.S. operating presence. Ledger has described the 12 United States as its largest global market and committed additional capital and personnel to serving 13 it. California has a substantial interest in protecting its resident consumers and their separately 14 owned property from the alleged failure of security products marketed to them. Ledger possesses or 15 controls the product specifications, authentication records, distribution requirements, and 16 organizational evidence needed to adjudicate these claims. 17 Venue is proper under 28 U.S.C. § 1391(c)(3) (2024), because Ledger SAS is a defendant 18 not resident in the United States. Ledger's California consumer business, public San Francisco 19 headquarters representations, promotion of the product family at issue, and Baylor's longstanding 20 California relationship with Ledger connect this action to this District. 21 Divisional Assignment. Assignment to the San Francisco or Oakland Division is 22 appropriate under Civil Local Rules 3-2(c)–(d) and 3-5(b). Plaintiff is domiciled in San Mateo 23 County, California, and his longstanding use of Ledger products occurred in that county. The 24 California course of dealing and consumer relationship alleged here concerns a county served by 25 those Divisions. 26 Plaintiff's California consumer claims enforce nonwaivable rights and class remedies under 27 Civil Code sections 1751 and 1781 and California Business and Professions Code sections 17200 28 et seq. California has a fundamental interest in protecting its resident consumers from the challenged 8 CLASS ACTION COMPLAINT Case No. 26-16867 Case 3:26-cv-12867 Document 1 Filed 10/30/26 Page 9 of 51 PageID #: 9 1 practices of a manufacturer that deliberately serves this State. Plaintiff seeks enforcement of those 2 protections in his home forum. 3 4 IV. FACTUAL ALLEGATIONS A. Ledger supplies the product and the initial security determination 5 6 7 8 A hardware wallet generates and protects private keys used to authorize transactions involving cryptocurrency recorded on a blockchain. A recovery phrase permits those keys to be reconstructed on a compatible wallet. Anyone who obtains the necessary recovery information can gain control of the associated assets without possessing the owner's original device. 9 10 11 The cryptocurrency belongs to the user independently of the hardware wallet. Ledger did not sell Plaintiff the Bitcoin or Ether lost in this incident. The Flex was purchased to secure the credentials controlling that separately owned property. 12 13 14 15 16 17 18 19 20 Ledger supplies its hardware wallets together with an official setup process, security instructions, and companion application. The product family uses a manufacturer-controlled Genuine Check directed to the Secure Element. A successful result is presented during the prescribed setup process and informs the purchaser's decision whether to entrust cryptocurrency to the device. The relationship between that component authentication and the integrity of the complete recovery-information path is a common issue across models using the challenged process. Ledger's developer documentation lists the same microcontroller and Secure Element models for Flex and Stax and describes a separate microcontroller handling peripheral communications for the Secure Element.8 21 22 23 Ledger's current Flex setup guide places Genuine Check before generation of a new 24-word recovery phrase, consistent with Plaintiff's reported sequence. The guide bears a January 6, 2026 publication date and an October 9, 2026 update date. 9 24 25 8 27 9 Ledger, Hardware Architecture, Ledger Developer Portal (updated Sept. 23, 2026), https://developers.ledger.com/docs/device-app/explanation/ledger-os/hardware-architecture (Flex 26 and Stax component table; Secure Element proxy architecture). Ledger, Unboxing Your Ledger Flex: A Step-by-Step Guide to Secure Digital Ownership (Jan. 6, 28 2026; updated Oct. 9, 2026), https://www.ledger.com/academy/topics/ledgersolutions/unboxing9 CLASS ACTION COMPLAINT Case No. 26-16867 Case 3:26-cv-12867 1 Document 1 Filed 10/30/26 Page 10 of 51 PageID #: 10 The same guide describes the two strips of tape on a Flex box as serving packaging purposes 2 and directs purchasers to the security built into the device and the setup check. Ledger thus directs 3 the purchaser to rely on the product's security architecture and authentication to evaluate a newly 4 received Flex, while the supplied paper closures provide no device-linked assurance against opening 5 and resealing. 6 Ledger's published technical description explains that its server challenges the device's 7 Secure Element and verifies its cryptographic response and attestation. This process can establish 8 that the original Secure Element is genuine. It does not, by itself, establish that every part of the 9 device remains physically unmodified. 10 Ledger's Donjon threat-model documentation expressly recognizes that a successful 11 Genuine Check may coexist with an unauthorized physical spying implant if the original Secure 12 Element remains intact. It also distinguishes authenticity from verification of the device's physical 13 supply-chain history. An attacker who acquires the recovery information elsewhere in the device 14 can bypass the protection afforded by authenticating the original chip. 10 15 Ledger states in its current consumer buying guide that Genuine Check "cannot detect 16 unauthorized physical modifications to the hardware—such as spying implants—if the original 17 Secure Element remains intact." In its discussion of counterfeit devices and counterfeit companion 18 software, the same guide directs: "No visual inspection, no packaging check, no seller reputation 19 can substitute for running the Genuine Check yourself with authentic software." It also 20 acknowledges that "no global supply chain is entirely immune to highly sophisticated interception 21 or tampering attacks." These statements confirm Ledger's distinction between a necessary 22 component-authentication step and an assessment of the complete device. Baylor followed the 23 24 25 26 your-ledger-flex-a-step-by-step-guide-to-secure-digital-ownership (last visited Oct. 11, 2026). 27 10 Ledger Donjon, Genuineness - Threat Model, https://donjon.ledger.com/threat-model/device28 genuineness/ (last visited Oct. 11, 2026). 10 CLASS ACTION COMPLAINT Case No. 26-16867 Case 3:26-cv-12867 Document 1 Filed 10/30/26 Page 11 of 51 PageID #: 11 1 prescribed authentication, yet the setup did not tell him that a successful result left the alleged 2 physical interception path unresolved before he generated recovery information. 11 3 That distinction matters at the point of initial use. A purchaser deciding whether to generate 4 a recovery phrase on a newly acquired device needs to know whether the manufacturer's successful 5 result addresses an alteration capable of exposing that phrase. A result verifying only an authentic 6 component does not supply that answer if a separate implant can remain undetected. 7 Ledger controls the language of its successful result and the warnings and instructions 8 displayed during setup. It can explain material limits before the purchaser generates recovery 9 information or commits assets. Plaintiff alleges that the setup presented to him did not adequately 10 disclose the implant limitation at that decision point. The warning needed to accompany the 11 successful result on which Ledger directed him to act, before the device generated the secrets 12 controlling his assets. 13 A supply-chain compromise, as used here, is an unauthorized addition, substitution, or 14 alteration of hardware or device-resident code before delivery to the consumer that acquires 15 recovery information generated during legitimate setup or defeats the protection of that information 16 through the delivered device. The spyware may include an added circuit, substituted component, 17 modified display assembly, or code carried by an unauthorized component. The relevant chain 18 includes component sourcing, manufacturing and assembly, storage, shipment, distribution, retail 19 custody, and returns. Plaintiff alleges that Ledger's original protective design and verification system 20 permitted the compromise to expose recovery information while the original Secure Element 21 remained authentic. Identification of the precise insertion point requires the physical and distribution 22 evidence within Ledger's and the supply-chain participants' possession. 23 24 25 26 11 vineet.nair, Best Practices To Securely Buy Your Ledger Signer, Ledger (Mar. 6, 2026, updated Sept. 18, 2026), https://www.ledger.com/academy/topics/ledgersolutions/best-practices-to27 securely-buy-ledger-signer, under “Ledger Genuine Check: Explained” and “Counterfeit Devices” 28 (last visited Oct. 19, 2026; current publication, not proof of purchase-date exposure). 11 CLASS ACTION COMPLAINT Case No. 26-16867 Case 3:26-cv-12867 Document 1 Filed 10/30/26 Page 12 of 51 PageID #: 12 1 B. Ledger represents the integrity of products supplied through its official network 2 Ledger maintains an Official Reseller Network on its website, organized by location and 3 identifying businesses from which consumers may obtain Ledger products. The designation is 4 Ledger's own statement about the seller's place in its authorized distribution channel. 5 Ledger's own website describes its authorized-channel protections in Best Practices To 6 Securely Buy Your Ledger Signer. Under its discussion of supply-chain security, Ledger describes 7 its retail partners as “carefully selected Authorized Resellers” and says they are “commercially 8 incentivized” to obtain inventory directly from Ledger or its authorized distributors. It describes a 9 “vetted logistics pipeline” designed to mitigate third-party-wholesaler and grey-market sourcing 10 risks, and states that its distribution agreements prohibit partners from restocking and reselling 11 returned devices. It also maintains an official reseller registry and recommends its own store or listed 12 resellers to enhance authenticity and supply-chain integrity. 12 13 These are representations about protective practices applied to the goods and their 14 distribution, not merely permission to use Ledger's name. In the security context alleged here, 15 Plaintiff understood Ledger's official purchasing designation to identify a channel whose selection, 16 sourcing, and custody protections made the delivered product suitable for secure initialization. 17 Ledger's current guide corroborates that manufacturer-described function and informs the challenge 18 to its continuing practices; the purchasing representation Baylor actually encountered was Ledger's 19 designation of CryptoBilis in its own directory. Plaintiff's theory concerns the product-integrity 20 meaning conveyed in that context, independently of the later authentication of the Secure Element. 21 Ledger created and controls its official distribution system. It selects participating resellers, 22 maintains the registry and purchasing links, establishes sourcing incentives, and, according to its 23 own guide, contractually prohibits distribution partners from restocking and reselling returned 24 devices. Those measures address opportunities for substitution, unauthorized physical access, and 25 recirculation of compromised products. On information and belief, Ledger's relationship with 26 12 vineet.nair, Best Practices To Securely Buy Your Ledger Signer, Ledger (Mar. 6, 2026, updated 27 Sept. 18, 2026), https://www.ledger.com/academy/topics/ledgersolutions/best-practices-to28 securely-buy-ledger-signer, under “Ledger Supply Chain: How Ledger Distribution aligns with security industry standards” (last visited Oct. 19, 2026). 12 CLASS ACTION COMPLAINT Case No. 26-16867 Case 3:26-cv-12867 Document 1 Filed 10/30/26 Page 13 of 51 PageID #: 13 1 CryptoBilis included arrangements for distributing Ledger products. The governing requirements, 2 audits, sourcing records, and enforcement communications are within Ledger's and the distributor's 3 possession. 13 4 Ledger joined two consumer decisions into its prescribed security process: where to obtain 5 a device and whether to trust the delivered hardware. It designated the official seller and supplied 6 the successful initial authentication. Ledger knew purchasers would rely on both before generating 7 recovery information and committing assets. Reasonable performance of those retained functions 8 required security controls throughout the authorized channel, reliable inventory provenance, 9 protection against returned-product substitution, and revalidation when the ownership or operation 10 of an authorized seller materially changed. Ledger's written product-integrity assurances and its 11 designation of the seller are distinct from, and cumulative with, the device-specific authentication 12 supplied during setup. 13 In a public statement concerning CryptoBilis, Arravind Prabu stated that CryptoBilis had 14 been acquired by new ownership and that he and Vimalatheethan completed a handover of 15 operational, managerial, and administrative responsibilities in March 2026. He further stated that 16 suppliers had been notified of the acquisition and new management, while contractual restrictions 17 postponed a joint public announcement until mid-October 2026. The statement identifies Nicholas 18 Chang as the current operational contact. 14 19 That reported transition preceded both of Baylor's purchases. On information and belief, 20 Ledger received notice of the ownership or management change as a supplier to the authorized 21 distribution network. It nevertheless continued to present CryptoBilis as an official source when 22 Baylor selected it. On information and belief, Ledger failed reasonably to revalidate the operator, 23 custody of authorized inventory, access to stock, returns handling, and compliance with the security 24 requirements associated with its designation before continuing to direct consumers to that business. 25 13 Id., under “Ledger Supply Chain: How Ledger Distribution aligns with security industry 26 standards” (describing sourcing incentives and a contractual prohibition on resale of returns). 27 14 Arravind Prabu, Official Statement Regarding CryptoBilis, LinkedIn, numbered items 1, 2 & 4 28 (undated post reproduced in screenshot supplied by Plaintiff; copy on file with counsel). 13 CLASS ACTION COMPLAINT Case No. 26-16867 Case 3:26-cv-12867 1 Document 1 Filed 10/30/26 Page 14 of 51 PageID #: 14 A screenshot Baylor captured on October 11, 2026 shows CryptoBilis PH still displayed in 2 Ledger's Official Reseller Network with a purchasing link and no warning adjacent to that entry, 3 after Ledger's October 10 public acknowledgment of a hardware implant. By October 12, 4 CryptoBilis PH no longer appeared in the official Philippines reseller list. Ledger controlled that 5 consumer-facing designation and its revision. Changing the directory did not examine hardware 6 already delivered to consumers, identify all affected inventory, or resolve the common limitations 7 of Ledger's prescribed security check. 15 8 C. Baylor's history, purchases, and reliance 9 In 2017, Baylor acquired a Ledger hardware wallet in the United States and subsequently 10 used it from San Mateo County, California, for nearly a decade without experiencing a compromise 11 of the assets he secured with it. His longstanding experience with Ledger's products and security 12 system led him to return to Ledger when he needed another device. 13 In July 2026, Baylor visited ledger.com to obtain another Ledger device. Ledger's website 14 directed him to its Official Reseller Network, where he selected CryptoBilis and followed the 15 purchasing process. Ledger's official designation materially influenced his choice. Baylor remained 16 a California citizen and domiciliary throughout the purchases and the loss alleged here. He relied 17 on Ledger's designation in choosing the authorized channel to obtain an authentic, unmodified 18 Ledger product, rather than treating the directory as a list of unrelated sellers. His reliance on that 19 purchasing representation preceded and was distinct from his reliance on Genuine Check during 20 setup. 21 On July 13, 2026, Baylor purchased a new Ledger Flex in BTC Orange from CryptoBilis. 22 He selected the product through the official distribution channel Ledger identified. 23 On September 4, 2026, Baylor purchased a second new Ledger Flex, in Oxidate Green, from 24 the same Ledger-designated seller. 25 26 15 Ledger, Official Reseller Network, Philippines listing, https://shop.ledger.com/pages/resellers?continent=asia+%26+oceania&country=philippines 28 (Plaintiff’s Oct. 11, 2026 screenshot on file with counsel). 27 14 CLASS ACTION COMPLAINT Case No. 26-16867 Case 3:26-cv-12867 1 Document 1 Filed 10/30/26 Page 15 of 51 PageID #: 15 Baylor paid approximately $620.00 for the two transactions and received products sold as 2 new. The purchase records identify him as the purchaser. The security architecture, packaging, 3 official application, and Genuine Check supplied with both products came from Ledger. 4 Baylor received the Flex devices in retail packaging secured by two ordinary paper strips. 5 The closures did not have individualized serial identifiers, holographic features, or destructive void 6 adhesive. He observed no visible indication that the delivered products had been physically 7 compromised. 8 For setup, Baylor connected the devices to Ledger's official application and ran Genuine 9 Check. He received successful results identifying the devices as 'Genuine.' He relied on those results 10 before proceeding with generation of new recovery information and committing cryptocurrency to 11 accounts controlled by that information. 12 Baylor generated the recovery information natively on the devices. He did not use a recovery 13 phrase supplied by the reseller or written in advance by another person. He kept the recovery 14 information offline, did not digitize it, did not store it in a cloud service, and did not enter it into an 15 Internet-connected interface. 16 In the context of a new Flex obtained through Ledger's official reseller channel and the 17 prescribed setup sequence, Baylor understood the successful result as confirmation that the 18 particular device had satisfied Ledger's authentication for secure initialization and use. The 19 affirmation concerned the existing security condition of the product on which he was about to 20 generate the secrets controlling his assets. Ledger's earlier representation about the integrity of 21 products obtained through its official channel independently informed that understanding. The two 22 assurances addressed different stages of the same purchase and initial use. 23 Before Baylor proceeded, Ledger did not adequately tell him in that setup process that a 24 device could pass while containing a physical implant capable of obtaining newly generated 25 recovery information. He was not warned that his adherence to the official channel and a successful 26 result left that specific, concealed condition unresolved. Nor did the purchasing process adequately 27 explain that Ledger's official designation did not establish that the particular delivered device was 28 15 CLASS ACTION COMPLAINT Case No. 26-16867 Case 3:26-cv-12867 Document 1 Filed 10/30/26 Page 16 of 51 PageID #: 16 1 free from a concealed physical alteration capable of capturing newly generated recovery 2 information. 3 Baylor would not have generated recovery information on an affected device or placed his 4 assets under the control of that information had the relevant condition or limitation been adequately 5 disclosed before funding. He would have withheld the assets pending a secure alternative. Had 6 Ledger adequately disclosed that its designated purchasing channel left that condition unresolved, 7 Baylor would have withheld the purchase or obtained a securely verified alternative before 8 entrusting assets to the delivered hardware. 9 After setup, Baylor placed Bitcoin and Ether under the control of the new recovery 10 information. He owned the cryptocurrency transferred without authorization in the incident alleged 11 below. 12 D. The unauthorized transfers and alleged physical compromise 13 On or about October 9, 2026, cryptocurrency controlled through the affected recovery 14 information was transferred without Baylor's authorization. The unauthorized transactions depleted 15 10.66256803 BTC and 58.991906189521260209 ETH from his assets, inclusive of the associated 16 network transaction fees. 17 Baylor contemporaneously estimated his total loss at approximately $1.05 million. The 18 legally recoverable dollar value of the asset quantities alleged above will be established according 19 to proof under the applicable valuation measure. Plaintiff seeks a single recovery for each loss, 20 including any associated network fees. 21 Baylor promptly quarantined the affected hardware and retained purchase documents and 22 transaction records. He did not authorize the transfers, and he did not knowingly disclose his 23 recovery information to the recipients or approve transfers to them. 24 Before filing, Baylor reported the unauthorized losses to Ledger. On October 12, 2026, 25 Ledger Support responded in case 00285187 and instructed him to move any remaining funds 26 associated with his current recovery phrase to a new recovery phrase without using the current 27 device. To investigate, Ledger requested the serial identifiers on the box, on the back of the device, 28 and in the firmware, where available; the purchase and delivery records; packaging photographs; 16 CLASS ACTION COMPLAINT Case No. 26-16867 Case 3:26-cv-12867 Document 1 Filed 10/30/26 Page 17 of 51 PageID #: 17 1 setup history; firmware information; and application logs. That response identifies the product2 identity, provenance, and configuration information Ledger itself considers relevant to investigating 3 the reported compromise. 4 On information and belief, one or more of the Flex devices were physically altered before 5 delivery to Baylor, in a manner that permitted capture of recovery information generated during 6 legitimate setup while preserving the authentic Secure Element and its ability to pass Genuine 7 Check. Plaintiff alleges that this compromise enabled the unauthorized transfers. 8 The grounds for that inference include Baylor's native generation and offline handling of 9 recovery information; the successful manufacturer checks; the subsequent unauthorized depletion 10 of assets; and the documented physical implant attacks on Ledger hardware that can leave 11 component authentication intact. On information and belief, an unauthorized component acquired 12 recovery information through the device's display or associated circuitry before the resulting theft. 13 The product's original susceptibility to that interference and Ledger's misleading security 14 determination operated together. The precise implant configuration and point of insertion can be 15 established through examination of the preserved hardware and the manufacturing, attestation, 16 batch, custody, and distribution records. 17 The original design failed to make the recovery-information path sufficiently resistant to 18 foreseeable interference or to prevent sensitive initialization after that path had been compromised. 19 The enclosure, component protections, packaging, authentication scope, and user-facing security 20 determination operated together. Their inadequacy allowed the alleged malicious addition to defeat 21 the product's security purpose without an effective warning to Baylor before he exposed his assets. 22 On information and belief, the absence of durable, individualized indications of interference 23 with the packaging and enclosure facilitated opening, alteration, and resealing without a warning 24 visible to Baylor. The ordinary paper closures neither authenticated the package's relationship to the 25 enclosed device nor supplied a persistent indication of earlier access. Those deficiencies left Baylor 26 dependent on the device and Ledger's check to identify concealed interference. 27 Acquisition of the recovery information and theft of the associated assets were foreseeable 28 consequences of this alleged condition. A malicious effort to intercept a device or acquire its 17 CLASS ACTION COMPLAINT Case No. 26-16867 Case 3:26-cv-12867 Document 1 Filed 10/30/26 Page 18 of 51 PageID #: 18 1 recovery information is a hazard for which purchasers obtain a security product. Ledger knew that 2 the value of cryptocurrency controlled by a device could substantially exceed the device's purchase 3 price. 4 On information and belief, effective physical barriers or a verifiable indication of prior 5 opening would have prevented or exposed the interference before use; a tamper response that 6 blocked sensitive initialization would have prevented the compromised device from revealing new 7 recovery information; and an adequate warning would have caused Baylor to withhold his assets. 8 Each protection addressed a stage of the sequence that led from concealed pre-delivery alteration to 9 unauthorized transfer. 10 E. Knowledge of the risk and common design choices 11 Ledger designed the authentication and knew which components and conditions it did and 12 did not examine. On information and belief, before Plaintiff's purchases, Ledger knew that 13 authentic-component verification did not itself exclude an additional physical implant, and that users 14 could mistake a successful result for resolution of that risk unless the distinction was adequately 15 explained. 16 Ledger had publicly identified supply-chain substitution and resealing risks years earlier. In 17 March 2019, its Donjon team described opening a competitor's package, altering a device, and 18 resealing the package despite a security sticker. Ledger also described the risk that attackers could 19 return altered devices into a manufacturer's sales channel. Ledger's own analysis thus recognized 20 that physical access, packaging, returns handling, and device design had to be evaluated together. 16 21 Physical implants in Ledger hardware had been examined before Baylor's purchases. 22 Security researcher Joe Grand published an analysis of an implant in a Ledger Nano X, with 23 presentation materials revised May 29, 2026. The work documents an unauthorized physical 24 25 26 16 Ledger, Our Shared Security: Responsibly Disclosing Competitor Vulnerabilities (Mar. 11, 2019), https://www.ledger.com/our-shared-security-responsibly-disclosing-competitor28 vulnerabilities. 27 18 CLASS ACTION COMPLAINT Case No. 26-16867 Case 3:26-cv-12867 Document 1 Filed 10/30/26 Page 19 of 51 PageID #: 19 1 addition to Ledger hardware and the recovery-information interception risk posed by a compromised 2 device.17 3 On October 10, 2026, Tai Zen publicly stated that he had sent multiple tampered Ledger 4 devices to Ledger's Donjon security team in January 2026. Mark Karpelès quoted that statement 5 publicly on October 11, 2026. The reported submission preceded Baylor's purchases and supports 6 Plaintiff's allegation, on information and belief, that Ledger had received specific notice of physical 7 tampering in its distribution chain. 18 8 The reported notice was not limited to general research. On October 16, 2026, security 9 researcher Joe Grand told Cointelegraph that he alerted Ledger on March 4, 2026 to a malicious 10 implant in a Nano X purchased through Lazada Thailand in August 2025. According to Grand, 11 Ledger acknowledged the findings and said it was investigating internally; he criticized its failure 12 to warn customers proactively. Karpelès separately reported awareness of at least two contacts 13 beginning in December 2025. The article did not establish the marketplace seller's authorization 14 when that device was purchased. The significance here is notice to Ledger of an actual implant 15 mechanism before both of Baylor's purchases, not an allegation that Grand's specimen came from 16 an authorized seller.19 17 On October 10, 2026, Ledger publicly confirmed that one impacted user's device contained 18 an unauthorized hardware implant and stated that it was contacting affected users as part of its 19 20 21 17 Joe Grand, Reverse Engineering a Ledger Nano X Hardware Implant, Grand Idea Studio, presentation slides 72–73, 77 (rev. May 29, 2026), 22 https://grandideastudio.com/portfolio/security/ledger-hardware-implant/ (presentation linked on 23 the project page). 24 18 26 19 Tai Zen (@HeyTaiZen), X (Oct. 10, 2026), quoted in Mark Karpelès (@MagicalTux), X (Oct. 11, 2026), https://x.com/MagicalTux/status/2109272516544041066 (reproduced post stating that 25 devices were sent in January 2026; screenshot on file with counsel). Helen Partz, Ledger’s Early Implant Warnings Deserved More Action, Karpelès Says, Cointelegraph (Oct. 16, 2026), https://ct.com/news/ledger-early-implant-warnings-mark-karpeles 27 (reporting interviews with Grand and Karpelès; see also “Marketplace Listings Expose Reseller 28 Verification Gaps”). 19 CLASS ACTION COMPLAINT Case No. 26-16867 Case 3:26-cv-12867 Document 1 Filed 10/30/26 Page 20 of 51 PageID #: 20 1 investigation. That acknowledgment corroborates the occurrence of physical implants in delivered 2 Ledger hardware.20 3 On October 11, 2026, Ledger directed CryptoBilis purchasers not to initialize unused devices 4 and advised users who had already completed setup to move to a new seed on a device obtained 5 from Ledger. It reminded its authorized resellers and distributors to source products only through 6 authorized channels and never restock returned devices, and announced review of reseller controls 7 and hardware protections. Ledger described the confirmed cases in its then-current investigation of 8 the October 9 incident as involving CryptoBilis. That account of the cases then confirmed did not 9 identify the manufacturing, custody, and examination evidence needed to resolve the separate 10 implant reports described below or the common limitations of Ledger's authentication. Plaintiff 11 alleges that Ledger's original security failures and the necessary corrective relief extend beyond that 12 reseller.21 13 In an October 2026 field report, Tibane Labs described two implanted Ledger Nano X 14 specimens obtained in September 2026: one through Yahoo! Auctions in Japan, and one from a 15 China-based seller on Amazon Japan, shipped from Malaysia. Tibane reported added circuitry 16 connected to the display path and cellular communication components. In the newer specimen, 17 black-coated circuitry was concealed beneath the OLED display while the original battery remained 18 in place.22 19 On October 10, 2026, Mark Karpelès published comparative photographs of Nano X implant 20 configurations and identified connections to display-bus signals at the device's factory test pads. He 21 described the newer black configuration as using fewer tapped signals than an earlier version and 22 23 20 Ledger Support (@Ledger_Support), X (Oct. 10, 2026), 24 https://x.com/Ledger_Support/status/2108968264055345381 (statement concerning an implant in one affected user’s device). 25 21 Ledger (@Ledger), X (Oct. 11, 2026), https://x.com/Ledger/status/2109331538072494364 (7226 hour update; instructions to CryptoBilis customers and authorized distribution partners). 27 22 Tibane Labs, Ledger Nano X: The Spy Implant (Oct. 2026), 28 https://www.tibane.net/research/ledger-nano-x-implant. 20 CLASS ACTION COMPLAINT Case No. 26-16867 Case 3:26-cv-12867 Document 1 Filed 10/30/26 Page 21 of 51 PageID #: 21 1 inferred that this simplified installation. These reported physical connections further support an 2 interception path outside the genuine Secure Element. 23 3 On October 11, 2026, a user posting as @0xJohannes_ reported an apparent implant in a 4 Ledger Nano X purchased in person through a European retailer and identified MediaMarkt in a 5 follow-up. Public posts by Coin Academy, Crypto Banter, and @RatPoisonaut reproduced the report 6 and the same photograph of the opened device. 24 Later that day, the same account published a closer 7 photograph showing the apparent added assembly and antenna lead. Mark Karpelès publicly 8 identified the first photographed assembly as another spy implant resembling an earlier iteration of 9 the implant he was examining. The report and that technical assessment identify an additional 10 alleged compromised Ledger product obtained through a different retail channel. 25 11 On October 12, 2026, Johannes reported finding an apparent spyware implant in a second 12 Ledger device purchased that day at a different MediaMarkt location. He published photographs 13 and linked a video he described as recording the unboxing, and reported the same additional wiring 14 and LTE module in the newly purchased device. He further reported that a MediaMarkt employee 15 told him this device was not a customer return and that returned Ledger devices were sent back to 16 the manufacturer rather than resold. He identified store inventory records as showing Aqipa GmbH 17 as the source of the stock.26 18 19 23 21 24 Mark Karpelès (@MagicalTux), X (Oct. 10, 2026), https://x.com/MagicalTux/status/2109031679528702257 (comparative photographs and discussion 20 of display signals and test-pad connections). Johannes (@0xJohannes_), X (Oct. 11, 2026), https://x.com/0xJohannes_/status/2109240472933671125; Johannes (@0xJohannes_), X (Oct. 11, 22 2026), https://x.com/0xJohannes_/status/2109285908079915305 (follow-up identifying 23 MediaMarkt; preserved reproductions on file with counsel). 25 Johannes (@0xJohannes_), X, photograph 2 (Oct. 11, 2026), https://x.com/0xJohannes_/status/2109369736391794711/photo/2; see also Mark Karpelès 25 (@MagicalTux), X (Oct. 11, 2026), https://x.com/MagicalTux/status/2109249759508869184 (assessment of the earlier European-device photograph). 26 26 Johannes (@0xJohannes_), X (Oct. 12, 2026), 27 https://x.com/0xJohannes_/status/2109634513957527974 Johannes (@0xJohannes_), X (Oct. 12, 28 2026), https://x.com/0xJohannes_/status/2109634517296148568 (accompanying video post; 24 21 CLASS ACTION COMPLAINT Case No. 26-16867 Case 3:26-cv-12867 1 Document 1 Filed 10/30/26 Page 22 of 51 PageID #: 22 Aqipa independently announced its Ledger distribution partnership in Germany and Austria 2 in August 2023, identifying the Nano X among the products. Ledger's own German consumer guide 3 identifies MediaMarkt as an authorized retail partner. The successive reports therefore implicate 4 another authorized retail channel and a separately identified upstream distributor. They support 5 tracing inventory through the distribution chain and comparing production lots, device 6 configurations, and access to stock across stores, rather than confining the inquiry to a single retail 7 seller.27 8 On October 13, 2026, Ledger announced that MediaMarktSaturn had suspended sales of 9 Ledger devices in stores and online in coordination with Ledger following a German customer's 10 report of a hardware implant. A MediaMarktSaturn spokesperson separately confirmed removal of 11 Ledger products from the retailer's lineup in all countries as a precaution. Ledger stated that no fund 12 loss had been reported in that German case and that it had no indication its infrastructure, systems, 13 or services were compromised. The sales suspension extended beyond CryptoBilis; it did not itself 14 inspect devices already delivered to consumers. 28 15 On October 11, 2026, the account @wentrre posted three internal photographs of a device it 16 identified as its Ledger Stax and asked Ledger whether the device had a problem. The photographs 17 show a Ledger-marked board with an apparent additional assembly, including a component marked 18 Nordic Semiconductor nRF9151 and a cable leading toward the rear cover. Bitcoin News 19 reproduced the post that day and characterized the assembly as suspected unauthorized hardware. 29 20 21 purchase, inventory provenance, and retailer statements are attributed to the reporting user). 27 Aqipa, Aqipa started mit LEDGER in neuer Kategorie der Krypto Wallets (Aug. 2, 2023), https://inside.aqipa.com/de/news/posts/aqipa-started-mit-ledger-in-neuer-kategorie-der-krypto23 wallets (article dateline Aug. 1, 2023); Ledger, Crypto in Germany: The Ultimate Guide, https://www.ledger.com/academy/topics/country-guides/crypto-in-germany-the-ultimate-guide 24 (current text identifying authorized retailers). 22 25 28 28 29 Ledger (@Ledger), X (Oct. 13, 2026), https://x.com/Ledger/status/2109984923343782374, quoted in Helen Partz, MediaMarktSaturn Pulls Ledger Products Amid Tampering Reports (Oct. 26 13, 2026), https://cointelegraph.com/news/mediamarkt-pulls-ledger-wallet-security-incident 27 (quoting Ledger’s statement and a MediaMarktSaturn spokesperson). @wentrre, X, photographs 1–3 (Oct. 11, 2026), 22 CLASS ACTION COMPLAINT Case No. 26-16867 Case 3:26-cv-12867 Document 1 Filed 10/30/26 Page 23 of 51 PageID #: 23 1 Mark Karpelès also linked the original report and identified the pictured Stax as apparently 2 containing an implant. Nordic Semiconductor identifies the nRF9151 as incorporating an LTE3 M/NB-IoT cellular modem.30 The suspected assembly's function and the circumstances of that 4 device's delivery remain unverified. 5 On October 13, 2026, Mark Karpelès reported finding a spy implant in a Ledger Flex 6 purchased at Singapore Airport. His post identified Ben Yorke as the owner, stated that Yorke 7 noticed suspicious marks and withheld the device from use, and linked an inspection video. This 8 reported finding concerns the same product model purchased by Baylor and a different retail 9 channel. It supports tracing Flex inventory and comparing the relevant product configurations across 10 sellers and upstream suppliers rather than limiting the inquiry to the CryptoBilis transactions. 31 11 The Nano X examinations, the reported Flex implant from a Singapore Airport purchase, the 12 apparent Stax assembly, and the repeated European retail reports support a manufacturer-wide 13 inquiry into susceptibility to pre-delivery alteration and the limits of Ledger's security check. The 14 reported Flex finding supplies same-model evidence relevant to Baylor's claim without establishing 15 that every specimen has an identical alteration or that all were compromised at the same point in the 16 supply chain. The reported involvement of new inventory from an identified distributor makes the 17 sourcing, lot, and custody records upstream of the retail store material to determining the reach of 18 19 https://x.com/wentrre/status/2109339646102778306; Bitcoin News (@BitcoinNewsCom), X (Oct. 11, 2026), https://x.com/BitcoinNewsCom/status/2109379275325309107 (reproducing the same 20 owner’s photographs, not a separate incident). 21 30 Mark Karpelès (@MagicalTux), X (Oct. 11, 2026), https://x.com/MagicalTux/status/2109370197710868656 (commenting on the @wentrre 22 photographs); Nordic Semiconductor, nRF9151, https://www.nordicsemi.com/Products/nRF9151 23 (component documentation; modem capability does not establish operation of the pictured assembly); see also Ariel Givner (@GivnerAriel), X (Oct. 11, 2026), 24 https://x.com/GivnerAriel/status/2109418373377638688 (commentary on the same reported specimen). 25 31 Mark Karpelès (@MagicalTux), X (Oct. 13, 2026), 26 https://x.com/MagicalTux/status/2109916873689280900, reproduced in Kim Zetter, Who Is Planting Backdoors in Ledger Crypto Wallets? (Oct. 13, 2026), https://www.zetter27 zeroday.com/who-is-planting-backdoors-in-ledger-crypto-wallets/ (attributed account of the 28 Singapore-airport Flex; not a verified report of asset theft from that specimen). 23 CLASS ACTION COMPLAINT Case No. 26-16867 Case 3:26-cv-12867 Document 1 Filed 10/30/26 Page 24 of 51 PageID #: 24 1 the compromise. An implant that captures display information and has its own cellular connection 2 can expose recovery information even when the owner keeps the phrase off networked computers. 3 Ledger applies the Secure Element authentication principle across its product family, and its own 4 technical documentation identifies common core components in Flex and Stax. Its original design 5 records, incident submissions, product examinations, manufacturing and shipment records, and 6 reseller controls provide common evidence of which devices share the challenged condition. The 7 scope of protective relief should follow that evidence, rather than the identity of the last seller or the 8 first incident Ledger publicly confirmed. 9 Ledger's knowledge of the authentication it designed, its earlier supply-chain research, the 10 published implant analysis, and the reported submission of tampered devices and acknowledgment 11 of Grand's March 4, 2026 disclosure establish a factual basis for its pre-purchase knowledge of the 12 risk. On information and belief, Ledger knew before Baylor's purchases that its successful check 13 could leave a concealed interception path unresolved, yet failed to implement adequate physical 14 protection, tamper response, packaging controls, and point-of-use disclosure. The resulting exposure 15 was the foreseeable failure of the security function for which consumers bought the product. 16 On October 15, 2026, Ledger published a further response. It reported reverse-engineering 17 the implant, examining spot-purchased and warehouse samples, finding those sampled stock units 18 clean, and asking authorized resellers and distributors to suspend sales in Southeast Asia and Hong 19 Kong. It denied a flaw in its chip, operating system, or servers and characterized the event as a 20 localized distribution attack. Ledger also announced immediate instructions to keep products off 21 shelves and displays, hold stock in backrooms until sale, prohibit all resale of returns, and escalate 22 unusual-product reports. It stated that additional product-level measures were being developed. 23 These measures addressed selected inventory and future handling; the announcement did not 24 establish a comprehensive inspection or verified-replacement program for products already held by 25 Class members.32 26 32 The Ledger Team, Ledger’s Response to the Hardware Implant Attack, Ledger (Oct. 15, 2026), https://www.ledger.com/blog-response-hardware-implant-attack, under “What Happened,” “How 28 We Responded,” and “What We Are Doing Differently.” 27 24 CLASS ACTION COMPLAINT Case No. 26-16867 Case 3:26-cv-12867 1 Document 1 Filed 10/30/26 Page 25 of 51 PageID #: 25 The same day, Ledger's Chief Technology Officer, Charles Guillemet, expressly 2 acknowledged that “an attestation cannot catch an implant spying on the screen.” He stated that 3 “over the past few months” Ledger had developed an active shield around the new Ledger Atom's 4 secure zone to detect pre-delivery touching, opening, probing, or modification and trigger a Secure 5 Element response. This account places protective engineering before the October 9 losses and 6 confirms Ledger's awareness that authenticating the chip does not resolve screen interception. The 7 precise development milestones, test results, and applicability to the earlier devices are within 8 Ledger's records.33 9 Ledger's Atom whitepaper describes a protected enclosure for the Secure Element, graphics 10 coprocessor, and display-switch circuitry; display-signal tracks buried within the circuit board; and 11 a second opening-detection perimeter resettable only through a controlled Ledger-supervised 12 process. It separately describes isolating the sensitive screen and touch input from compromised 13 Android software. A Ledger spokesperson told The Block that the announced tamper sensors would 14 have an independent battery and stated: “The Core Protection feature will explicitly block the screen 15 reader implants from this weekend’s incident.” These are Ledger's announced design and 16 performance claims, not results of an independent examination of Baylor's Flex devices. 34 17 The launch also addressed packaging and distribution. Solana Mobile's October 15 18 partnership announcement described planned tamper-resistant and tamper-evident measures 19 extending from Atom's packaging to the device and stated that Atom would be sold directly through 20 21 22 33 Charles Guillemet, The Security Architecture of Ledger Atom™, Ledger (Oct. 15, 2026), https://www.ledger.com/blog-ledger-atom-security-architecture, under “Privacy & Tamper 24 Protection Are Built Into the Hardware.” 23 25 34 Ledger, Ledger Atom™—Whitepaper (Oct. 15, 2026), https://www.ledger.com/ledger-atomwhitepaper, under “Secure Screen,” subsections “Physical Tamper Protection” and “Display and 26 Touch Isolation”; James Hunt, Ledger Unveils Atom Android Device with Solana Mobile Integration and New Tamper Protections Amid Investigation into Modified Wallets, The Block 27 (Oct. 15, 2026), https://www.theblock.co/news/business/2026-10-15-ledger-atom-solana-mobile28 418644, under “Protections Against Physical Tampering” (quoting Ledger’s spokesperson). 25 CLASS ACTION COMPLAINT Case No. 26-16867 Case 3:26-cv-12867 Document 1 Filed 10/30/26 Page 26 of 51 PageID #: 26 1 Ledger's official site. These statements identify physical custody, enclosure integrity, and packaging 2 as distinct protections in addition to Secure Element authentication. 35 3 Ledger marketed Atom as a smartphone-shaped, Android-based security device; its product 4 FAQ specifies that it is a data-only device, not a conventional cellular telephone. The October 15 5 announcement solicited a $100 refundable reservation toward an $849 reserve price and projected 6 delivery in 2027, while disclosing that Atom remained in development and its design, features, price, 7 and delivery estimate could change. The same announcement encouraged people who did not 8 already own a Ledger to buy one immediately. A reservation for a future product was not an 9 immediately available correction of hardware already sold. 36 10 CoinDesk also reported Ledger's statement that it had no plans for a trade-in program for 11 existing customers affected by the incident, although future upgrade promotions were not excluded. 12 That statement concerns trade-ins; it is not an allegation that Ledger denied every form of support. 13 The distinction remains material to the relief sought: announcing additional security for a future 14 premium product, restricting retail handling, and offering case-specific support do not establish the 15 integrity of every Covered Device already held by Class members or provide the court-supervised 16 corrective program alleged below.37 17 18 19 35 Solana Mobile, Solana Mobile Announces Ledger as Its First Hardware Expansion Partner, PR 20 Newswire (Oct. 15, 2026), https://www.prnewswire.com/news-releases/solana-mobile-announcesledger-as-its-first-hardware-expansion-partner-302909677.html (announcing packaging-to-device 21 tamper protections and direct-site distribution). 22 36 Pascal Gauthier, Ledger Atom™: The Device Built to Protect Everything You Value, Ledger (Oct. 15, 2026), https://www.ledger.com/blog-introducing-ledger-atom, under “Ledger Atom – 23 Built to Protect Everything You Value” and the accompanying reservation disclaimer; Ledger, 24 Ledger Atom™, https://shop.ledger.com/pages/ledger-atom, FAQ “Can Ledger Atom™ make phone calls? Is this a phone?” (last visited Oct. 17, 2026). 25 37 Jamie Crawley & AI Boost, Under Pressure, Ledger Unveils Plan to Turn Its Crypto Hardware 26 Wallet into a Smartphone, CoinDesk (Oct. 15, 2026), https://www.coindesk.com/tech/2026/10/15/under-pressure-ledger-unveils-plan-to-turn-its-crypto27 hardware-wallet-into-a-smartphone (reporting Ledger’s statements about trade-ins and possible 28 future upgrade promotions). 26 CLASS ACTION COMPLAINT Case No. 26-16867 Case 3:26-cv-12867 Document 1 Filed 10/30/26 Page 27 of 51 PageID #: 27 1 F. Available designs that prevent sensitive operation after tampering 2 On information and belief, feasible protective designs available before Baylor's purchases 3 could have prevented, detected, or exposed the alleged compromise while preserving the product's 4 intended function. They included protection of the complete path by which recovery information 5 reaches the display, physical barriers to unauthorized component access, persistent tamper detection, 6 and refusal to generate or expose secrets after an integrity failure. 7 A secure design must protect confidential recovery information as it is rendered into display 8 data and communicated through the circuitry necessary to present it to the user. Protecting the 9 Secure Element alone does not protect recovery information that an unauthorized component can 10 acquire elsewhere. Reasonable alternatives included protected interconnections, authenticated 11 component relationships where appropriate, tamper-resistant enclosure or encapsulation of the 12 sensitive path, and testing of the complete assembled device against interception during normal 13 setup. On information and belief, additional feasible protections included encrypting sensitive 14 display communications and authenticating receiving components, with protection continuing 15 through the receiving component, and eliminating, isolating, or physically shielding unnecessary 16 accessible test points. 17 An effective tamper response would prevent a compromised device from generating, 18 displaying, or using recovery information until its secure condition was restored through an 19 appropriate manufacturer-controlled process or the device was replaced. A persistent tamper state 20 could preserve evidence of unauthorized opening or interference during shipment and storage, 21 including while the device lacked external power, and prevent ordinary reset or firmware 22 reinstallation from clearing that condition. The response must operate before the first sensitive 23 initialization of an altered new device, when the user's recovery information has not yet been 24 generated. 25 Recognized cryptographic-module security frameworks describe progressively stronger 26 physical protections, including tamper evidence, barriers to access, detection, and response. The 27 FIPS 140-3 framework has four security levels; its strongest physical-security category includes an 28 enclosure or protective envelope designed to detect and respond to physical penetration. Those 27 CLASS ACTION COMPLAINT Case No. 26-16867 Case 3:26-cv-12867 Document 1 Filed 10/30/26 Page 28 of 51 PageID #: 28 1 approaches provide engineering benchmarks for device-appropriate protection of the complete 2 secret-handling path, including prevention of sensitive operation when integrity is lost. 38 3 A June 2025 security policy for Senetas CN Series network encryptors describes a tamper 4 circuit that remains active without external power, destroys a protected master key when triggered, 5 records the condition upon restart, and blocks data output in an unactivated state. That existing 6 design illustrates mechanisms for preserving a tamper response across power states and withholding 7 sensitive operation pending secure reconfiguration; adaptation to a consumer hardware wallet 8 requires consideration of its dimensions, power requirements, cost, and intended use. 39 9 Protective packaging and enclosure designs were also in commercial use in the hardware- 10 wallet market before Baylor's purchases. In December 2018, Coinkite described uniquely serialized 11 security bags whose identifiers were permanently recorded in the enclosed wallet, together with a 12 welded transparent enclosure intended to make added hardware more apparent. These 13 complementary measures addressed package substitution, prior access, and concealed additions at 14 different stages of delivery and use.40 15 G. Packaging and distribution controls that reveal interference before use 16 Reasonably secure packaging required more than a closure that could be replaced without 17 an individualized indication of interference. Feasible protective layers included destructible seals or 18 enclosures covering access points, unique package identifiers linked to the particular device, and a 19 manufacturer-provided means for the consumer to verify that association before generating recovery 20 38 Nat’l Inst. of Standards & Tech., FIPS PUB 140-3, Security Requirements for Cryptographic 21 Modules § 3 (Mar. 22, 2019), https://csrc.nist.gov/pubs/fips/140-3/final; Nat’l Inst. of Standards & Tech., Implementation Guidance for FIPS 140-3, 22 https://csrc.nist.gov/csrc/media/Projects/cryptographic-module-validation23 program/documents/fips%20140-3/FIPS%20140-3%20IG.pdf (mutable document; retrieved edition retained in counsel’s source file) (physical-security engineering benchmarks, not a 24 certification requirement alleged to bind Ledger). 25 39 28 40 Senetas Corp. Ltd., CN Series Non-Proprietary Security Policy § 9.3.3, at 64 (ver. 1.02, June 2025), https://csrc.nist.gov/CSRC/media/projects/cryptographic-module-validation26 program/documents/security-policies/140sp4869.pdf (tamper-response operation; printed page 27 number, not PDF viewer count). Coinkite, Some Other Wallets.fail (Dec. 28, 2018), https://blog.coinkite.com/other-wallet-fail/. 28 CLASS ACTION COMPLAINT Case No. 26-16867 Case 3:26-cv-12867 Document 1 Filed 10/30/26 Page 29 of 51 PageID #: 29 1 information. Combining those features with protected hardware and a persistent tamper response 2 would reduce the ability to substitute, open, alter, and reseal a product without detection. 3 The package and device identifiers could be recorded at manufacture and checked at 4 authorized transfers and first activation, with inconsistent identifiers, duplicate activation, or an 5 unexplained chain-of-custody exception triggering quarantine and verification. Packaging controls 6 also included secure custody of unused seals and containers, separation of returned products from 7 new inventory, inspection of compromised shipments, and investigation of material changes in the 8 businesses handling authorized stock. Those protections must operate at manufacturer-to-distributor 9 and distributor-to-retailer transfers as well as at the final sale; prohibiting retail returns alone does 10 not verify newly supplied inventory. 11 These measures perform complementary functions. Physical barriers impede access; tamper 12 evidence reveals interference; detection and response prevent sensitive operation; and traceability 13 helps identify substituted or recirculated products. On information and belief, Ledger's use of 14 ordinary closures for Baylor's devices, combined with the alleged hardware and authentication 15 limitations, omitted protections that would have interrupted the compromise before his recovery 16 information was exposed. 17 Reasonable testing included attempting to open, alter, and reseal an authentic device and its 18 packaging; determining whether an added component could acquire recovery information during 19 prescribed setup; testing whether Genuine Check still succeeded; and determining whether detected 20 interference prevented the device from performing sensitive operations. The tests needed to cover 21 the assembled product, relevant hardware revisions, packaging configurations, new inventory 22 moving through authorized distributors, and foreseeable returns or substitution pathways. Testing 23 also needed to examine concealed additions beneath display assemblies, access through exposed 24 test points, and modifications that preserve the original battery and outward appearance. 25 Ledger also controlled the communication at the last practical point before exposure. An 26 adequate warning would have explained that the successful check authenticated a component 27 without excluding a concealed implant elsewhere, that apparently intact packaging did not resolve 28 that limitation, and that proceeding could expose newly generated recovery information. It would 29 CLASS ACTION COMPLAINT Case No. 26-16867 Case 3:26-cv-12867 Document 1 Filed 10/30/26 Page 30 of 51 PageID #: 30 1 have directed the purchaser not to rely on Genuine Check alone while whole-device integrity 2 remained unverified, and to obtain appropriate verification, a verified replacement, or a secure 3 alternative before generating recovery information or funding the affected accounts. Baylor would 4 have heeded that warning. 5 H. Continuing injury and a protective recall and inspection program 6 Baylor presently wants to continue using Ledger hardware wallets and to use or obtain a 7 Ledger device whose physical security Ledger can professionally verify or correct. He wants the 8 security characteristics represented for the products he purchased. His decision to quarantine the 9 affected devices does not end that desire. He cannot determine from a successful Genuine Check, 10 apparently intact packaging, or the outward appearance of a device whether its recovery-information 11 path is free from the concealed interference alleged here. 12 Baylor's knowledge of the earlier compromise does not tell him whether his retained devices 13 can be reliably corrected or whether newly obtained Ledger hardware is free from the same 14 concealed condition. He presently wants to use Ledger hardware with the represented protective 15 characteristics, but cannot make that decision reliably while Ledger's official authentication leaves 16 whole-device physical integrity unresolved. A payment for the completed loss would not require 17 accurate future security communications, provide reliable manufacturer-supported verification, or 18 correct the distribution and initialization practices that created that uncertainty. Those prospective 19 corrections would permit him to evaluate and use Ledger hardware on an informed basis. The same 20 unresolved question affects his ability to rely on Ledger's official seller designation and written 21 assurances when selecting replacement hardware. Correcting the authentication alone would not 22 correct misleading representations about the source and condition of newly delivered products. 23 Ledger's current buying guidance directs confident consumers toward physical inspection 24 while cautioning them not to damage the device. Its linked hardware-integrity guidance specifically 25 warns that Flex is not designed for routine opening, says internal inspection should ideally be 26 performed by qualified technical personnel, and strongly discourages owner disassembly because it 27 can cause irreversible visible damage and make reassembly highly difficult. Consumers confronting 28 an undetected implant therefore face a software check that cannot resolve the condition and a 30 CLASS ACTION COMPLAINT Case No. 26-16867 Case 3:26-cv-12867 Document 1 Filed 10/30/26 Page 31 of 51 PageID #: 31 1 physical examination that Ledger warns can damage the product. A reliable remedy requires 2 qualified inspection or verified replacement without requiring consumers to open their own devices, 3 bear the resulting damage, or surrender warranty or statutory rights. 41 4 As of October 12, 2026, Ledger's publicly available consumer guide for Germany continued 5 to promote Flex and Stax and state that "a Ledger wallet has never been hacked." That broad 6 assurance does not explain the distinction between an uncompromised Secure Element and an 7 assembled device carrying a concealed physical implant. The continuing presentation reinforces the 8 need for accurate, coordinated security disclosures and reliable verification before sensitive use. 42 9 Reliable inspection must address the assembled device and every material path through 10 which recovery information can be displayed, captured, or transmitted. Repeating Genuine Check 11 does not exclude an implant outside the authenticated Secure Element. A comparison to a generic 12 photograph cannot by itself establish the absence of circuitry concealed beneath a display assembly 13 or elsewhere within the device. Ledger controls the original product specifications, authentication 14 design, manufacturing information, and distribution records necessary to develop and validate 15 model-specific examination protocols. Those protocols must address unauthorized components, 16 altered display assemblies, concealed additions, and device-resident alterations capable of exposing 17 recovery information. A written result must identify what was examined, the method used, and 18 whether the examination established physical integrity or left an unresolved condition. An 19 inconclusive examination must not be reported as confirmation that the complete device is secure. 20 21 22 41 26 42 Ledger, Best Practices to Securely Buy Your Ledger Signer, https://www.ledger.com/academy/topics/ledgersolutions/best-practices-to-securely-buy-ledger23 signer; see also Ledger, Check Hardware Integrity, Ledger Flex tab, “Important notice,” 24 https://support.ledger.com/article/4404382029329-zd (Flex-specific warning reproduced in Plaintiff’s “Do not disassemble” screenshot on file with counsel); Ledger Donjon, Genuineness, 25 https://donjon.ledger.com/threat-model/device-genuineness/. Ledger, Crypto in Germany: The Ultimate Guide, https://www.ledger.com/academy/topics/country-guides/crypto-in-germany-the-ultimate-guide 27 (Oct. 12, 2026 text cited in the supplied draft; preserve that dated version for the quoted historical 28 statement). 31 CLASS ACTION COMPLAINT Case No. 26-16867 Case 3:26-cv-12867 1 Document 1 Filed 10/30/26 Page 32 of 51 PageID #: 32 Plaintiff seeks the prompt establishment of a Ledger-funded protective recall and 2 professional inspection program for the Covered Devices held by Class members, regardless of 3 seller or distribution channel. No Class member must disassemble a device or provide an 4 independent technical report as a condition of requesting professional inspection. The program must 5 prevent additional exposure when a Class member resumes use of retained or replacement Ledger 6 hardware. Qualified Ledger hardware-security personnel or independent specialists must examine 7 submitted devices under validated, model-specific protocols addressing the complete recovery8 information path. Ledger must pay the necessary intake, shipping, examination, and secure-return 9 costs. The protocol must account for Ledger's own warning that opening a Flex can irreversibly 10 damage it, and must not condition eligibility on the owner performing that disassembly. Where 11 examination identifies compromise, reliable verification cannot promptly be completed, or 12 examination damages the device, the program must provide a new, professionally verified 13 replacement through secure and traceable delivery before the consumer resumes sensitive use. 14 Ledger must correct the relevant security deficiency before presenting a replacement as safe for that 15 use. 16 The program's scope must follow the challenged security condition and the available 17 technical and traceability evidence. Reports involving different Ledger models and sales channels, 18 including the reported Flex implant, support protection beyond CryptoBilis. An intact Secure 19 Element, apparently unopened packaging, or a different seller does not resolve whether concealed 20 hardware can acquire recovery information. The requested program therefore includes the Covered 21 Devices held by Class members across manufacturing and assembly facilities, production lots, and 22 distribution channels. Any proposed exclusion must be supported by reliable component, 23 manufacturing, custody, and examination evidence sufficient for the Court to determine that the 24 excluded devices do not require the protective measure at issue. Ledger must provide that 25 information for independent assessment and the Court's determination of appropriate scope. 26 The program must provide secure intake, documented custody, written inspection results, 27 independent technical oversight, and preservation of suspect components before destructive 28 examination or reset. Participation must not require a release of claims or forfeiture of warranty or 32 CLASS ACTION COMPLAINT Case No. 26-16867 Case 3:26-cv-12867 Document 1 Filed 10/30/26 Page 33 of 51 PageID #: 33 1 statutory rights. Neither Ledger nor an examiner may obtain the owner's recovery phrase, private 2 keys, PIN, control of assets, or unnecessary wallet or account identifiers. Where recovery 3 information may have been exposed, the program must provide secure instructions and assistance 4 enabling the owner to generate fresh recovery information on trusted hardware and migrate assets 5 under the owner's exclusive control. A replacement device must not be presented as correcting 6 exposure if the owner continues using compromised recovery information. 43 7 The same prospective protection requires Ledger to identify and quarantine unverified 8 inventory within its control, implement validated physical-integrity and traceability controls before 9 further distribution, correct its authentication and setup communications, and give affected 10 consumers direct and prominent notice of available verification and protective measures. Corrective 11 notices must reach consumers where Ledger directs purchasing and use, including the official 12 reseller directory, purchasing links, activation instructions, the official application, and support 13 communications. Removing a seller from a directory does not notify every prior purchaser or 14 determine whether devices already delivered through that or another channel contain an implant. 15 Plaintiff seeks court-supervised implementation with defined completion milestones and 16 independent technical reporting. This relief addresses the continuing inability to evaluate and use 17 Ledger hardware with the represented security protections and the risk of future exposure during 18 sensitive use. The announced regional sales suspensions, sample inspections, and backroom-stock 19 requirements do not determine the condition of each product already delivered to a consumer. They 20 cannot substitute for direct notice and reliable verification of those products. The requested relief 21 addresses that unresolved need, with model-specific inspection and replacement standards 22 supported by the technical evidence. Those corrections must separately address what Ledger's 23 official reseller designation, partner vetting, sourcing requirements, and product-integrity 24 25 26 43 Ledger, What to Do If Your Crypto Project Gets Hacked, https://www.ledger.com/academy/basic-basics/launch-a-crypto-project-securely/what-to-do-if27 your-crypto-project-gets-hacked (background for owner-controlled protective measures; the 28 requested program is Plaintiff’s proposed relief). 33 CLASS ACTION COMPLAINT Case No. 26-16867 Case 3:26-cv-12867 Document 1 Filed 10/30/26 Page 34 of 51 PageID #: 34 1 assurances do and do not establish about an individual unit. Ledger must not present commercial 2 authorization alone as verified absence of physical tampering. 3 Contemporaneously with filing, Plaintiff will provide the separate notice and corrective 4 demand required by Civil Code section 1782. Plaintiff presently seeks injunctive relief under the 5 CLRA and UCL. CLRA damages, monetary restitution, and other relief subject to the statutory 6 notice and correction requirements are reserved for amendment after compliance with section 1782. 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 V. CLASS ACTION ALLEGATIONS Plaintiff brings every cause of action in this Complaint on behalf of himself and the same Class under Federal Rule of Civil Procedure 23(a) and (b)(3), and seeks certification of appropriate common injunctive relief for that Class under Rule 23(b)(2). Plaintiff proposes one Class, defined as follows: All natural persons who purchased a Ledger hardware wallet primarily for personal, family, or household use and, before class certification, suffered an unauthorized loss of cryptocurrency through spyware installed in that wallet before delivery to them. For purposes of this Complaint, “spyware” means an unauthorized hardware implant, component substitution, or device-resident alteration capable of acquiring or transmitting recovery information without the user’s authorization. “Covered Devices” means Ledger hardware wallets implicated by that mechanism, including Flex, Nano X, Stax, and other Ledger models. The Class is not limited to CryptoBilis, an authorized seller, a particular model, or a particular country of purchase or residence. A loss caused only by phishing, voluntary disclosure of recovery information, or malware unrelated to spyware in the delivered hardware is outside this definition. Class membership turns on the purchase, the pre-delivery spyware, and the resulting unauthorized cryptocurrency loss—not on a determination that Ledger is liable. Ledger’s product, distribution, support, incident, and examination records, together with purchase, device, and transaction evidence, can identify members. Recovery remains subject to proof of the elements and timeliness of each claim, without separate purchaser, theft, model, seller, or injunctive classes. Excluded from the Class are Ledger and its officers and directors; persons who participated in installing or knowingly distributing the spyware or carrying out the unauthorized transfers; 34 CLASS ACTION COMPLAINT Case No. 26-16867 Case 3:26-cv-12867 Document 1 Filed 10/30/26 Page 35 of 51 PageID #: 35 1 entities controlled by Ledger; the assigned judicial officers and their immediate families; and 2 persons who timely and validly request exclusion from a class certified under Rule 23(b)(3). 3 Numerosity. On information and belief, the Class is sufficiently numerous that joinder is 4 impracticable. The reported spyware incidents across multiple models and distribution channels, 5 Ledger’s investigation and customer contacts, and the concealed nature of the alleged compromise 6 support the need for aggregate treatment. The number and identities of qualifying victims will be 7 determined from incident, support, sales, distribution, device-examination, and transaction records; 8 Ledger’s total sales are not treated as a count of spyware victims. 9 Commonality. Common questions include whether Ledger adequately protected the 10 recovery-information path against pre-delivery spyware; whether Genuine Check and the associated 11 communications disclosed that an authentic chip could coexist with an implant; what Ledger knew 12 and when; whether its design, packaging, testing, and distribution controls reasonably addressed the 13 risk; whether its product-security affirmations and omissions were misleading; and what corrective 14 measures are necessary. The design, warranty, negligence, and consumer-protection claims arise 15 from that shared manufacturer-level conduct. 16 Typicality and adequacy. Baylor purchased two Flex devices for personal use, followed 17 Ledger’s purchasing and setup directions, received successful Genuine Check results, and suffered 18 the alleged spyware-related theft of his cryptocurrency. His claims present the same distinction 19 between an authentic Secure Element and the integrity of the complete product. He seeks recovery 20 for the same type of property loss and correction of the practices that prevent reliable future use. He 21 will fairly and adequately protect the Class and has retained counsel experienced in complex and 22 class litigation. 23 Predominance and superiority. Ledger’s design specifications, authentication, standardized 24 communications, knowledge, and distribution controls are susceptible to common documentary and 25 technical proof. Individual ownership, device configuration, transaction history, causation, and loss 26 amounts can be evaluated through a common evidentiary process without repeatedly litigating the 27 manufacturer-level issues. Class treatment avoids duplicative expert examinations and adjudications 28 35 CLASS ACTION COMPLAINT Case No. 26-16867 Case 3:26-cv-12867 Document 1 Filed 10/30/26 Page 36 of 51 PageID #: 36 1 and provides a practical means of pursuing claims whose investigation and litigation costs would 2 otherwise deter recovery. 3 Damages. Plaintiff and the Class seek the legally recoverable value of cryptocurrency lost 4 through the alleged spyware compromise, together with recoverable product-value loss and 5 incidental and consequential expenses under the applicable counts. A damages method consistent 6 with the liability theory will account for device and transaction records, valuation, refunds, 7 recoveries, and any other offsets, without double recovery. The difference in the amounts lost does 8 not change the alleged common mechanism. 9 Prospective relief. Ledger’s continuing authentication, warning, distribution, and 10 verification practices are common to the Class. Baylor retains the affected hardware and presently 11 wants to use or obtain reliably verified Ledger devices. He seeks a uniform corrective program that 12 gives Class members reliable information, professional examination, and verified replacement 13 where needed before further sensitive use. Certification under Rule 23(b)(2) is requested only 14 insofar as the evidence establishes indivisible prospective relief appropriate to the Class as a whole; 15 monetary awards are sought under Rule 23(b)(3). 16 Case management. Plaintiff seeks certification of this single Class for all six counts. If 17 particular issues require separate adjudication, Rule 23(c)(4) permits common issues to be resolved 18 for the same Class, with individualized determinations where necessary. Model-specific technical 19 protocols and transaction records can address factual differences without creating separately defined 20 classes. Plaintiff may refine the definition in light of discovery and the Court’s orders. 21 22 23 24 25 26 VI. CAUSES OF ACTION FIRST CAUSE OF ACTION BREACH OF EXPRESS WARRANTY California Commercial Code §§ 2313, 2714, and 2715 Plaintiff and the Class against Ledger SAS Plaintiff incorporates the allegations in Sections I through V. Plaintiff brings this count on behalf of himself and the Class. 27 28 36 CLASS ACTION COMPLAINT Case No. 26-16867 Case 3:26-cv-12867 1 Document 1 Filed 10/30/26 Page 37 of 51 PageID #: 37 Ledger made express affirmations of fact and descriptions of the goods through two distinct 2 communications. First, its official reseller designation, in the purchasing and security context 3 alleged above, described goods supplied through a manufacturer-selected channel as protected by 4 Ledger's product-integrity and distribution safeguards and suitable for secure initialization. The 5 channel protections Ledger describes in its own publications corroborate that asserted meaning. 6 Those factual product descriptions create express warranties under California Commercial Code § 7 2313(1)(a)–(b) to the extent they formed part of the basis of the bargain. Second, Ledger's successful 8 Genuine Check, furnished with the hardware and prescribed initial setup, communicated in context 9 that the particular delivered device was suitable to proceed safely through Ledger's initialization. 10 The warranties concern the described physical condition and security functionality, not merely the 11 authenticity of one chip. 12 Ledger supplied its official directory to guide the purchasing decision and its authentication 13 to guide initial use. Baylor followed that directory, relied on Ledger's designation of CryptoBilis in 14 selecting his source, and purchased the two Flex devices as new products of Ledger's authorized 15 channel. The product-integrity description conveyed by that designation in the security context 16 alleged above formed part of the basis of his bargain. The manufacturer-prescribed authentication 17 was included product performance and separately reinforced his decision to proceed with setup and 18 commit cryptocurrency. These are cumulative assurances concerning the goods and their initial 19 protective function. 20 The channel-integrity warranties are asserted against Ledger for Ledger's own descriptions 21 and representations concerning its goods and their distribution safeguards. They do not depend on 22 attributing every independent statement or act of the reseller to Ledger. Nor does the use of the word 23 “recommends,” rather than “warrants” or “guarantees,” defeat an otherwise actionable factual 24 affirmation or description under California Commercial Code § 2313(2). The physical condition 25 represented for products supplied through the designated channel is independently capable of proof 26 or disproof. 27 On information and belief, one or more of Baylor's devices contained the concealed physical 28 alteration described above when delivered. Such a device did not conform to the physical-integrity 37 CLASS ACTION COMPLAINT Case No. 26-16867 Case 3:26-cv-12867 Document 1 Filed 10/30/26 Page 38 of 51 PageID #: 38 1 and secure-initialization condition conveyed by the official purchasing designation in context, even 2 if its original Secure Element remained genuine. On information and belief, the delivered goods and 3 included security functionality also failed to conform to the setup-stage affirmation: inadequate 4 protection of the recovery-information path, ineffective indications of prior interference, and the 5 absence of an effective tamper response allowed the altered device to pass the supplied 6 authentication and expose newly generated recovery information. The inadequate disclosure left that 7 material condition unresolved. A technically successful check of an authentic component does not 8 establish conformity of the complete product with the alleged warranties. 9 Plaintiff paid for the products, used Ledger's official setup and authentication, generated 10 recovery information on the devices, and kept that information offline. 11 Before filing, Baylor reported the unauthorized losses to Ledger, which acknowledged his 12 report and sought device, purchase, delivery, and setup information in its October 12, 2026 response 13 in support case 00285187. Contemporaneously with filing this Complaint, Plaintiff will also provide 14 Ledger with written notice identifying the alleged breaches and security deficiencies and demanding 15 corrective relief. That notice identifies the product-integrity meaning conveyed by Ledger's official 16 reseller designation, Ledger's published descriptions of reseller selection, sourcing protections and 17 restrictions on returned goods, the alleged delivery of altered goods through that channel, and the 18 separate setup-stage warranty breach. 19 The breach was a substantial factor in Plaintiff's loss. Ledger's purchasing designation 20 induced him to obtain the devices through its authorized channel; the delivered products' 21 nonconformity exposed recovery information; and the successful setup result induced him to 22 commit assets. He would not have obtained and funded hardware through that channel had the actual 23 compromised condition or material limitation been adequately disclosed. Loss of cryptocurrency 24 through exposure of recovery information was foreseeable to Ledger, which supplied the product 25 and authentication for the specific purpose of securing access to that property. 26 Plaintiff seeks direct, incidental, and consequential relief under California Commercial Code 27 sections 2714 and 2715 for breach of Ledger's public product affirmations and descriptions. 28 Replacing the hardware after exposure cannot restore the secrecy of the compromised recovery 38 CLASS ACTION COMPLAINT Case No. 26-16867 Case 3:26-cv-12867 Document 1 Filed 10/30/26 Page 39 of 51 PageID #: 39 1 information or return cryptocurrency already transferred. Plaintiff does not concede any agreed 2 disclaimer or limited remedy. If Ledger establishes an otherwise applicable limitation, Plaintiff 3 challenges it, as appropriate, under sections 2316(1) and 2719, including inconsistency with an 4 express warranty or failure of an exclusive remedy's essential purpose. 5 Plaintiff and the Class seek the difference between the value of the goods and included 6 security functionality as represented and as delivered, together with recoverable incidental and 7 consequential damages under California Commercial Code §§ 2714 and 2715. Consequential 8 damages include the value of cryptocurrency lost through the alleged spyware compromise and 9 reasonable response and recovery expenses to the extent incurred and proven. Plaintiff’s 10 cryptocurrency loss exceeds $1 million. No duplicate recovery is sought. 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 SECOND CAUSE OF ACTION VIOLATION OF THE CONSUMERS LEGAL REMEDIES ACT (INJUNCTIVE RELIEF ONLY) California Civil Code § 1750 et seq. Plaintiff and the Class against Ledger SAS Plaintiff incorporates the allegations in Sections I through V. Plaintiff brings this count on behalf of himself and the Class and seeks present injunctive relief to prevent continuing deceptive practices and future exposure during use of the Covered Devices. CLRA damages, monetary restitution, and other relief subject to the notice and correction requirements of Civil Code section 1782 are reserved for amendment after compliance with that statute. Plaintiff and the Class are consumers under Civil Code § 1761(d). The Covered Devices are tangible consumer goods under § 1761(a), purchased primarily for personal, family, or household use. Ledger is a person under § 1761(c). The transactions included the manufacturer-supplied security functionality, packaging, initial setup, and authentication associated with those goods. Ledger represented security characteristics and benefits the goods did not possess, in violation of Civil Code § 1770(a)(5), and a standard or quality the goods did not meet, in violation of § 1770(a)(7). Ledger’s purchasing representation concerned product integrity and suitability for secure initialization conveyed by Ledger's manufacturer-controlled designation of the purchasing channel. Ledger's own descriptions of reseller selection, sourcing safeguards, and restrictions on 39 CLASS ACTION COMPLAINT Case No. 26-16867 Case 3:26-cv-12867 Document 1 Filed 10/30/26 Page 40 of 51 PageID #: 40 1 returned goods corroborate the asserted meaning of that designation. An altered device does not 2 possess the alleged physical-integrity condition merely because its Secure Element is authentic. 3 Separately, the successful Genuine Check and prescribed setup communicated a condition for secure 4 initial use without adequately disclosing that the result could coexist with physical interception of 5 recovery information. 6 Ledger's successful result and setup directions communicated only part of the material 7 security condition. Ledger knew the scope of the authentication it designed and the difference 8 between an authentic component and an uncompromised complete device. Having furnished that 9 result to guide initial use, Ledger was required to disclose the material limitation that a concealed 10 component could acquire recovery information while remaining undetected. The condition 11 concerned the wallet's central protective function and rendered the communicated characteristics, 12 benefits, standard, and quality misleading. Having directed consumers to a manufacturer-selected 13 purchasing channel as a product-integrity safeguard, Ledger also had to disclose facts necessary to 14 prevent that direction from misleading purchasers about the concealed physical-interception risk. 15 The omission concerned the delivered goods despite the official seller designation and subsequent 16 successful component check. 17 The challenged communication was made by Ledger through its official application during 18 Plaintiff's initial setup of the two Flex devices purchased on July 13 and September 4, 2026. It 19 identified the devices as 'Genuine' and allowed Plaintiff to proceed. Plaintiff received that result 20 before generating recovery information and committing assets. The material omitted information 21 was the physical-implant limitation described in the factual allegations above. Ledger also made the 22 purchasing representation through its own Official Reseller Network when Baylor selected 23 CryptoBilis for the July 13 and September 4 purchases. Baylor relied on that official designation in 24 choosing the source of his new Flex devices. The challenged purchasing representation is the 25 product-integrity meaning conveyed by that designation in the security context alleged above, not a 26 statement made solely by CryptoBilis. 27 The condition and omission were material. A reasonable consumer buying a hardware wallet 28 to safeguard recovery information would consider whether the manufacturer's successful check 40 CLASS ACTION COMPLAINT Case No. 26-16867 Case 3:26-cv-12867 Document 1 Filed 10/30/26 Page 41 of 51 PageID #: 41 1 addresses an alteration capable of capturing that information. Plaintiff actually relied on Ledger's 2 official purchasing designation in choosing his source and on the later successful result in deciding 3 to proceed with sensitive setup and funding. An adequate warning would have caused him to 4 withhold assets from the affected recovery information and obtain a secure alternative. 5 Plaintiff's reliance during setup caused him to expose his assets to the affected recovery 6 information and resulted in the theft losses alleged above. He also received security functionality 7 worth less than represented because it failed to address the concealed condition central to its 8 protective purpose. Those completed injuries establish his stake in the challenged conduct. His 9 present desire to use or obtain Ledger hardware with verified or corrected physical security, and 10 inability to rely on the challenged authentication for that purpose, supply the prospective injury for 11 which he seeks an injunction. A later damages award for the completed loss would not stop the 12 continuing deception or permit informed future use. Reliable future purchasing requires correction 13 of the authorized-channel product-integrity representations as well as the authentication and setup 14 disclosures. 15 Plaintiff seeks only prospective injunctive relief under the CLRA in this initial Complaint. 16 Contemporaneously with commencement of this action, Plaintiff will provide Ledger with a 17 separate written notice identifying the particular violations alleged here, including the authorized18 channel product-integrity and setup representations, and demanding corrective relief under Civil 19 Code section 1782(a), including the inspection and replacement program described above. After at 20 least 30 days have elapsed following commencement of this action and the applicable statutory 21 notice and correction periods have expired, Plaintiff intends to amend under section 1782(d) and 22 Federal Rule of Civil Procedure 15 to seek available CLRA damages and other remedies, subject to 23 sections 1782(b) and (c). 24 Plaintiff seeks preliminary and permanent injunctive relief under Civil Code section 25 1780(a)(2) correcting Ledger's continuing deceptive authentication, disclosure, distribution, and 26 initialization practices. Ledger must correct misleading representations about the integrity of goods 27 purchased through its official network and the scope and implementation of reseller vetting and 28 sourcing standards. It must also provide accurate security representations, prominent disclosure of 41 CLASS ACTION COMPLAINT Case No. 26-16867 Case 3:26-cv-12867 Document 1 Filed 10/30/26 Page 42 of 51 PageID #: 42 1 unresolved physical-interception risks before sensitive use, and reliable standards for physical2 integrity verification. It must not present component authentication or an inconclusive physical 3 examination as assurance that the complete device is uncompromised. The immediate protective 4 recall, professional inspection, and secure-replacement program is also requested under Count VI. 5 Plaintiff seeks reasonable attorney's fees and costs under section 1780(e). This count requests no 6 damages or monetary restitution at this time. The statutory protections and remedies may not be 7 waived contrary to section 1751. 8 THIRD CAUSE OF ACTION NEGLIGENCE Plaintiff and the Class against Ledger SAS 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 Plaintiff incorporates the allegations in Sections I through V. Plaintiff brings this count on behalf of himself and the Class. As the designer and manufacturer of a security product intended to protect access to separately owned assets, Ledger owed foreseeable users reasonable care in designing, manufacturing, packaging, testing, and validating the hardware's recovery-information protections and in supplying accurate instructions and authentication. Ledger also owed reasonable care in the distribution-security functions it undertook and controlled. The duty encompasses foreseeable interference with a security device before the consumer receives and initializes it, including access during manufacturing, assembly, storage, shipment, retail custody, and returns handling. Ledger also undertook to provide purchasers with an initial security assessment through its official application and Genuine Check, specify the initial-use procedure, and identify its official distribution channel. Ledger knew that purchasers would use those functions to decide whether to generate recovery information and commit cryptocurrency. Having supplied the assessment and directed that reliance, Ledger owed reasonable care in performing the functions it undertook and communicating the material limits of the result at the point where it invited the purchaser to proceed. That duty required an accurate explanation before generation of recovery information, when the foreseeable exposure could still be prevented. Baylor relied on that assessment and procedure before exposing his assets. 28 42 CLASS ACTION COMPLAINT Case No. 26-16867 Case 3:26-cv-12867 1 Document 1 Filed 10/30/26 Page 43 of 51 PageID #: 43 Ledger knew or should have known that users would rely on its authentication in deciding 2 whether to generate recovery information and commit cryptocurrency; that exposure of that 3 information could give an attacker control of the assets; and that pre-delivery interference with a 4 security device was a foreseeable hazard. The magnitude of loss could be substantial even for a 5 single consumer. 6 Ledger breached its duties by inadequately protecting the complete recovery-information 7 path; failing reasonably to test authentic devices against opening, alteration, and resealing; failing 8 to provide effective tamper detection and a response that prevented sensitive operation; using 9 inadequate packaging and verification controls; and communicating a successful result without 10 adequate disclosure of the unresolved condition. On information and belief, it also failed reasonably 11 to implement and enforce inventory, returns, revalidation, and incident-response controls associated 12 with its official distribution channel. The alleged breach also includes failure to provide adequate 13 transaction-stage and pre-initialization warnings in response to the physical-implant information 14 received before Baylor's purchases and loss. 15 Those failures were substantial factors in Plaintiff's harm. The deficient protections 16 permitted an altered device to reach him without effective indication of interference, and the absence 17 of an effective tamper response allowed exposure of new recovery information. Ledger's successful 18 security assessment and inadequate disclosure induced him to proceed and commit assets. 19 Reasonable performance of the undertaken functions and effective protective layers would have 20 interrupted that sequence. On information and belief, the same failures permitted pre-delivery 21 spyware to acquire Class members’ recovery information and were substantial factors in their 22 unauthorized cryptocurrency losses. 23 The malicious actors' acquisition and exploitation of recovery information were foreseeable 24 manifestations of the risk against which the product and authentication were supplied. Their 25 intervention does not eliminate the causal role of the alleged product and warning deficiencies. 26 Plaintiff and the Class lost cryptocurrency they owned independently of the hardware wallets 27 and their software. They seek compensation for that separate property and other legally recoverable 28 43 CLASS ACTION COMPLAINT Case No. 26-16867 Case 3:26-cv-12867 Document 1 Filed 10/30/26 Page 44 of 51 PageID #: 44 1 consequential harm according to proof. This tort claim is pleaded in the alternative to the warranty 2 claim, without duplicate recovery. 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 FOURTH CAUSE OF ACTION STRICT PRODUCTS LIABILITY - DESIGN DEFECT Plaintiff and the Class against Ledger SAS Plaintiff incorporates the allegations in Sections I through V. Plaintiff brings this count on behalf of himself and the Class. Ledger designed, manufactured, and placed the Covered Devices and their packaging into the stream of commerce for ultimate purchasers to generate and protect recovery information and control their cryptocurrency. Ledger intended consumers to initialize them through the official process without first performing a forensic examination of internal components. On information and belief, the original design inadequately protected the recoveryinformation path against foreseeable physical interference and allowed a delivered device to proceed with sensitive initialization despite an undetected alteration. The challenged design includes the enclosure and component protections, detection of and response to tampering, the packaging's failure to reveal prior interference, and the relationship of those safeguards to Genuine Check. Those choices permitted the alleged compromise to defeat the product's security purpose. The challenged design choices existed when Ledger placed the products into distribution. Their inadequacy made the recovery-information path susceptible to foreseeable pre-delivery interference and allowed an altered device to proceed through Ledger's successful initial check. The original defect was Ledger's failure to protect, detect, or stop that exposure through the hardware and security process it supplied. That defect accompanied the product through the supply chain and operated when Baylor followed the prescribed setup. The identity and location of the person exploiting the defect do not remove its substantial causal role in the resulting exposure. The risks of the challenged design outweighed its benefits. The gravity of exposing recovery information and the associated assets, the known prospect of pre-delivery tampering, and the product's security purpose outweighed the benefits of the inadequate protective choices. Feasible alternatives included the physical barriers, persistent tamper detection and response, protected 28 44 CLASS ACTION COMPLAINT Case No. 26-16867 Case 3:26-cv-12867 Document 1 Filed 10/30/26 Page 45 of 51 PageID #: 45 1 information paths, and verifiable packaging alleged above. They would have reduced the risk before 2 initialization and funding while preserving the product's useful function. 3 Alternatively, the product failed to perform as safely as an ordinary consumer would expect 4 during intended and reasonably foreseeable use. A consumer who obtains a device sold as new, 5 follows the prescribed setup, receives the manufacturer's successful check, and generates recovery 6 information on the device reasonably expects that the process will not expose that information to a 7 concealed unauthorized component. Baylor followed that process, yet the alleged original security 8 deficiencies allowed the information controlling his assets to be acquired. 9 Plaintiff used the Flex in an intended and reasonably foreseeable manner by following 10 official setup, generating recovery information on the device, and committing cryptocurrency after 11 a successful check. Attempts by criminals to modify hardware wallets before delivery were a 12 foreseeable product risk of the kind described above. 13 On information and belief, the original defect was a substantial factor in the interception of 14 recovery information and the resulting unauthorized transfers. Plaintiff and members of the Class 15 suffered loss of separately owned cryptocurrency. They seek compensatory damages according to 16 proof, in the alternative to other available theories and without duplication. 17 18 19 20 21 22 23 24 25 26 27 FIFTH CAUSE OF ACTION STRICT PRODUCTS LIABILITY - FAILURE TO WARN Plaintiff and the Class against Ledger SAS Plaintiff incorporates the allegations in Sections I through V. Plaintiff brings this count on behalf of himself and the Class. Ledger manufactured and distributed the Covered Devices with their packaging, setup, and authentication. On information and belief, the risk that unauthorized pre-delivery interference could expose recovery information despite successful Secure Element authentication was known or knowable in light of the generally recognized scientific and technical knowledge available when the relevant devices were manufactured and distributed. Ledger's knowledge included the scope of its own design and the supply-chain research and implant information available at the relevant time. The reported March 4, 2026 disclosure and the earlier research described above 28 45 CLASS ACTION COMPLAINT Case No. 26-16867 Case 3:26-cv-12867 Document 1 Filed 10/30/26 Page 46 of 51 PageID #: 46 1 concern notice of the relevant attack mechanism before Baylor's purchases, not advance 2 identification of his particular units. 3 That risk presented a substantial danger to users' separately owned cryptocurrency during 4 intended initial use. It was concealed within the product and was not a condition an ordinary 5 purchaser could identify from the unopened retail packaging, an apparently normal device, or a 6 successful result from the manufacturer's own check. 7 Ledger failed to provide an adequate warning before sensitive initialization that a successful 8 Genuine Check did not exclude an unauthorized component elsewhere in the device; that apparently 9 intact packaging did not resolve that limitation; and that the condition could expose newly generated 10 recovery information. An adequate warning would have explained the specific limitation and 11 directed the purchaser not to rely on Genuine Check alone while whole-device integrity remained 12 unverified, and to obtain appropriate verification, a verified replacement, or a secure alternative 13 before generating recovery information or committing assets. 14 Plaintiff did not receive an adequate warning of that risk before proceeding. He would have 15 heeded one by withholding assets pending a secure alternative. The failure to warn was therefore a 16 substantial factor in his exposure to the alleged compromise and ensuing loss. On information and 17 belief, the same failure to provide an adequate warning before sensitive use contributed to Class 18 members’ spyware-related losses. Plaintiff and the Class seek compensatory damages for their 19 separately owned cryptocurrency and other recoverable harm according to proof. 20 21 22 23 24 25 26 27 28 SIXTH CAUSE OF ACTION VIOLATION OF THE UNFAIR COMPETITION LAW (INJUNCTIVE RELIEF ONLY) California Business and Professions Code § 17200 et seq. Plaintiff and the Class against Ledger SAS Plaintiff incorporates the allegations in Sections I through V. Plaintiff brings this count on behalf of himself and the Class. Ledger's design, distribution, marketing, authentication, and support of the Covered Devices are business acts and practices within California Business and Professions Code section 17200. Ledger directs those practices to California consumers through the California commerce and 46 CLASS ACTION COMPLAINT Case No. 26-16867 Case 3:26-cv-12867 Document 1 Filed 10/30/26 Page 47 of 51 PageID #: 47 1 continuing customer relationships alleged above. Those practices include Ledger's own written 2 representations about the physical integrity of products obtained from its official network, its vetting 3 and standards for designated sellers, and the source and custody protections accompanying the 4 goods. 5 Those practices are unlawful because Ledger misrepresents and omits material security 6 characteristics, benefits, and quality in violation of Civil Code sections 1770(a)(5) and (7). Ledger 7 supplies an initial security determination that permits sensitive setup while withholding the material 8 fact that concealed hardware can acquire newly generated recovery information despite the 9 successful result. For authorized-network purchasers, the unlawful practices also include the 10 product-integrity, vetting, sourcing, and quality representations and related material omissions 11 pleaded under the same CLRA subsections. 12 Those practices are unfair because they expose consumers to concealed interference with the 13 very secrets the products are purchased to protect while denying consumers a reliable means of 14 determining whether the delivered hardware is compromised. The substantial injury cannot 15 reasonably be avoided by following Ledger's prescribed setup and is not outweighed by 16 countervailing benefits to consumers or competition. Consumers cannot resolve the hidden 17 condition through component authentication, ordinary packaging inspection, or disassembly that 18 Ledger itself strongly discourages because of the risk of irreversible damage. Accurate disclosures, 19 validated integrity verification, effective tamper controls, and secure distribution practices provide 20 feasible means of reducing the injury. The practices also offend the consumer-protection policies 21 embodied in the CLRA. Directing consumers to the official network as a means of safeguarding the 22 integrity of delivered products, while leaving an undisclosed material gap between seller 23 authorization and individual-device integrity, prevents purchasers from avoiding the very risk the 24 direction purports to address. 25 Those practices are fraudulent because they are likely to deceive reasonable consumers about 26 the condition of newly received hardware and the protection afforded by Ledger's successful 27 authentication. The misleading impression arises from Ledger's official reseller designation, the 28 product's security purpose, the prescribed setup sequence, and the successful result communicated 47 CLASS ACTION COMPLAINT Case No. 26-16867 Case 3:26-cv-12867 Document 1 Filed 10/30/26 Page 48 of 51 PageID #: 48 1 before the user generates recovery information and commits assets. Ledger knows the material 2 difference between authenticating the Secure Element and excluding an unauthorized component 3 elsewhere in the device. The additional purchasing representation conveys in context that Ledger's 4 designated network supplies new hardware protected by the manufacturer-described distribution 5 safeguards and suitable for secure initialization. Ledger's own purchasing and setup communications 6 are challenged; a third party's unauthorized alteration does not resolve whether Ledger's 7 representations and material omissions were misleading. 8 Baylor suffered injury in fact and lost money and property as a result. He relied on Ledger's 9 official distribution designation and successful authentication, followed the prescribed setup, and 10 placed his separately owned cryptocurrency under the control of the recovery information generated 11 on the devices. The concealed compromise and misleading security determination caused the 12 unauthorized losses alleged above. Adequate disclosure before sensitive use would have caused him 13 to withhold his assets pending a secure alternative. His expenditure on the devices followed Ledger's 14 official-channel representation, and the later asset commitment followed its authentication. On 15 information and belief, the goods he received did not have the physical-integrity condition and 16 protective functionality conveyed by those representations in context. The two stages of reliance are 17 alleged as parts of the causal sequence, not as duplicate losses. 18 Baylor retains the quarantined devices and presently wants to use or obtain Ledger hardware 19 whose physical security has been reliably verified or corrected. Ledger's continuing practices 20 prevent him from determining whether retained or newly obtained hardware can be trusted for that 21 use. Compensation for the completed loss cannot require Ledger to disclose the limits of its ongoing 22 authentication, provide the manufacturer-controlled information needed for reliable verification, or 23 correct its continuing distribution and initialization practices. Purchasing another device without 24 those corrections leaves the same concealed integrity question unresolved. Ledger's own instruction 25 to Baylor to use a new recovery phrase without using the current device underscores the need for a 26 reliably verified or corrected product on which he can securely resume the intended use. An 27 announcement of additional protections for an unreleased product does not establish the integrity of 28 48 CLASS ACTION COMPLAINT Case No. 26-16867 Case 3:26-cv-12867 Document 1 Filed 10/30/26 Page 49 of 51 PageID #: 49 1 his retained Flex devices or supply a present means of safely using them. Legal damages therefore 2 do not provide an adequate remedy for the prospective injury alleged here. 3 Plaintiff seeks preliminary and permanent injunctive relief under section 17203 requiring 4 accurate security communications, correction of misleading authorized-network product-integrity, 5 vetting, and sourcing representations, validated physical-integrity verification, and the protective 6 recall, professional inspection, and secure-replacement program alleged above, together with 7 effective controls against further distribution and sensitive initialization of compromised products. 8 The program addresses future use and exposure of recovery information through model-specific 9 protocols and the Court's determination of appropriate scope. Plaintiff requests no damages, 10 restitution, disgorgement, or cash reimbursement under this count. Plaintiff seeks reasonable 11 attorney's fees and costs under Code of Civil Procedure section 1021.5 and other applicable law. 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 VII. PRAYER FOR RELIEF WHEREFORE, Plaintiff requests judgment against Ledger SAS as follows: A. Certifying the Class under Federal Rule of Civil Procedure 23(b)(3) and, for appropriate common prospective relief, Rule 23(b)(2), or certifying particular common issues for that same Class under Rule 23(c)(4); appointing Kenneth Baylor as Class representative; and appointing his counsel as Class counsel; B. Awarding Plaintiff and the Class damages under Count I according to proof, including recoverable product-value loss and incidental and consequential damages; C. Awarding Plaintiff and the Class the legally recoverable value of cryptocurrency lost under Counts I, III, IV, and V, with Plaintiff’s contemporaneous estimate of his loss being approximately $1.05 million, together with proven, recoverable response and recovery expenses, without duplicate recovery; D. Awarding reasonable attorney's fees and costs under California Civil Code § 1780(e), California Code of Civil Procedure § 1021.5, and other applicable authority; E. Awarding prejudgment and postjudgment interest as permitted by law; F. Awarding preliminary and permanent injunctive relief under Counts II and VI for Plaintiff and the Class, to the extent supported by prospective injury and the requirements for the relief 49 CLASS ACTION COMPLAINT Case No. 26-16867 Case 3:26-cv-12867 Document 1 Filed 10/30/26 Page 50 of 51 PageID #: 50 1 sought, requiring Ledger to cease misleading representations concerning authorized-network 2 product integrity, reseller vetting, sourcing standards, and security verification; accurately 3 describe the controls actually applied to the products and their distribution; and disclose 4 material physical-integrity and Genuine Check limitations before purchase and sensitive 5 initialization, and requiring the immediate protective recall, professional inspection, and secure- 6 replacement program under Count VI. The order should require direct notice to eligible 7 consumers and coordinated corrections in Ledger's reseller directory, purchasing links, 8 activation materials, application, and support communications; Ledger-funded examination of 9 Covered Devices held by Class members under validated, model-specific protocols that account 10 for the risk of inspection damage and do not require owner disassembly; secure intake and 11 documented custody; written findings and independent technical oversight; verified 12 replacement before further sensitive use where a device is compromised, prompt reliable 13 verification is unavailable or inconclusive, or examination damages it; secure instructions and 14 assistance for owner-controlled recovery-information regeneration and asset migration; 15 quarantine and verification of unverified inventory before further distribution; effective 16 manufacturing, packaging, custody, and returns controls; access to the corrective program 17 without purchasing a new premium model or awaiting the release of Ledger Atom; and defined 18 implementation milestones and compliance reporting; and 19 G. Granting such other relief as the Court determines is just and proper, without duplicate recovery. 20 CLRA damages, monetary restitution, and other remedies subject to Civil Code section 1782 21 remain reserved pending compliance with that statute. Count VI seeks injunctive relief and 22 associated fees and costs only. 23 24 25 26 27 28 50 CLASS ACTION COMPLAINT Case No. 26-16867 Case 3:26-cv-12867 Document 1 1 Filed 10/30/26 Page 51 of 51 PageID #: 51 VIII. DEMAND FOR JURY TRIAL 2 Pursuant to Federal Rule of Civil Procedure 38, Plaintiff demands a trial by jury on all issues so 3 triable. 4 5 DATED: October 30, 2026 FROST LLP 6 7 8 9 By: CHRISTOPHER FROST KEVIN S. DICKER Attorneys for Kenneth Baylor 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 51 CLASS ACTION COMPLAINT Case No. 26-16867