Global payment processor Checkout.com has confirmed it was the target of a data breach by the notorious ShinyHunters cybercrime group. The attackers gained access to a legacy cloud file storage system containing internal operational documents. In a notable departure from typical incident responses, Checkout.com has publicly refused to pay the ransom demanded by the attackers. Instead, the company has pledged to donate the equivalent sum to the cybersecurity research centers at Carnegie Mellon University and the University of Oxford. The company's investigation found that its core payment processing environment, merchant funds, and payment card data were not compromised, as the breach was contained to an isolated, outdated system.
The breach was initiated by ShinyHunters, a well-known threat group responsible for numerous high-profile data breaches, including attacks on Microsoft and Ticketmaster. The group's primary motivation is financial, typically achieved by stealing data and either selling it on dark web forums or extorting the victim company. In this case, the attackers identified and exploited a misconfiguration in Checkout.com's asset inventory: a legacy third-party cloud storage system that was last used in 2020 but had not been properly decommissioned. This oversight provided an entry point for the attackers to access and exfiltrate data.
The root cause of the breach was a failure in asset management and decommissioning processes. The attack vector was not a sophisticated zero-day, but rather the exploitation of a forgotten, insecure asset.
This incident highlights a common but critical security gap: organizations losing track of their digital assets, especially in complex, multi-cloud environments. Such 'shadow IT' or legacy systems often fall outside the scope of regular security monitoring and patching, making them prime targets for attackers.
T1530 - Data from Cloud Storage Object: The primary technique used by ShinyHunters to access and exfiltrate data from the misconfigured cloud storage.T1580 - Cloud Infrastructure Discovery: Attackers likely scanned for and discovered the exposed cloud asset as part of their reconnaissance.T1657 - Financial Theft: While direct financial theft was not achieved, the ransom demand falls under this category, representing the attacker's ultimate goal.While the breach did not compromise the most sensitive financial data, the impact is still significant:
Detecting such an incident relies on comprehensive visibility into all cloud assets.
System Configuration Permissions.Checkout.com's response sets a strong precedent. By refusing to pay the ransom, they avoid funding criminal activity. By donating the funds, they turn a negative event into a positive contribution to the security community, reinforcing their commitment to fighting cybercrime.
To prevent similar breaches, organizations must focus on fundamental cybersecurity hygiene:
Checkout.com reiterates breach details, confirms refusal to pay extortion, and emphasizes no sensitive financial data was compromised.
Further reports confirm Checkout.com's data breach and subsequent extortion attempt. The company continues to assert that no sensitive cardholder or financial data was compromised, reinforcing its initial statements. Checkout.com maintained its refusal to engage with the extortionists, reporting the incident to law enforcement. While the specific threat actor was not named in these follow-up reports, the tactics align with data extortion groups. Technical analysis suggests potential initial access via public-facing application exploits or compromised credentials, leading to data exfiltration from cloud storage. The incident underscores the persistent threat of data theft for extortion against fintech companies, even when core financial systems remain secure.

Cybersecurity professional with over 10 years of specialized experience in security operations, threat intelligence, incident response, and security automation. Expertise spans SOAR/XSOAR orchestration, threat intelligence platforms, SIEM/UEBA analytics, and building cyber fusion centers. Background includes technical enablement, solution architecture for enterprise and government clients, and implementing security automation workflows across IR, TIP, and SOC use cases.
Help others stay informed about cybersecurity threats