Checkout.com Refuses Ransom After ShinyHunters Breach of Legacy System
Checkout.com, a payment services provider, was targeted by the ShinyHunters criminal group, who gained unauthorized access to a legacy third-party cloud file storage system used for internal documents and merchant onboarding materials from 2020 and earlier. The attackers demanded a ransom, but Checkout.com refused to pay, instead donating the equivalent amount to cybercrime research. The company confirmed that its live payment processing platform was not affected, and no merchant funds or card numbers were accessed. Checkout.com has taken full responsibility for the incident, apologized to affected partners, and is working with law enforcement and regulators while notifying impacted parties.
The breach affected less than 25% of Checkout.com's current merchant base, as the compromised system contained only historical operational data. The company emphasized its commitment to transparency and accountability, outlining plans to invest further in cybersecurity. The incident highlights the ongoing threat posed by ransomware and extortion groups, with ShinyHunters continuing to target organizations for data theft and ransom. Checkout.com's public stance against paying the ransom and redirecting funds to cybercrime research sets a notable precedent in the industry.
How this story unfolded
5 events from the most recent confirmed update back to the earliest known activity.
Checkout.com pledged ransom-equivalent donations to cybersecurity research
Instead of paying the attackers, Checkout.com said it would donate an equivalent amount to Carnegie Mellon University and the University of Oxford Cyber Security Centre. The company framed the move as support for cybersecurity research following the extortion attempt.
Checkout.com disclosed the breach and refused to pay ransom
Checkout.com publicly acknowledged the data breach, said it would not pay the extortion demand, and stated it was contacting affected customers. The company also said it was working with law enforcement and regulators on the incident.
Attackers attempted to extort Checkout.com over stolen data
After stealing data, ShinyHunters demanded a ransom from Checkout.com. The company characterized the incident as an extortion attempt tied to the legacy system compromise.
ShinyHunters breached Checkout.com's legacy storage environment
The ShinyHunters cybercrime group accessed data from Checkout.com's legacy third-party cloud file storage system. Checkout.com said the incident affected less than 25% of its merchant base and did not impact payment processing, merchant funds, or card numbers.
Legacy cloud file storage system remained accessible after 2020
Checkout.com said the breached environment was a legacy third-party cloud file storage system used in 2020 and earlier that was not properly decommissioned. The system reportedly held internal operational documents and merchant onboarding materials.
Related entities
Vulnerabilities, threat actors, malware, products, organizations, and breaches Mallory has linked to this story.
Sources
6 references tracked. Mallory keeps watching after this page renders.
A miracle: A company says sorry after a cyber attack - and donates the ransom to cybersecurity research
bitdefender.com
Open sourceCheckout.com Discloses Data Breach After Extortion Attempt
databreaches.net
Open sourceCheckout.com snubs hackers after data breach, to donate ransom instead
bleepingcomputer.com
Open sourceShinyHunters-hit Checkout.com rejects ransom payment
scworld.com
Open sourceRansomed CTO falls on sword, refuses to pay extortion demand
go.theregister.com
Open sourceProtecting our Merchants: Standing up to Extortion
checkout.com
Open sourceSee the full picture, correlated to your attack surface.
Map indicators from this story to your assets and identify affected systems in minutes.
Every observed campaign, victim, and pivot linked to actors named in this story.
Malware, exploits, and IOCs connected to the activity described here.
YARA, Sigma, and Snort rules deployed to your SIEM as soon as they’re published.
Get matching new stories delivered to your team as they break — not the next morning.
Ask questions about this story and take action on the answers.



