Where does the Bitcoin Depot, Inc. case file come from?

Every entry is taken from the breach report Bitcoin Depot, Inc. lodged with the California Attorney General. Nothing here is estimated.

Why do the incident date and the report date differ?

Companies usually investigate before they report. The gap between the two dates shows how long that took.

What does the records-affected figure count?

It is the number the company gave the state. It can cover residents of that state only, so the national total may be higher.

Does this case file change over time?

Yes. When a company files an update or a new state publishes its copy of the report, the dates and counts here are refreshed.

Case file

Case File: Bitcoin Depot, Inc. Data Breach

This file collects the dated facts on record for the Bitcoin Depot, Inc. incident. The state report is dated July 7, 2025. The incident itself is dated June 23, 2024.

Timeline

379 days separate the incident date from the date it was reported.

June 23, 2024Incident dateWhen the filing says the breach took place.
July 7, 2025Report filed in CaliforniaDate the notice was lodged with the California Attorney General.

Case facts

Filing state: California
Date reported: July 7, 2025
Incident date: June 23, 2024
Receiving office: California Attorney General

Case notes

Bitcoin Depot, Inc. recently reported a data security incident to California regulators, with the official filing date noted as July 7, 2025. This notification details an event that occurred on or around June 23, 2024, involving the potential compromise of personal information.

The specific categories of personal information affected by this incident have not been disclosed in the public record. Similarly, the nature of the breach itself remains unspecified, with an ongoing investigation mentioned as part of the case details.

While the filing confirms a data exposure, the number of individuals whose data was involved has not been publicly specified. Bitcoin Depot, Inc. is currently investigating the full scope and impact of the incident.

Individuals who may have been impacted by this event should remain vigilant. Review statements from financial institutions and other service providers for any suspicious activity. Consider placing a fraud alert or credit freeze on your credit reports with the three major bureaus, and change passwords for online accounts, especially if reusing them across different services.

Staying informed about account activity and exercising caution with unsolicited communications are important steps to protect your personal information following any data security event.

Questions about this case file

Where does the Bitcoin Depot, Inc. case file come from?: Every entry is taken from the breach report Bitcoin Depot, Inc. lodged with the California Attorney General. Nothing here is estimated.
Why do the incident date and the report date differ?: Companies usually investigate before they report. The gap between the two dates shows how long that took.
What does the records-affected figure count?: It is the number the company gave the state. It can cover residents of that state only, so the national total may be higher.
Does this case file change over time?: Yes. When a company files an update or a new state publishes its copy of the report, the dates and counts here are refreshed.

California data breaches

Filing source: California Attorney General

Named in the Bitcoin Depot, Inc. breach?

Attach your notice and a short note. An attorney checks it against this case file at no cost.

Timeline

Case facts

Case notes

Questions about this case file

More California case files