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

Heartland Struggles To Measure Extent Of Massive Security Breach

Data breach could be industry's biggest ever, experts say

In what some experts are calling the largest security breach ever, Heartland Payment Systems yesterday disclosed that intruders hacked into the computers it uses to process 100 million payment card transactions per month for 175,000 merchants.

Robert Baldwin, Heartland's president and CFO, told reporters that the intruders had access to Heartland's system for "longer than weeks" in late 2008. The number of victims is unknown. "We just don't have the information right now," Baldwin said.

Tech security experts say the breach could surpass the record set by retail giant TJX, which lost 94 million customer records to hackers in 2007. With more than 100 million transactions per month, Heartland could discover that several months' worth of transactions were captured, says Michael Maloof, chief technology officer at TriGeo Network Security.

Heartland processes card payments for restaurants, retailers, and other merchants. It discovered the hack last week after Visa and MasterCard notified it of suspicious transactions stemming from accounts linked to its systems. Investigators then found the data-stealing program planted by the thieves.

"Our discussions with the Secret Service and Department of Justice give us a pretty good indication that this is part of a group that appears to have done security breaches at other financial institutions," Baldwin said. "This is a very sophisticated attack."

According to published reports, attackers managed to slip keylogger and sniffer programs onto the network, enabling them to record keystrokes and collect unencrypted data in transit. Most of the lost data is probably credit card numbers, names, and expiration dates, which could be used to create counterfeit cards, experts say.

Several reports indicate that Heartland had complied with Payment Card Industry (PCI) security standards and was using strong encryption, but the keylogger collected the data before it was encrypted. Some reports indicate that the breach began as early as May 2008, and may have been detected months ago.

Experts say the keylogger attack might have gone undetected even if Heartland was using a variety of off-the-shelf security tools. "Most security technologies in use today are about looking for the explicitly -- and in most cases already known to be -- bad. And that leaves a lot of room for error," says Chris King, director of strategic marketing at firewall vendor Palo Alto Networks.

Once it sorts out the matter, Heartland plans to notify each victim in compliance with data-loss disclosure laws in more than 30 states, he says.

"It is quite unlikely they will be able to confidently determine whose data was lost," says Michael Argast, senior security analyst at Sophos. "If they have great logging, it is possible, but the nature of any compromise makes it difficult to have assurance on the event. At worst, it could be every customer who has used their infrastructure since the breach. "The reality is cleaning up the mess could be potentially much more expensive than any fines or penalties. For example, issuing a new card costs around $30. Multiplied by 100 million cards, $3 billion is much more than the scope of any fines. In reality, that could bankrupt the business."

Heartland's disclosure coincides with reports of heightened criminal activities involving stolen payment card numbers. Security firm CardCops has been tracking a 20 percent year-over-year increase in Internet chat room activity where hackers test batches of payment card numbers to make sure they're active. "The numbers could have come from a processor, like Heartland, or some other source that has access to a lot of customer data but is not a retailer," says Dan Clements, president of CardCops president.

Also, Forcht Bank in Kentucky last week began issuing replacement debit cards to 8,500 patrons due to reports of fraudulent card activity. "There are several other banks affected, and this is not isolated to Forcht Bank customers," the bank said in a Jan. 12 statement to customers.

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 Tim Wilson is Editor in Chief and co-founder of Dark Reading.com, UBM Tech's online community for information security professionals. He is responsible for managing the site, assigning and editing content, and writing breaking news stories. Wilson has been recognized as one ... View Full Bio

Comment  | 
Print  | 
More Insights
Comments
Newest First  |  Oldest First  |  Threaded View
COVID-19: Latest Security News & Commentary
Dark Reading Staff 11/19/2020
New Proposed DNS Security Features Released
Kelly Jackson Higgins, Executive Editor at Dark Reading,  11/19/2020
How to Identify Cobalt Strike on Your Network
Zohar Buber, Security Analyst,  11/18/2020
Register for Dark Reading Newsletters
White Papers
Video
Cartoon Contest
Write a Caption, Win an Amazon Gift Card! Click Here
Latest Comment: A GONG is as good as a cyber attack.
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
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2020-26890
PUBLISHED: 2020-11-24
Matrix Synapse before 1.20.0 erroneously permits non-standard NaN, Infinity, and -Infinity JSON values in fields of m.room.member events, allowing remote attackers to execute a denial of service attack against the federation and common Matrix clients. If such a malformed event is accepted into the r...
CVE-2020-28348
PUBLISHED: 2020-11-24
HashiCorp Nomad and Nomad Enterprise 0.9.0 up to 0.12.7 client Docker file sandbox feature may be subverted when not explicitly disabled or when using a volume mount type. Fixed in 0.12.8, 0.11.7, and 0.10.8.
CVE-2020-15928
PUBLISHED: 2020-11-24
In Ortus TestBox 2.4.0 through 4.1.0, unvalidated query string parameters to test-browser/index.cfm allow directory traversal.
CVE-2020-15929
PUBLISHED: 2020-11-24
In Ortus TestBox 2.4.0 through 4.1.0, unvalidated query string parameters passed to system/runners/HTMLRunner.cfm allow an attacker to write an arbitrary CFM file (within the application's context) containing attacker-defined CFML tags, leading to Remote Code Execution.
CVE-2020-28991
PUBLISHED: 2020-11-24
Gitea 0.9.99 through 1.12.x before 1.12.6 does not prevent a git protocol path that specifies a TCP port number and also contains newlines (with URL encoding) in ParseRemoteAddr in modules/auth/repo_form.go.