Russian man pleads guilty in US to role in hacking scheme that targeted JPMorgan

Andrei Tyurin, 36, pleaded guilty in Manhattan federal court to six counts


Reuters September 24, 2019
Rep image. PHOTO: AFP

SEOUL: A Russian man pleaded guilty on Monday to US charges he took part in a massive computer hacking scheme that targeted JPMorgan Chase & Co and other financial services companies.

Andrei Tyurin, 36, pleaded guilty in Manhattan federal court to six counts including wire fraud and computer hacking conspiracy, admitting that he illegally obtained the personal information of the companies’ customers to find potential victims for fraudulent investment schemes.

He is scheduled to be sentenced on February 13 by US District Judge Laura Taylor Swain in Manhattan. He has agreed to forfeit more than $19 million as part of his plea.

Once hacked, twice shy: How auto supplier Harman learned to fight cyber carjackers

His lawyer, Florian Miedel, declined to comment on the case.

Tyurin was arrested in the country of Georgia at the request of US authorities last year, the latest of several people to be charged with taking part in the scheme.

JPMorgan disclosed that it had been hacked in 2014, saying it had exposed information associated with about 83 million customer accounts.

Other victims included E*Trade Financial Corp, Scottrade and News Corp’s Dow Jones & Co, publisher of the Wall Street Journal. Prosecutors said a total of more than 100 million customers of the hacked companies were affected.

Google reveals some malicious websites have been ‘quietly’ hacking into iPhones

Prosecutors had previously charged two Israeli citizens, Gery Shalon and Ziv Orenstein, along with an American resident of Israel, Joshua Samuel Aaron, in connection with the scheme.

Members of the conspiracy made hundreds of millions of dollars through criminal schemes using stolen information, prosecutors said.

 

COMMENTS

Replying to X

Comments are moderated and generally will be posted if they are on-topic and not abusive.

For more information, please see our Comments FAQ