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.

Comments
Home Depot Breach May Not Be Related To BlackPOS, Target
Newest First  |  Oldest First  |  Threaded View
Sara Peters
Sara Peters,
User Rank: Author
9/15/2014 | 2:33:42 PM
Re: PoS malware a growing threat
@GonzSTL   All great points. The most professional malware authors are going to build on success (whether it's theirs or someone else's) not reinvent the wheel. But this is, I think, the most important thing you said:  "More importantly, why didn't these breached companies have some mechanism in place that examines data leaving their organizations and prevents data from inappropriately going out?"   I think we're seeing again and again and again that organizations aren't watching what's leaving, which is making it possible for these breaches take place over the span of months. 
SgS125
SgS125,
User Rank: Ninja
9/12/2014 | 10:26:57 AM
Great write up!
Thanks for providing the technical details on the code.

Always nice to have some in depth reporting, and it is interesting to see the differences so cleanly laid out by someone who has access to the details.

Very much appreciated, great article!
GonzSTL
GonzSTL,
User Rank: Ninja
9/12/2014 | 9:43:45 AM
Re: PoS malware a growing threat
Agreed, but is it really surprising that there is a potentially new malware strain that is equally nasty? I used to write software and one of my main strategies was to never reinvent the wheel, but instead, improve and optimize it. If I were to create new malware, I would look at the existing ones that have had great success, pick out the particularly good and clever aspects of each one, and combine them all into a new product, optimized and sophisticated enough to hide itself using proven methods. I view this as a natural evolution of malware; the bad guys are quite clever, and surely that is exactly what they are doing. Why is this shocking? In fact, why isn't this anticipated? Why aren't the anti-malware products equipped with this anticipated behavior detecting techniques in their heuristic algorithms? Maybe they are, but apparently not quite up to the challenge, supporting the stigma that the good guys are always playing catch up to the bad guys.

More importantly, why didn't these breached companies have some mechanism in place that examines data leaving their organizations and prevents data from inappropriately going out? Plain text data traversing the network can be easily examined and regulated for controlled content, to prevent sensitive data leakage. Encrypted data with external destinations should be suspicious and therefore carefully monitored and controlled. I am curious - did any of these breached companies even fully implement the SANS 20 Critical Security Controls at the very least, or did they simply put cursory systems in place that allowed them to mark a check in the appropriate compliance checkboxes? One of the biggest pitfalls in security is assuming that compliance means security, and I wonder if any of these companies were guilty of that.
Marilyn Cohodas
Marilyn Cohodas,
User Rank: Strategist
9/12/2014 | 8:18:15 AM
Getting the facts straight
With the almost daily reporting of retail breaches these days, it's tempting for the news media to jump to quick  conclusion that further analysis doesn't bear out. Thanks for the thoughtful reporting on this story, Sara, and for keeping the record straight at Dark Reading, Sara. 
securityaffairs
securityaffairs,
User Rank: Ninja
9/11/2014 | 4:57:26 PM
PoS malware a growing threat
PoS malware has characterized the 2013, their evolution is the results of continuous developments offered in the underground market. Exfiltration techniques and evasion methods are making these threats even more complex and hard to analyze.

If the news in the title is confirmed security community will face with a new strain of malware with features similar to BlackPos malware that is equally dangerous.


Edge-DRsplash-10-edge-articles
I Smell a RAT! New Cybersecurity Threats for the Crypto Industry
David Trepp, Partner, IT Assurance with accounting and advisory firm BPM LLP,  7/9/2021
News
Attacks on Kaseya Servers Led to Ransomware in Less Than 2 Hours
Robert Lemos, Contributing Writer,  7/7/2021
Commentary
It's in the Game (but It Shouldn't Be)
Tal Memran, Cybersecurity Expert, CYE,  7/9/2021
Register for Dark Reading Newsletters
White Papers
Video
Cartoon
Current Issue
Black Hat USA 2022 Attendee Report
Black Hat attendees are not sleeping well. Between concerns about attacks against cloud services, ransomware, and the growing risks to the global supply chain, these security pros have a lot to be worried about. Read our 2022 report to hear what they're concerned about now.
Flash Poll
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2017-2597
PUBLISHED: 2022-08-08
** REJECT ** DO NOT USE THIS CANDIDATE NUMBER. ConsultIDs: none. Reason: This candidate was in a CNA pool that was not assigned to any issues during 2017. Notes: none.
CVE-2017-2631
PUBLISHED: 2022-08-08
** REJECT ** DO NOT USE THIS CANDIDATE NUMBER. ConsultIDs: none. Reason: This candidate was in a CNA pool that was not assigned to any issues during 2017. Notes: none.
CVE-2017-2657
PUBLISHED: 2022-08-08
** REJECT ** DO NOT USE THIS CANDIDATE NUMBER. ConsultIDs: none. Reason: This candidate was in a CNA pool that was not assigned to any issues during 2017. Notes: none.
CVE-2017-7527
PUBLISHED: 2022-08-08
** REJECT ** DO NOT USE THIS CANDIDATE NUMBER. ConsultIDs: none. Reason: This candidate was in a CNA pool that was not assigned to any issues during 2017. Notes: none.
CVE-2021-41615
PUBLISHED: 2022-08-08
websda.c in GoAhead WebServer 2.1.8 has insufficient nonce entropy because the nonce calculation relies on the hardcoded onceuponatimeinparadise value, which does not follow the secret-data guideline for HTTP Digest Access Authentication in RFC 7616 section 3.3 (or RFC 2617 section 3.2.1). NOTE: 2.1...