Google LLC v. Dmitry Starovikov

District Court, S.D. New York·Decided November 15, 2022·No. 1:21-cv-10260·Unknown

Opinion

UNITED STATES DISTRICT COURT SOUTHERN DISTRICT OF NEW YORK -------------------------------------- X : GOOGLE LLC, : : Plaintiff, : : 2 1 c v 1 0 2 6 0 (DLC) -v- : : OPINION AND ORDER DMITRY STAROVIKOV, ALEXANDER FILIPPOV, : and DOES 1–15, : : Defendants. : : -------------------------------------- X APPEARANCES: For plaintiff: Andrew Zenner Michaelson Kathleen Elizabeth McCarthy Laura Elizabeth Harris King & Spaulding LLP (NYC) 1185 Avenue of the Americas New York, NY 10036

Bethany Rupert King & Spalding 1180 Peachtree Street NE Atlanta, GA 30309

David Paul Mattern Sumon Dantiki King & Spalding LLP (DC) 1700 Pennsylvania Avenue, N.W. Washington, DC 20006

For Defendants: Igor B. Litvak The Litvak Law Firm, PLLC 1733 Sheepshead Bay Road Suite 22 Brooklyn, NY 11235 DENISE COTE, District Judge: Google LLC (“Google”) has brought claims against the defendants for operating a botnet to steal and exploit Google

users’ personal information. Dmitry Starovikov and Alexander Filippov, the two named individual defendants (the “Defendants”) failed to timely appear in this action, and after their default was vacated, produced almost no discovery. The Defendants assert that the discovery Google requests is held by their former employer, Valtron LLC (“Valtron”), which Google alleges operated many of the Defendants’ criminal schemes. Google contends that the Defendants misrepresented their relationship with Valtron to this Court and to Google, and that the Defendants spoliated critical evidence. Google has filed a motion for sanctions, in the form of monetary sanctions and entry of a default judgment, against Dmitry Starovikov,

Alexander Filippov, and sanctions against their attorney, Igor Litvak. The Defendants have cross-moved for sanctions. For the following reasons, Google’s motion is granted, and the Defendants’ motion is denied. Background This Court presumes familiarity with its prior Opinions in this action. See Google LLC v. Starovikov, 21CV10260, 2022 WL 1239656 (S.D.N.Y. Apr. 27, 2022) (vacating the entry of default); Google LLC v. Starovikov, 21CV10260, 2022 WL 4592899 (S.D.N.Y. Sept. 30, 2022) (issuing default judgment against defendants Does 1–15). The complaint alleges that the Defendants control the Glupteba botnet, a network of private

computers infected with malware. This malware hijacks the infected computers, instructing them to execute commands issued by a command-and-control server (also called a “C2 server”), which controls the computers that are part of the botnet. Conventional botnets receive instructions from C2 servers whose domains or IP addresses are hardcoded in the botnet malware. This means that a conventional botnet can be disabled by taking the server at the hardcoded address offline. The Glupteba malware, however, instructs infected computers to look for the addresses of its C2 servers by referencing transactions associated with specific accounts on the Bitcoin blockchain. The blockchain is not controlled by any central authority, and

each transaction is disseminated to and viewable by any user on the blockchain. These features make the Glupteba botnet unusually resistant to disruption. If the botnet's C2 servers are disabled, then its operators can simply set up new servers and broadcast their addresses on the blockchain. Google alleges that the Defendants use the Glupteba botnet to further several unlawful schemes (collectively, the “Glupteba Enterprise”). In particular, the Defendants use the botnet to harvest personal and financial information from the infected computers, which they then sell; the Defendants use the botnet to place disruptive ads on the infected computers; the Defendants use the infected computers to mine cryptocurrency;

and the Defendants use the infected computers as proxies, directing third-party internet traffic through the infected computers to disguise the origin of the traffic. The Defendants operate these criminal schemes through various corporate entities, including Valtron. Google also alleges that Starovikov and Filippov used some of the botnet’s C2 servers when signing up for their own Google accounts, that they operate the botnet, and that they acted as administrators for Valtron’s Google Workspace account. Google filed the present lawsuit on December 2, 2021, bringing claims for violation of the Racketeer Influenced and Corrupt Organizations Act, the Computer Fraud and Abuse Act, the

Electronic Communications Privacy Act, trademark and unfair competition law, and for tortious interference with a business relationship and unjust enrichment. Along with the complaint, Google requested a temporary restraining order enjoining the defendants from their alleged unlawful activities, and permitting Google to request that entities providing services to domains and IP addresses associated with the Glupteba botnet take reasonable best efforts to disrupt the botnet. The temporary restraining order was issued on December 7, granting the requested relief, and authorizing Google to use alternative service “via mail, email, text, and/or service through ICANN.” The temporary restraining order was converted into a preliminary

injunction on December 16 after no defendant made an appearance to challenge it. A. The Defendants’ Default On February 7, 2022, Google requested an entry of default from the Clerk of Court against Defendants Starovikov and Filippov, describing their efforts on December 8 through 10 to serve the Defendants by the methods authorized in the temporary restraining order. Default was entered by the Clerk of Court against them on February 8. An Order of February 1 required Google to move for entry of a default 21 days thereafter. On February 24, Litvak submitted a letter requesting that the February 1 Order be suspended, and proposed a schedule for filing a motion to vacate the default entered against the two

Defendants. The schedule for the motion was set at a conference held on March 1. At the March 1 conference, Litvak represented that the Defendants had never received notice of the action, and that they only found out about it from their friends toward the end of January. Google argued that the Defendants had received notice, however, because they had actively set up new C2 servers after Google had taken the previous ones offline. Google explained that the Defendants would have known when the original C2 servers were taken offline, because they had used the IP addresses associated with those servers when signing up for their Google accounts.

On March 14, the Defendants submitted a motion to vacate the default, arguing that they had not been served, that the Court lacked jurisdiction over them, and that they had meritorious defenses, including that Google had failed to state a claim against them. In support of their motion, the Defendants submitted nearly identical signed declarations, each of which stated: “I work for Valtron LLC as a software engineer.” The declarations also asserted that the Defendants had never received service of process, and did not receive actual notice of the action until late January, when they heard about it from “friends.” Google submitted a cross-motion for default judgment against the Defendants on March 25, arguing

that the Defendants had agreed to waive personal jurisdiction in their discussions with Google, and that they had no other meritorious defenses. The motions became fully submitted on April 19. In an Opinion of April 27, this Court denied Google’s motion for default judgment and vacated the entry of default against the Defendants.1 See id. at *10. Although the Opinion

1 Google’s request for default judgment was also denied with respect to Does 1–15, because the certificate of default did not found it “improbable” that “all of Google’s attempts at service . . .

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

Google LLC v. Dmitry Starovikov, (S.D.N.Y. 2022).

Google LLC v. Dmitry Starovikov (Google LLC v. Dmitry Starovikov) — published by Counsel Stack Legal Research, free access to 12M+ legal documents.

Related