Classic site
Audiobee.ai logo

Breach registry

Audiobee.ai Data Breach

Audiobee.ai

What was exposed, when it happened, and which databases confirm it.

UnverifiedPassword can be found in search
accounts
41,404,030
Breached
September 1, 2026

Were you caught in this breach?

Search your email, phone number or username against every record CheckLeaked indexes.

Your address never leaves this page: it is hashed in your browser and only a short fragment of that hash is sent.

What happened

In February 2024, a data breach occurred at Cutout.Pro, an AI-powered visual design platform, exposing approximately 40 million records. The compromised data included email addresses, IP addresses, full names, phone numbers, and salted MD5 password hashes. This information was widely disseminated on hacking forums and Telegram channels.

Compromised Info

  • email
  • ip_address
  • phone_number
  • hashed_password
  • hashed_password_salt_only
  • name_full

Attestation

Four independent databases catalog this breach and they do not always agree. Each lane below is one source’s own count.

HIBP41,404,030
DEHASHED41,404,030
LEAKCHECK2,370,212
VIGILANTEnot attested

Sources & Link Methods

  • LeakCheck
  • Dehashed— linked via AI direct match to LeakCheck (70% confidence)

FAQ

What was leaked in the Audiobee.ai breach?

The Audiobee.ai breach exposed: email, ip_address, phone_number, hashed_password, hashed_password_salt_only, and name_full.

When did the Audiobee.ai breach happen?

The Audiobee.ai breach was disclosed on September 1, 2026 and affected 41,404,030 records.

Am I affected by the Audiobee.ai breach?

Search your email, phone or username at checkleaked.cc to find out whether your data appears in the Audiobee.ai leak.

Advertising choice

Google Analytics stays active. Allow Google Ads, LinkedIn Ads and Reddit Ads to measure purchases and personalize advertising? Your choice won’t affect search or purchases. You can change it in Settings.

Privacy policy