The Hannaford and Heartland breaches of 2008 and 2009 changed card security because they proved that a company could pass a PCI compliance assessment and still lose millions of card numbers. In both cases, attackers did not raid a database of stored cards. They planted malware that copied card data while it was moving through internal networks for authorization. That single lesson pushed the payments industry toward encrypting card data from the moment of the swipe, replacing card numbers with tokens, and moving the United States onto chip cards, changes that still define how card payments are protected in 2026.

Key takeaways

  • Hannaford disclosed in March 2008 that malware on its store servers had exposed 4.2 million card numbers, with about 1,800 fraud cases linked to the theft.
  • Heartland disclosed on 20 January 2009 that attackers had been inside its processing network for months; data from more than 130 million cards was taken.
  • Both companies had been assessed as PCI compliant, because the rules at the time did not require encryption of card data on private internal networks.
  • The same hacking ring, led by Albert Gonzalez, was behind both attacks; he was sentenced to 20 years in prison in March 2010.
  • The response shaped modern payments: end-to-end and point-to-point encryption, tokenization, the 2015 US chip liability shift and a sharper focus on data in transit.

What happened at Hannaford in 2008?

Hannaford Bros., a supermarket chain based in Scarborough, Maine, announced on 17 March 2008 that card data from its checkout lanes had been stolen. The company said about 4.2 million credit and debit card numbers had been exposed and roughly 1,800 cases of fraud had already been reported. The theft affected all 165 Hannaford stores in New England and New York, 106 stores of its sister chain Sweetbay in Florida and some independent grocers supplied by Hannaford, and ran from early December 2007 until 10 March 2008.

What shocked the industry was how it was done. Investigators found malware on servers in the stores that captured card numbers as they traveled from the card-swipe PIN pad across the company's private network to its central payment switch, according to Supermarket News' account of the breach. The malware then sent the stolen numbers in batches over the internet to an offshore internet provider. Only card numbers and expiry dates were taken; no names or addresses were involved.

Hannaford had been certified as compliant with the PCI Data Security Standard, and it was recertified on 27 February 2008, while the breach was still running. It became one of the first publicly known breaches of a PCI-compliant merchant. The gap was simple: PCI required encryption of card data sent over public networks, but not over a company's own private network, and that internal hop was exactly where the malware sat.

How did the Heartland breach unfold?

Heartland Payment Systems, then the fifth-largest card processor in the United States, announced on 20 January 2009, the day of a presidential inauguration, that it had been the victim of a breach inside its processing system during 2008. The intrusion had started much earlier. Attackers first got in through a SQL injection flaw in a web-facing application in late 2007, then spent months moving through the network before installing sniffer software that captured card data as it passed through Heartland's processing platform.

The scale was unprecedented. The US Justice Department's indictment in August 2009 alleged that data from more than 130 million credit and debit cards had been stolen, making it the largest card theft ever prosecuted in the United States at the time. Because Heartland processed for hundreds of thousands of merchants, a single compromise at the processor exposed cards used at businesses that had done nothing wrong themselves.

Like Hannaford, Heartland had been assessed as PCI compliant before the attack. Visa removed it from its list of validated service providers after the breach, then restored it on 1 May 2009 once it had revalidated. Heartland put its own losses at between $130 million and $140 million over the following years, including settlements of about $60 million with Visa, $41.4 million with Mastercard and $3.6 million with American Express, according to reporting compiled by Privacy Rights Clearinghouse and IEEE Spectrum.

Who was behind both attacks?

The same group was responsible for both breaches, as well as earlier attacks on TJX, the owner of T.J. Maxx, and other retailers. Its leader, Albert Gonzalez of Miami, had at one point been a Secret Service informant. Prosecutors said the group used SQL injection to get into corporate networks, then installed custom malware to capture card data and pass it to collaborators who sold it or turned it into counterfeit cards.

Gonzalez pleaded guilty and was sentenced on 25 March 2010 to 20 years in federal prison, at the time the longest sentence ever handed down in the US for computer crime. The case did not end there. In February 2018, two Russian co-conspirators, Vladimir Drinkman and Dmitriy Smilianets, were sentenced, with the US Secret Service describing the scheme as the largest data breach ever prosecuted in the United States.

BreachDisclosedCards exposedHow data was takenCompliance status
TJXJanuary 2007About 45.7 millionWeak wireless security, then stored dataNot fully compliant
Hannaford17 March 2008About 4.2 millionMalware capturing data in transit inside storesCertified PCI compliant
Heartland20 January 2009More than 130 millionSQL injection, then sniffer malware on the processing networkAssessed PCI compliant

Why did PCI compliance not stop them?

PCI compliance did not stop either breach because the standard of the time was built mainly around protecting stored card data and data crossing public networks. Attackers adapted. As Gartner analyst John Pescatore told eWeek after the Hannaford breach, hijacking card data in transit was a direct result of large merchants moving sensitive data out of their stores. Once databases were locked down, criminals went to the one place card data still had to appear in readable form: the moment it was being sent for authorization.

The breaches also exposed the limits of a point-in-time assessment. An assessor confirms that controls are in place on the day of the review. It does not prove that nobody is already inside the network, and in Hannaford's case the recertification was signed while the malware was running. That is why today's standard leans on continuous measures, from regular scope confirmation and card data discovery scans to monitoring and incident response that assumes an intruder may already be present.

What changed in card security afterwards?

The response came from processors, card networks and the standards body, and most of it is still in place.

What did the breaches mean for Heartland's future?

Heartland survived and, in the view of many in the industry, became an example of how to respond to a breach. Its chief executive Bob Carr pushed publicly for end-to-end encryption and information sharing among processors. In April 2016, Heartland merged into rival processor Global Payments in a deal that Global Payments' annual report valued at $4.4 billion including assumed debt, adding more than 300,000 merchants and about $130 billion in yearly payment volume.

Where things stand in November 2026

As of November 2026, the protections born from these breaches are mainstream. Chip cards are standard in US stores, contactless and wallet payments rely on tokens and one-time codes rather than reusable card numbers, as our guide to contactless card payments explains, and point-to-point encryption is widely offered by processors. The PCI P2PE standard moved to version 3.2, and from 1 January 2026 all new P2PE product submissions, including reassessments, must meet it.

The core weakness the Hannaford and Heartland attackers exploited has not disappeared, though. Any system where card data appears in readable form, even briefly, is a target. Later breaches at large US retailers used memory-scraping malware on point-of-sale systems that had not yet adopted end-to-end encryption, and online checkout pages are now attacked with skimming scripts that capture card details before they are encrypted. The tools to close these gaps exist; the risk lies with businesses that have not adopted them.

What should businesses take from these cases today?

The practical lesson is to remove readable card data from your environment rather than relying on walls around it. Use a payment terminal or hosted payment page that encrypts or tokenizes card data before it touches your systems, so a compromise of your network yields nothing usable. Treat compliance as a minimum, not proof of safety, and plan for the possibility that an attacker is already inside: monitor for unusual outbound traffic, scan for card data where it should not be, and rehearse how you would respond.

For anyone tracing card fraud on their own accounts, these cases are also a reminder that the business where a card was stolen is rarely the one where it is misused. Hannaford's stolen numbers turned up in fraudulent charges in Mexico, Bulgaria and Italy, far from the grocery aisles where they were captured.

Frequently asked questions

How many cards were stolen in the Heartland breach?

Prosecutors said data from more than 130 million credit and debit cards was stolen in the Heartland breach, which was disclosed on 20 January 2009. It was the largest card data breach ever prosecuted in the United States at the time.

Was Hannaford PCI compliant when it was breached?

Yes. Hannaford had been certified as PCI compliant and was recertified on 27 February 2008, while the breach was still under way. The malware captured data on the company's private network, where PCI did not then require encryption.

Who hacked Heartland and Hannaford?

A hacking ring led by Albert Gonzalez, which also attacked TJX and other retailers. Gonzalez was sentenced to 20 years in prison in March 2010, and two Russian co-conspirators were sentenced in 2018.

Does Heartland Payment Systems still exist?

Heartland became part of Global Payments when the two companies completed their merger in April 2016.

Could a breach like Hannaford's happen today?

It is much harder where point-to-point encryption or tokenization is in place, because card data is never readable on the merchant's network. Businesses that still handle unencrypted card data internally remain exposed to the same kind of in-transit capture.