In re: Snowflake, Inc., Data Security Breach Litigation

CourtDistrict Court, D. Montana
DecidedFebruary 5, 2026
Docket2:26-cv-00011
StatusUnknown

This text of In re: Snowflake, Inc., Data Security Breach Litigation (In re: Snowflake, Inc., Data Security Breach Litigation) is published on Counsel Stack Legal Research, covering District Court, D. Montana primary law. Counsel Stack provides free access to over 12 million legal documents including statutes, case law, regulations, and constitutions.

Bluebook
In re: Snowflake, Inc., Data Security Breach Litigation, (D. Mont. 2026).

Opinion

UNITED STATES JUDICIAL PANEL Fl L E D on MULTIDISTRICT LITIGATION Feb 05, 2026 CLERK, U.S. DISTRICT COURT EASTERN DISTRICT OF CALIFORNIA IN RE: SNOWFLAKE, INC., DATA SECURITY BREACH LITIGATION MDL No. 3126

TRANSFER ORDER

Before the Panel:* Pro se plaintiff in the action listed on Schedule A (Jones IT) moves under Panel Rule 7.1 to vacate the order conditionally transferring the action to the District of Montana for inclusion in MDL No. 3126. Defendant AT&T Inc. opposes the motion and supports transfer. After considering the parties’ arguments, we find that the action involves common questions of fact with the actions transferred to MDL No. 3126, and that transfer under 28 U.S.C. § 1407 will serve the convenience of the parties and witnesses and promote the just and efficient conduct of the litigation. The actions in MDL No. 3126 involve common factual questions concerning a cluster of data breaches that occurred on the Snowflake cloud platform from approximately April through June 2024, when a threat actor allegedly exfiltrated the personal information of over 500 million consumers and employees, including AT&T cellular customers. See In re AT&T Inc. Cellular Customer Data Sec. Breach Litig., 753 F. Supp. 3d 1368, 1371 (J.P.M.L. 2024). In centralizing the actions, we observed that the breach of AT&T data on the Snowflake cloud allegedly involves metadata for calls and texts made by AT&T cellular customers and certain others using the AT&T network from May 1, 2022, to October 31, 2022, and, for some customers, records from January 2, 2023. Jd. at 1372-73 n.6. The Jones IJ action involves overlapping factual issues concerning the breach of AT&T data on the Snowflake platform — in particular, the breach of text messaging and call data from May 2022 to October 2022 and in January 2023. Notably, plaintiff filed a substantially identical action against AT&T in late 2024 that we previously transferred to the MDL (Jones J).' Transfer will facilitate the efficient conduct of overlapping pretrial proceedings in Jones J and Jones IT, as well as the other actions in the MDL, and avoid the risk of inconsistent rulings.

* Judge Karen K. Caldwell, Judge Matthew F. Kennelly, and Judge David C. Norton did not participate in the decision of this matter. ' See Jones v. AT&T, Inc., No. 24-3368 (E.D. Cal. filed Dec. 2, 2024). The conditional transfer order transferring Jones J to the District of Montana became effective on January 2, 2025. See In re Snowflake, Inc., Data Sec. Breach Litig., MDL No. 3126, ECF No. 280 (J.P.M.L. Jan. 2, 2025). Jones I was docketed in the transferee court as Case No. 25-00001.

-2-

In opposition to transfer, plaintiff principally argues that (1) Jones II concerns breaches related exclusively to AT&T, in contrast to Snowflake, thus eliminating any common factual questions with the MDL; (2) the damages in Jones II are plaintiff-specific; (3) he opted out of the class settlement in the MDL; and (4) transfer would unfairly delay the resolution of his claims and cause inefficiency. These arguments are unpersuasive. First, plaintiff’s assertion that the MDL does not include the breach of AT&T data alleged in Jones II is wrong. Our initial transfer order clearly states that the MDL includes actions against AT&T and specifies that the AT&T incident at issue in the Snowflake MDL is the one announced by AT&T in July 2024 “involv[ing] metadata for calls and texts made by AT&T cellular customers . . . from May 1, 2022 to October 31, 2022, and, for some customers, records from January 2, 2023.” See In re AT&T Inc. Cellular Customer Data Sec. Breach Litig., 753 F. Supp. 3d at 1373- 73 & n.6. These specific data sets are at issue in Jones II. There is no basis for excluding Jones II from the MDL based on the complaint’s exclusive focus on AT&T as the alleged wrongdoer, the omission of allegations concerning Snowflake, and the inclusion of additional alleged data breaches spanning 2021-2024. Section 1407 does not require a complete identity of common factual issues or parties when, as here, the actions arise from a common factual core. See In re Valsartan Prods. Liab. Litig., 433 F. Supp. 3d 1349, 1352 (J.P.M.L. 2019). The asserted differences raised by Jones II also are undercut by the fact that, by plaintiff’s own account, Jones II raises the same factual issues as the Jones I action pending in the MDL. Second, plaintiff’s individualized injuries do not weigh against transfer. The existence of individualized injuries does not negate the efficiencies gained by transfer. See, e.g., In re Fluoroquinolone Prods. Liab. Litig., 122 F. Supp. 3d 1378, 1379 (J.P.M.L. 2015). Further, many of plaintiff’s alleged injuries – for example, emotional distress from the breach and the increased risk of fraud – are largely the same types of injuries alleged in the MDL. Indeed, they are the same injuries alleged in Jones I. Additionally, like the MDL plaintiffs, plaintiff Jones seeks punitive damages against AT&T. Third, plaintiff’s decision to opt out of the class settlement does not affect transfer. We routinely transfer opt-out actions to MDLs with class settlements because of the efficiencies to be gained from the transferee court’s management of overlapping actions and expertise in the issues. See, e.g., In re Payment Card Interchange Fee and Merchant Discount Antitrust Litig., MDL No. 1720, Transfer Order at 2 (J.P.M.L. Oct. 16, 2013). Fourth, transfer is warranted despite the alleged delay and inconvenience from transfer. Plaintiff’s grievances about the temporary stay of proceedings in the MDL and the alleged lack of progress in Jones I are not to the contrary. All of these grievances are essentially disagreements with how to structure the proceedings in the MDL. Dissatisfaction with the course of pretrial proceedings in an MDL is not a factor in deciding whether to transfer otherwise factually-related cases. See id. at 2 & n.3 (transferring opt-out plaintiffs’ actions over their objections concerning how the MDL was managed). Moreover, we look to “the overall convenience of the parties and -3- witnesses in the litigation as a whole, not just those of a single plaintiff or defendant in isolation.” See In re Watson Fentanyl Patch Prods. Liab. Litig., 883 F. Supp. 2d 1350, 1351-52 (J.P.M.L. 2012). Finally, we must raise an additional issue, given our serious concerns about the integrity of the record in this matter. Plaintiff’s briefs misrepresent the holdings and fabricate quotations with respect to at least seven Panel decisions.2 Additionally, two of the citations in plaintiffs’ briefs appear to be fabricated.3 The nature and number of the misrepresentations strongly suggest that plaintiff used generative artificial intelligence to draft his briefs without checking the accuracy of the information produced,4 though it also is possible he used some other unreliable source. Regardless, plaintiff improperly submitted briefs with false legal representations. We admonish plaintiff for fabricating and misrepresenting legal authorities in his briefing. This is an abuse of the judicial process, and one which we do not take lightly. Although pro se filings are held to less stringent standards than formal pleadings drafted by lawyers, all litigants (whether represented by counsel or not) are subject to an affirmative duty to conduct a reasonable inquiry into the substance of a filing before they present it to a court. This duty includes ensuring that citations and quotations are, in fact, real, as we recognized in a similar pro se matter last year. See In re Snowflake, Inc., Data Sec. Breach Litig., MDL No.

Free access — add to your briefcase to read the full text and ask questions with AI

Related

In Re Plumbing Fixture Cases
298 F. Supp. 484 (Judicial Panel on Multidistrict Litigation, 1968)
In Re Multidistrict Civil Antitrust Actions Involving the Distribution of Scotch Whiskey
299 F. Supp. 543 (Judicial Panel on Multidistrict Litigation, 1969)
In Re IBM Peripheral EDP Devices Antitrust Litigation
407 F. Supp. 254 (Judicial Panel on Multidistrict Litigation, 1976)
McKinney v. Bridgestone/Firestone, Inc.
128 F. Supp. 2d 1196 (S.D. Indiana, 2001)
In Re Not-For-Profit Hospitals/Uninsured Patients Litigation
341 F. Supp. 2d 1354 (Judicial Panel on Multidistrict Litigation, 2004)
In re Fluoroquinolone Products Liability Litigation
122 F. Supp. 3d 1378 (Judicial Panel on Multidistrict Litigation, 2015)
In re Watson Fentanyl Patch Products Liability Litigation
883 F. Supp. 2d 1350 (Judicial Panel on Multidistrict Litigation, 2012)

Cite This Page — Counsel Stack

Bluebook (online)
In re: Snowflake, Inc., Data Security Breach Litigation, Counsel Stack Legal Research, https://law.counselstack.com/opinion/in-re-snowflake-inc-data-security-breach-litigation-mtd-2026.