Former Goldman Programmer Faces New Charges

A Russian-born computer programmer who formerly worked for Goldman Sachs has rejected a plea deal that would have spared him jail time for allegedly stealing top-secret, high-frequency trading software from the investment firm.

Sergey Aleynikov, 42, was indicted Thursday in New York State criminal court on felony charges of accessing and duplicating "highly confidential" source code from Goldman Sachs, according to the office of Manhattan district attorney Cyrus Vance.

"The code is so highly confidential that it is known in the industry as the firm's 'secret sauce,'" said Vance, in a statement. "Employees who exploit their access to sensitive information should expect to face criminal prosecution in New York State in appropriate cases."

Aleynikov was previously convicted in federal court on similar charges, but his conviction was overturned by the 2nd Circuit Court of Appeals after he had served a year in jail. Aleynikov's attorney said he plans to seek dismissal of the state charges, which he contends put his client in double jeopardy.

"The precise factual circumstances that underlie these charges have already been fully adjudicated," attorney Kevin Marino told the court, according to Reuters. "There's nothing remotely lawful or constitutional about what's going on … he left Russia for freedom and the American way, and he got Franz Kafka and Goldman Sachs."

Aleynikov holds dual U.S.-Russian citizenship. The programmer joined Goldman Sachs in May 2007 and was paid an annual salary of $400,000, according to records. Formally, he's been charged by Vance's office with one count of unlawful use of secret scientific material, and one count of duplication of computer-related material.

"His job responsibilities included developing and maintaining computer programs used to operate the bank's high-frequency trading systems, which allowed Goldman Sachs traders to make a large volume of trades in securities, commodities, and options," said Vance's office. "Goldman Sachs' programmers created its high-frequency trading system to maintain a competitive advantage."

Aleynikov was first apprehended on the federal charges in 2009, after Goldman Sachs noticed large amounts of data being uploaded from its servers via HTTPS transfers. The uploads, 32 MB in total, were ultimately traced to Aleynikov's workstation, federal authorities charged.

Aleynikov faces up to four years in prison if he is convicted on the state charges.

New York State senior investigative counsel Joanne Y. Li is prosecuting the case under the supervision of assistant district attorney David Szuchman, chief of the Cybercrime and Identity Theft Bureau. Supervising rackets Investigator Robert Muldoon, senior rackets investigator Jason Malone, senior cybercrime analyst Jeremy Apple, and cybercrime analyst Bret Rubin also assisted in the investigation, according to Vance's office.

Web-facing databases have a huge target on their backs. The easy way to secure these databases would be to take them off the Web, but a system that does not serve a business function is worthless to the company. Security pros must figure out ways to secure databases with limited resources while keeping business systems operational. In the Strategies For Protecting Web-Facing Databases report, we recommend several cost-efficient methods. (Free registration required.)

That is all good and great but what about the double jeopardy factor? Are they the same charges that he was already cleared of or are they completely separate incidents. IT looks like Aleynikov feels that he will get off scott free, or he would have taken the year in prison as compare dot the 4 he could face if convicted. I wonder what Vance meant when he stated Gǣ"Employees who exploit their access to sensitive information should expect to face criminal prosecution in New York State in appropriate cases.", What are appropriate cases?

Published: 2015-03-31The build_index_from_tree function in index.py in Dulwich before 0.9.9 allows remote attackers to execute arbitrary code via a commit with a directory path starting with .git/, which is not properly handled when checking out a working tree.