Jay Lewis Farrow v. John Does, 1-20

CourtDistrict Court, E.D. New York
DecidedNovember 4, 2025
Docket1:25-cv-06033
StatusUnknown

This text of Jay Lewis Farrow v. John Does, 1-20 (Jay Lewis Farrow v. John Does, 1-20) is published on Counsel Stack Legal Research, covering District Court, E.D. New York primary law. Counsel Stack provides free access to over 12 million legal documents including statutes, case law, regulations, and constitutions.

Bluebook
Jay Lewis Farrow v. John Does, 1-20, (E.D.N.Y. 2025).

Opinion

UNITED STATES DISTRICT COURT EASTERN DISTRICT OF NEW YORK --------------------------------------------------------------- X : JAY LEWIS FARROW, : Plaintiff, : MEMORANDUM AND ORDER

– against – : 25-CV-6033 (AMD) (PK) : JOHN DOES, 1-20, : Defendants. : --------------------------------------------------------------- X

A NN M. DONNELLY, United States District Judge: On October 28, 2025, the plaintiff, a Florida re sident and suspended attorney,1 filed this

action against 20 John Does alleging violations of the Computer Fraud and Abuse Act, 18 U.S.C.

§ 1030, the Electronic Communications Privacy Act, 1 8 U.S.C. § 2701, the Racketeer Influenced and Corrupt Organizations Act, 18 U.S.C. § 1962 (“Fe deral RICO Act”), Florida’s Racketeer

Influenced and Corrupt Organization Act, Fla. Stat. § 895.02 et seq. (“Florida’s RICO Act”), and

the All-Writs Act, 28 U.S.C. § 1651. (ECF No. 1.) Along with the complaint, the plaintiff filed an ex parte motion for a temporary restraining order and preliminary injunction, as well as a motion to seal the case. (ECF Nos. 2, 3.) For the reasons below, the plaintiff’s motions are denied. BACKGROUND The plaintiff initiated this action purportedly to stop a “years-long and ongoing Advanced Persistent Threat [] cyberattack targeting the legal system and those who operate within it.”

1 See https://www.floridabar.org/directories/find-mbr/profile/?num=625213 (last visited Nov. 4, 2025). The plaintiff is also a member of the New York bar. (ECF No. 1 ¶ 4.) (ECF No. 1 at 1.) The plaintiff asserts that the defendants — whose identities are unknown — are “sophisticated threat actors who have spent years infiltrating court networks, e-filing portals, law firm systems, and related digital infrastructure in order to sabotage active courts proceedings and undermine the administration of justice.” (Id.) He alleges that the defendants’ “tactics

include hijacking official court communications, manipulating electronic filings, and even threatening physical harm to coerce and intimidate” him. (Id.) These defendants “first infiltrated” his law firm network “no later than 2019,” and despite his efforts to remedy the issues, “repeatedly re-established footholds.” (Id. ¶ 17.) “[E]ssentially all” of the plaintiff’s “digital assets” were compromised, including “email accounts, cloud storage, and case management systems.” (Id. ¶¶ 19–20.) The plaintiff asserts that the defendants “manipulate[d] litigation proceedings that [he] was involved in, both as an attorney for clients and as a litigant himself,” and “built a parallel shadow network atop the legitimate judicial system – intercepting and altering communications and filings to engineer outcomes they desired.” (Id. ¶ 23.) The plaintiff conducted a “forensic investigation,” which “uncovered extensive overlaps

between the infrastructure used against him and the infrastructure identified in prior federal cyber crime cases.” (Id. ¶ 30.) He says that “many of the same Internet domain names and IP addresses that appear in [his] network logs and malware configuration files also appeared in court filings and evidence from those earlier cases.” (Id. ¶ 31.) In particular, he claims that the defendants in this case are “part of the same threat ecosystem” as the defendants in Microsoft Corp. v. Does 1-2, No. 23-CV-2447, 2023 WL 11984986 (E.D.N.Y. Apr. 19, 2023). (Id. ¶ 33.) There, the court issued a temporary restraining order, and later a preliminary injunction, to prevent John Doe defendants from using a proprietary software that infringed on the plaintiffs’ copyrights. Microsoft Corp., 2023 WL 11984986, at *2–3. The plaintiff relies on declarations from Microsoft Corp., and says that “many of [the] IP addresses” the experts in Microsoft Corp. identified “later showed up communicating with Plaintiff’s own systems.” (Id. ¶ 32.)2 The plaintiff also relies on a “December 5, 2024 Marlin Forensics Report” and “October 22, 2025 Cyber-N.E.T. Forensics (“CNF”) Expert Report,” which he says “corroborate the technical underpinnings of Defendants’ scheme.” (Id. ¶ 33.)3

The plaintiff also filed a “Declaration of Cyber-N.E.T Forensics Expert Forensic Team,” in which he is the declarant;4 he says his relevant experience includes being an “Expert Team Member and Associate of Cyber-N.E.T. Forensics,” “strategic associate and/or asset of the Joint Cyber Defense Collaborate,” “Chief Technology Officer of Farrow Law,” and the “Director of Incident Responses.” (ECF No. 2-2 ¶¶ 2–4.) He maintains that he worked with the “Marlin Technologies” and “CNF’s Team” “with respect to the preparation of each of their respective Reports” and that he “was present for each individual and independent extraction of files, artifacts and inspections of each of the computer endpoint machines.” (Id. ¶¶ 11–12.) He also claims to have met with the law firm that represented Microsoft in Microsoft Corp. (Id. ¶¶ 27–

2 The plaintiff bases his claim that venue is proper in this district on the Microsoft Corp.’s expert findings that the conduct in that case “spanned across various locations, including multiple nodes within this District.” (ECF No. 1 ¶ 32; see also id. ¶ 11 (“Venue is proper in the Eastern District of New York” because the defendants “made use of instrumentalities located in this District (including New York- based servers, domain registries, and networks) to carry out the acts alleged herein”).) But merely citing an expert’s conclusions in an entirely different case is not sufficient to show that the defendants in this case operate in this District, let alone the state of New York. Nor is the fact that the plaintiff is admitted to practice in New York state enough to establish venue. Even if it were, the plaintiff does not allege any connection to this District; he says only that he has “represented Clients residing in Putnam County,” which is not in this District, “with respect to their property interests in other parts of New York State, and with respect to business transactional matters relative to starting or joining business in New York State. And/or in Florida.” (ECF No. 2-1 ¶ 195.) The plaintiff is a Florida resident, and almost all of his allegations relate to his Florida bar disciplinary proceeding and his law practice in Florida. Thus, venue is almost certainly not proper in this District. 3 The plaintiff says that these reports were “concurrently filed” with his motion but they do not appear on the docket. Rather, the plaintiff cites and summarizes these reports in his complaint, motion, and declaration. 4 The plaintiff does not identify the other team members. 29.) Based on this experience, he “develop[ed] the method and means of extracting data from approximately 150 lawsuits, court filings, pdf documents, email header metadata, and tracking the same” and has become familiar with the “threat actor defendants who are the subject of this lawsuit and . . . highly likely to be the same group and/or some of the same individuals who

comprise the John Doe defendants” in Microsoft Corp. v. Does 1-2. (Id. ¶¶ 37, 48.) The plaintiff also filed an affidavit in support of his motion detailing the defendants’ supposed impact on the plaintiff’s disciplinary proceeding in Florida, which resulted in the plaintiff’s Florida bar license being suspended. (ECF No.

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

Related

Coppedge v. United States
369 U.S. 438 (Supreme Court, 1962)
Salinger v. Colting
607 F.3d 68 (Second Circuit, 2010)
Tracy v. Freshwater
623 F.3d 90 (Second Circuit, 2010)
Jayaraj v. Scappini
66 F.3d 36 (Second Circuit, 1995)
Hartford Courant Co. v. Pellegrino
380 F.3d 83 (Second Circuit, 2004)
Lugosch v. Pyramid Co. of Onondaga
435 F.3d 110 (Second Circuit, 2006)
Parent v. New York
485 F. App'x 500 (Second Circuit, 2012)
Mazurek v. Armstrong
520 U.S. 968 (Supreme Court, 1997)
United States v. Pierce
649 F. App'x 117 (Second Circuit, 2016)
Free Country Ltd. v. Drennen
235 F. Supp. 3d 559 (S.D. New York, 2016)
JBR, Inc. v. Keurig Green Mountain, Inc.
618 F. App'x 31 (Second Circuit, 2016)

Cite This Page — Counsel Stack

Bluebook (online)
Jay Lewis Farrow v. John Does, 1-20, Counsel Stack Legal Research, https://law.counselstack.com/opinion/jay-lewis-farrow-v-john-does-1-20-nyed-2025.