Cutout.Pro Data Breach (2024): What Was Exposed & What To Do
SourceBreach data provided in part by Have I Been Pwned, used under CC BY 4.0.
The Cutout.Pro Data Breach (2024) (reported February 26, 2024) exposed Email addresses, IP addresses, Names and Passwords belonging to roughly 20.0M people. If you have an account with them, your information may now be circulating on the open web and with data brokers. Here’s exactly what happened, how to check if you were affected, and what to do next.
In February 2024, roughly 20 million people who used or registered with Cutout.Pro learned that their personal details had been exposed in a data breach. For those individuals the practical stakes are immediate: email addresses, names, IP addresses and password material that can be reused for phishing, account takeover attempts or further targeting elsewhere on the internet.
Public reporting places the incident in that month and states that the records were later circulated on a popular hacking forum and Telegram channels. Exact timing of the intrusion itself and the full technical method remain limited in open sources, but the scale and the types of data involved make the event consequential for ordinary users of the service.
Inside the incident
According to the reported summary, the AI-powered visual design platform Cutout.Pro suffered a data breach in February 2024 that exposed 20 million records. The material that became public included email addresses, IP addresses, names and salted MD5 password hashes. Those records were subsequently distributed broadly on a popular hacking forum and Telegram channels. The breach was reported on 26 February 2024. No further public detail has been given on the precise date the intrusion began, how long it lasted, or the specific technical vector used to obtain the data.
How a breach like this happens
Incidents of this type typically begin when an attacker gains unauthorised access to a system that stores user accounts or related logs. Common pathways include exploitation of an unpatched application vulnerability, compromised credentials for an administrative interface, or misconfigured storage that is reachable from the public internet. Once inside, the attacker may copy database tables or export files containing account identifiers and authentication material. In many cases the stolen data is later offered or simply posted on underground forums and messaging channels so that others can use it for credential stuffing, spam or further social-engineering attacks. No specific threat group has been publicly attributed to this particular incident, and the precise method used against Cutout.Pro remains undisclosed.
Cutout.Pro and its sector
Cutout.Pro operates as an AI-powered visual design platform that offers tools such as background removal, image enhancement and related photo-editing services. Platforms in this sector routinely collect account registration details, usage logs and authentication credentials so that users can save projects, manage subscriptions and access paid features. Because the service is used by both individual consumers and professional designers, the user base can be large and geographically diverse. A breach at such a platform is consequential precisely because the same email addresses and passwords are often reused across other online services; exposure therefore creates risk that extends well beyond the original site.
What data was at risk
The facts name the exposed data types as email addresses, IP addresses, names and passwords. The reported summary further specifies that the passwords appeared as salted MD5 hashes. These elements were part of the 20 million records that were later distributed. No additional categories of data have been publicly confirmed for this incident.
Why it matters
For affected people the concrete risks include targeted phishing that uses their real name and email address, attempts to reuse the recovered password hashes against other accounts, and correlation of IP addresses with other online activity. Even salted hashes can be attacked offline if the salt is known or weak, and many users still reuse passwords across services. For the organisation the breach creates operational, reputational and potential regulatory consequences, including the need to notify users, reset credentials and review security controls. Because the records were circulated on public channels, the data remains available for opportunistic misuse long after the initial disclosure.
What to do if you're exposed
If you have ever registered with or used Cutout.Pro, treat the possibility of exposure as real and take the following practical steps:
- Change the password on your Cutout.Pro account immediately, and change it on any other site where you used the same or a similar password.
- Enable multi-factor authentication wherever it is offered, especially on email and financial accounts.
- Watch for unexpected login alerts, password-reset emails or phishing messages that reference your name or recent activity.
- Consider placing a fraud alert or credit freeze if you have reason to believe the exposed data could be combined with other personal information.
- Run a free exposure scan of your email address to check whether it has appeared in known breach data sets.
These measures will not reverse the original leak, but they reduce the chance that the circulating records can be used successfully against you.
AICompiled with AI assistance from public sources and published under our editorial standards.
How this breach connects
More recent breaches
BitView Data Breach (2024)Yonéma Data Breach (2024)1win Data Breach (2024)SuperDraft Data Breach (2024)Latest breaches
Read GalaxyWarden’s full analysis of the Cutout.Pro Data Breach (2024) →
Verified breach. Breach data provided in part by Have I Been Pwned, used under CC BY 4.0.
Breach listings — particularly those originating from ransomware or leak sites — are third-party claims that may be unverified, incomplete, or inaccurate. A listing does not by itself confirm that a breach occurred or that any specific data was exposed. Severity is an automated assessment, not a definitive rating. Verification status is shown where available.
Attributions to threat groups and methods reflect public reporting and, in some cases, unverified claims made by the groups themselves; they may be incomplete or later revised. Recent Breaches and GalaxyWarden are independent and are not affiliated with, and do not endorse, any company or group named on this page. This information is aggregated from public sources for awareness only and is not legal, security, or investment advice.