Dark Reading is part of the Informa Tech Division of Informa PLC

This site is operated by a business or businesses owned by Informa PLC and all copyright resides with them.Informa PLC's registered office is 5 Howick Place, London SW1P 1WG. Registered in England and Wales. Number 8860726.

Attacks/Breaches

4/17/2013
11:56 AM
50%
50%

Schnucks Grocery Store Hack Details Emerge

The malware attack exposed approximately 2.4 million credit and debit cards used at 79 of the company's grocery stores

More details have emerged about a hack impacting the Schnucks grocery store chain that compromised as many as 2.4 million credit and debit cards.

According to the company, only the numbers and expiration dates of the credit and debit cards could have been accessed, and no other customer data -- such as names and addresses -- was taken. So far, the investigation has determined that the attackers got their hands on cards used between December 2012 and March 29, 2013, at 79 of the company's more than 90 stores.

The situation came to the company's attention March 15 when a credit card processor noticed that 12 cards used at Schnucks stores had been used to commit fraud. The company immediately began to investigate, ruling out employee misconduct and any tampering with point-of-sale devices.

By March 19, more incidents of fraud were reported, prompting Schnucks to organize an incident response team. The company commissioned Mandiant to help with its investigation and the following day contacted law enforcement. On March 28, Mandiant identified the malware used by the attackers; in the next two days, Schnucks implemented a containment plan and admitted the attack.

"We've worked hard to provide a secure transaction environment for our customers and, today I make a personal pledge to you that we will be relentless in maintaining the security of our payment processing system," said Schnucks CEO Scott Schnuck, in a statement. "We expect that the actions we have taken and will take in the future will send a clear signal that our customers may continue to trust us."

The company has worked with the payment processor to make sure any card numbers potentially affected were sent to the credit card companies so that they may send alerts to the issuing banks, according to the grocery store chain.

"While PCI-DSS has helped protect merchant environments through security requirements and audits, it is usually difficult to provide perfect security," says Jose Diaz, director of technical and strategic business development at Thales e-Security. "PCI-DSS and best practices can help mitigate risk but not necessarily completely eliminate it due to the complexity of some environments.

"One of the approaches to improve a security posture is to scope reduction. If the sensitive data in merchant environments can be isolated, it will be much easier to protect. Attempting to protect complete IT infrastructures can be a very complex task."

Schnucks contacted the Secret Service and FBI about the incident.

"On behalf of myself, the Schnuck family, and all of our 15,000 teammates, I apologize to everyone affected by this incident," Schnuck said. "Over the years, technology has helped us deliver superior customer service, but it also introduces risks that we have actively worked to manage through compliance audits, encryption technology and various other security measures."

Have a comment on this story? Please click "Add Your Comment" below. If you'd like to contact Dark Reading's editors directly, send us a message. Brian Prince is a freelance writer for a number of IT security-focused publications. Prior to becoming a freelance reporter, he worked at eWEEK for five years covering not only security, but also a variety of other subjects in the tech industry. Before that, he worked as a ... View Full Bio

Comment  | 
Print  | 
More Insights
Comments
Newest First  |  Oldest First  |  Threaded View
yadavvivi
50%
50%
yadavvivi,
User Rank: Apprentice
7/27/2013 | 4:06:06 PM
re: Schnucks Grocery Store Hack Details Emerge
i want some cards or account number and sort code
The Cold Truth about Cyber Insurance
Chris Kennedy, CISO & VP Customer Success, AttackIQ,  11/7/2019
Why Cyber-Risk Is a C-Suite Issue
Marc Wilczek, Digital Strategist & CIO Advisor,  11/12/2019
6 Small-Business Password Managers
Curtis Franklin Jr., Senior Editor at Dark Reading,  11/8/2019
Register for Dark Reading Newsletters
White Papers
Video
Cartoon Contest
Current Issue
7 Threats & Disruptive Forces Changing the Face of Cybersecurity
This Dark Reading Tech Digest gives an in-depth look at the biggest emerging threats and disruptive forces that are changing the face of cybersecurity today.
Flash Poll
Rethinking Enterprise Data Defense
Rethinking Enterprise Data Defense
Frustrated with recurring intrusions and breaches, cybersecurity professionals are questioning some of the industrys conventional wisdom. Heres a look at what theyre thinking about.
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2019-16863
PUBLISHED: 2019-11-14
STMicroelectronics ST33TPHF2ESPI TPM devices before 2019-09-12 allow attackers to extract the ECDSA private key via a side-channel timing attack because ECDSA scalar multiplication is mishandled, aka TPM-FAIL.
CVE-2019-18949
PUBLISHED: 2019-11-14
SnowHaze before 2.6.6 is sometimes too late to honor a per-site JavaScript blocking setting, which leads to unintended JavaScript execution via a chain of webpage redirections targeted to the user's browser configuration.
CVE-2011-1930
PUBLISHED: 2019-11-14
In klibc 1.5.20 and 1.5.21, the DHCP options written by ipconfig to /tmp/net-$DEVICE.conf are not properly escaped. This may allow a remote attacker to send a specially crafted DHCP reply which could execute arbitrary code with the privileges of any process which sources DHCP options.
CVE-2011-1145
PUBLISHED: 2019-11-14
The SQLDriverConnect() function in unixODBC before 2.2.14p2 have a possible buffer overflow condition when specifying a large value for SAVEFILE parameter in the connection string.
CVE-2011-1488
PUBLISHED: 2019-11-14
A memory leak in rsyslog before 5.7.6 was found in the way deamon processed log messages are logged when $RepeatedMsgReduction was enabled. A local attacker could use this flaw to cause a denial of the rsyslogd daemon service by crashing the service via a sequence of repeated log messages sent withi...