Welcome Guest. | Log In | Register | Membership Benefits

TJX, Heartland Hacker Hit With A Second 20-Year Prison Sentence

'Cybercrime pusher' Albert Gonzalez today was handed a 20-year prison sentence for his breach of Heartland Payment Systems, 7-Eleven

Mar 26, 2010 | 05:33 PM | 

By Kelly Jackson Higgins

One day after receiving a 20-year sentence for his role in the massive breach at TJX, convicted black-hat hacker Albert Gonzales got hit with another 20-year penalty -- this time for his breach of Heartland Payment Systems, 7-Eleven, and other companies.

But Gonzalez, 28, will serve only a total of 20 years because the latest ruling is concurrent with the first sentence, according to published reports.

Gonzalez's 20-year sentence, announced yesterday in U.S. District Court in Boston for stealing and selling payment card information in his hacking of TJX, BJ's Wholesale Club, OfficeMax, Boston Market, Barnes & Noble, Sports Authority, and Dave & Busters restaurants, was the largest ever levied for a computer crime. It's considered the largest identity theft case ever in the U.S.

But it wasn't the maximum penalty he could have received: Gonzalez faced anywhere from 17 to 25 years behind bars.

Jeffrey Troy, acting deputy assistant director of the FBI's cyber division, says Gonzalez's big sentence was commensurate with the amount of damages the hacks incurred. The FBI's Troy says the outcome of the trial should make an impact on cybercriminals. "Sitting at a computer [and robbing a bank, for instance] should not give anybody an increased level of comfort that they are not going to be pursued by the authorities. They are going to be," Troy says.

In September, Gonzales admitted to the TJX breach, and later plead guilty to stealing data from Heartland Payment Systems, Hannaford Brothers, 7-Eleven, and Target Co.

Federal prosecutors say Gonzalez's crimes in the TJX case cost the companies and insurers nearly $200 million by his actions.

Gonzalez, also known as "segvec," soupnazi," and "j4guar17," conducted most of his dirty deeds during 2005 to 2008 while he served as a paid undercover informant for the U.S. Secret Service. He reportedly was paid a $75,000 salary by the agency. He had called his cybercrime enterprise "Operation Get Rich Or Die Tryin.'" In August, he was indicted, along with two Eastern Europeans for the hacks of Heartland, Hannaford Bros, 7-11, and two retailers who have not yet been revealed. Michael Maloof, CTO at TriGeo Network Security, says he was hoping for a major sentence for Gonzalez. "He was also a supplier, who made the tools and techniques" and sold them to others, Maloof says. "He was a cybercrime pusher and organizer."

But while the sentence should send a message, the Gonzalez case certainly won't be the last, according to Maloof. "I wish I could say crime doesn't pay. So many cybercriminals are not caught," he says. "But anything that might give someone pause so that they think twice before going down this path might help."

Gonzalez and his crew used classic and well-known hacking methods -- namely SQL injection, packet sniffing, and backdoor malware designed to evade detection -- that experts say could have been thwarted.

Specifically, Gonzalez allegedly provided his co-conspirators -- two of whom resided in Russia and another in Virginia Beach, Va. -- with SQL injection strings to use for hacking into the victims' networks. He also provided them with malware to plant inside the victims' systems that would serve as a backdoor for subsequent access. The attackers installed sniffers to capture credit and debit-card numbers and other card data. They wrote malware that could avoid detection by anti-virus software in order to remain under the radar. The stolen data was sent back to servers operated by the suspects that were located in California, Illinois, Latvia, the Netherlands, and Ukraine, according to the indictment.

Have a comment on this story? Please click "Discuss" below. If you'd like to contact Dark Reading's editors directly, send us a message.



Currently we allow the following HTML tags in comments:

Single tags

These tags can be used alone and don't need an ending tag.

<br> Defines a single line break

<hr> Defines a horizontal line

Matching tags

These require an ending tag - e.g. <i>italic text</i>

<a> Defines an anchor

<b> Defines bold text

<big> Defines big text

<blockquote> Defines a long quotation

<caption> Defines a table caption

<cite> Defines a citation

<code> Defines computer code text

<em> Defines emphasized text

<fieldset> Defines a border around elements in a form

<h1> This is heading 1

<h2> This is heading 2

<h3> This is heading 3

<h4> This is heading 4

<h5> This is heading 5

<h6> This is heading 6

<i> Defines italic text

<p> Defines a paragraph

<pre> Defines preformatted text

<q> Defines a short quotation

<samp> Defines sample computer code text

<small> Defines small text

<span> Defines a section in a document

<s> Defines strikethrough text

<strike> Defines strikethrough text

<strong> Defines strong text

<sub> Defines subscripted text

<sup> Defines superscripted text

<u> Defines underlined text

Dark Reading encourages readers to engage in spirited, healthy debate, including taking us to task. However, Dark Reading moderates all comments posted to our site, and reserves the right to modify or remove any content that it determines to be derogatory, offensive, inflammatory, vulgar, irrelevant/off-topic, racist or obvious marketing/SPAM. Dark Reading further reserves the right to disable the profile of any commenter participating in said activities.

Disqus Tips To upload an avatar photo, first complete your Disqus profile. | View the list of supported HTML tags you can use to style comments. | Please read our commenting policy.
Subscribe to RSS



Database Security Reports

report Securing The Data Warehouse
Many enterprises are building data warehouses to centralize the ever-increasing information flowing through their organizations into useful repositories. This makes good business sense, but it opens up a slew of concerns from a security standpoint. IT professionals can apply many of the same security best practices used with databases, but there are new lessons to be learned as well.

report Defend Your Data From Malicious Insiders
The biggest threat to your company?s most sensitive data may be the employee who has legitimate access to corporate databases but less-than-legitimate intentions. And while the incidence of insider data breaches has decreased, external attacks often imitate them--and do serious damage. Follow our advice to mitigate the risk.

report Ensuring Secure Database Access
Role-based access control based on least user privilege is one of the most effective ways to prevent the compromise of corporate data. But proper provisioning is a growing challenging, due to the proliferation of "big data," NoSQLdatabases, and cloud-based data storage.

Other reports from the Database Security Tech Center:

Related Content

Establishing a Strategy for Database Security is No Longer Optional
As databases continue to grow in size, complexity and importance, enterprises struggle to identify the most appropriate controls regarding their use and misuse. The report identifies best practices, including: Implementing database activity monitoring to mitigate the high levels of risk from database vulnerabilities, and address audit findings in areas such as database segregation of duties and change management; using data security measures, such as data masking and data encryption; and monitoring privileged-user access and access to critical data.

Database Activity Monitoring Is Evolving Into Database Audit and Protection
In this report, Gartner writes that "Database audit and protection (DAP) represents an evolutionary advance in database activity monitoring tools." DAP suites provide comprehensive, cross-platform support in heterogeneous database environments to protect sensitive data from inappropriate use. Organizations are increasingly concerned with optimizing database security and mitigating risks associated with database vulnerabilities.

Protecting Against Database Attacks and Insider Threats: Top 5 Scenarios
Data security presents a multi-dimensional challenge in today's complex IT environment. Multiple access paths and permission levels have resulted in a broad array of security threats and vulnerabilities. We invite you to read this new eBook: "Protecting against database attacks and insider threats" to learn the top five scenarios and essential best practices for preventing database attacks and insider threats.

Demo: Distributed Database Security with Real-time Monitoring and Audit Protection
Organizations across the globe continue to experience compromised data caused by malicious attacks, web application vulnerabilities or unauthorized changes. View this demo and learn how IBM InfoSphere Guardium? database activity monitoring can help protect your sensitive data in distributed DBMS environments with a holistic approach to data security and compliance.

Look Beyond Native Database Auditing To Improve Security, Audit Visibility, And Real-Time Protection
Today's attacks on enterprise databases are more sophisticated than ever, and they occur so fast that it's often difficult to stop them in real time. Despite significant efforts to protect enterprise databases, the number of records breached has grown each year - due to all types of internal and external attacks and violations of corporate policy.




Featured Webcasts
Featured Whitepapers
Featured Reports