JCPenney’s Breach: Differences From Feds, Gonzalez, JCPenney Itself

Written by Evan Schuman
April 1st, 2010

In November 2007, Albert Gonzalez’s crew was in the midst of hitting their laundry list of major retailers when they used their SQL attack on JCPenney. But just how deep they penetrated the $18 billion clothing chain is unclear, with the Justice Department, JCPenney and intercepted messages from Gonzalez IM conversations all painting very different pictures.

Gonzalez has pleaded guilty to placing a file called sqlz.txt—contained information from JCPenney’s network—on a Ukrainian server. Assistant U.S. Attorney Stephen Heymann said the government wasn’t sure what Gonzalez’s team got from JCPenney: “Although the protective system used by JCPenney had unquestioningly failed, the Secret Service had no evidence as to whether payment card numbers had been stolen.”

As for Gonzalez’s comments at the time, a series of ICQ messages in November and December 2007 gave some hints of the perceptions—at that time—of the cyberthieves. A Nov. 1 exchange said they were searching for weak passwords at the chain and that access wasn’t difficult: “They have most of (their) ports open. Wasn’t too hard.”

On Dec. 16, Gonzalez then asked his associate: “I’m curious how Hacker 2 moved around on jcp so quickly w/o making noise” and he was told “SQL Servers is his key to everything. Heh.” On Christmas Eve, Gonzalez declared “I got access to the JCP POS network.”

The government now says that Secret Service agents alerted JCPenney in May 2008 “that it had been attacked in or about October 2007. Prior to receiving that alert, (JCPenney) was wholly unaware that it had been previously victimized by computer hackers.”

(Lawyers and a federal judge go a few rounds over trying to keep JCPenney’s name out of the case. The Judge wins.)

Side note from various federal documents that were unsealed this week: If anyone had been trying to visit 7-Eleven’s site on Nov. 9, 2007, they would have discovered the site down. But it wasn’t a software glitch or excessive traffic. It was the convenience store chain’s attempt to block Gonzalez’s attack. “7-Eleven disabled its public-facing Internet site to disrupt the unauthorized access,” the government filing disclosed.

Back to JCPenney. The chain’s version of its attack is that credit cards were indeed taken, but only two of them, and both were the chain’s own branded cards. Most importantly, though, when the cyberthieves thought they had broken into JCPenney’s centralized POS database, they had actually penetrated something much less valuable: “The hackers did not access JCPenney’s POS network, as was assumed by the hackers in their chatter, but rather a POS server in a single store, where they retrieved two private label credit cards,” said Darcie M. Brossart, VP for corporate communications at JCPenney.

Brossart said the chain considers none of the data to have ever been at risk, given that the thieves never got close to the core payment card systems. “They had been in the system but they weren’t getting anywhere. They were nowhere near the POS system, they were nowhere near penetrating actual customer databases,” she said. “There was never a risk of customer information being revealed.”

“Based upon the detailed forensic investigation that was completed on JCPenney’s systems, we know exactly the methods employed to gain access into our system, the tools used and the probes conducted against machines in our network,” Brossart said. “Our assumption is that once the hackers accessed the SQL server, the complexity of our network and its set-up, made it extremely difficult for them to compromise data.”


Comments are closed.


StorefrontBacktalk delivers the latest retail technology news & analysis. Join more than 17,000 retail IT leaders who subscribe to our free weekly email. Sign up today!
Our apologies. Due to legal and security copyright issues, we can't facilitate the printing of Premium Content. If you absolutely need a hard copy, please contact customer service.