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
News
Inside the Ransomware Campaigns Targeting Exchange Servers
Kelly Sheridan, Staff Editor, Dark Reading,  4/2/2021
Commentary
Beyond MITRE ATT&CK: The Case for a New Cyber Kill Chain
Rik Turner, Principal Analyst, Infrastructure Solutions, Omdia,  3/30/2021
Register for Dark Reading Newsletters
White Papers
Video
Cartoon
Current Issue
2021 Top Enterprise IT Trends
We've identified the key trends that are poised to impact the IT landscape in 2021. Find out why they're important and how they will affect you today!
Flash Poll
How Enterprises are Developing Secure Applications
How Enterprises are Developing Secure Applications
Recent breaches of third-party apps are driving many organizations to think harder about the security of their off-the-shelf software as they continue to move left in secure software development practices.
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2015-20001
PUBLISHED: 2021-04-11
In the standard library in Rust before 1.2.0, BinaryHeap is not panic-safe. The binary heap is left in an inconsistent state when the comparison of generic elements inside sift_up or sift_down_range panics. This bug leads to a drop of zeroed memory as an arbitrary type, which can result in a memory ...
CVE-2020-36317
PUBLISHED: 2021-04-11
In the standard library in Rust before 1.49.0, String::retain() function has a panic safety problem. It allows creation of a non-UTF-8 Rust string when the provided closure panics. This bug could result in a memory safety violation when other string APIs assume that UTF-8 encoding is used on the sam...
CVE-2020-36318
PUBLISHED: 2021-04-11
In the standard library in Rust before 1.49.0, VecDeque::make_contiguous has a bug that pops the same element more than once under certain condition. This bug could result in a use-after-free or double free.
CVE-2021-28875
PUBLISHED: 2021-04-11
In the standard library in Rust before 1.50.0, read_to_end() does not validate the return value from Read in an unsafe context. This bug could lead to a buffer overflow.
CVE-2021-28876
PUBLISHED: 2021-04-11
In the standard library in Rust before 1.52.0, the Zip implementation has a panic safety issue. It calls __iterator_get_unchecked() more than once for the same index when the underlying iterator panics (in certain conditions). This bug could lead to a memory safety violation due to an unmet safety r...