Where does the SimonMed Imaging case file come from?

Every entry is taken from the breach report SimonMed Imaging 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: SimonMed Imaging Data Breach

This file collects the dated facts on record for the SimonMed Imaging incident. The state report is dated October 10, 2025. The incident itself is dated January 21, 2025.

Timeline

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

January 21, 2025Incident dateWhen the filing says the breach took place.
October 10, 2025Report filed in CaliforniaDate the notice was lodged with the California Attorney General.

Case facts

Filing state: California
Date reported: October 10, 2025
Incident date: January 21, 2025
Receiving office: California Attorney General

Case notes

SimonMed Imaging, operating in California, has submitted a data breach notification to state regulators. The filing indicates an incident impacting personal information that was discovered and reported in October 2025, concerning a breach that initially took place earlier in the year.

The specific nature of the breach and the categories of personal information involved were not detailed in the public filing. As such, any affected individuals are advised to consider that their general personal data may have been compromised.

Records indicate the breach event itself occurred on January 21, 2025. SimonMed Imaging subsequently filed its report on October 10, 2025, after an internal investigation. The company has stated that the investigation into the incident is ongoing.

While the exact data types are not specified, it is broadly recommended that individuals who may be affected remain vigilant. This includes reviewing account statements for suspicious activity, placing a fraud alert or security freeze on credit files, and being wary of unsolicited communications requesting personal details.

These details are derived from public filings with state regulators, which serve to officially document such security incidents. Individuals who receive direct notification from SimonMed Imaging should review it carefully for any additional context or specific instructions.

Questions about this case file

Where does the SimonMed Imaging case file come from?: Every entry is taken from the breach report SimonMed Imaging 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 SimonMed Imaging 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