HackingTechnologyInformationCustomer Data InvolvedIdentity (basic)LowContained

OrthoMinds

bd_cea1351217e6bb5e · schema v1 · pii pii-v1

Severity

Low

Discovered

Nov 1, 2024

Filed

Mar 20, 2025

To disclose

20 weeks

Affected

20state residents only

Linked

10 filings

Confidence

64%

Full breach record for OrthoMinds →2 incidents on file

OrthoMinds, LLC notified Montana residents of a cybersecurity incident where files on certain databases were accessible to unauthorized parties between November 17 and 27, 2024. The company discovered the incident in November 2024. Personal information, including names, may have been involved. OrthoMinds offered credit monitoring and implemented additional security measures.

J jump to incidentP pin to compareR raw source

Incident timeline

Nov 17, 2024

Begins

Mar 20, 2025

Filed

vs. sector median

+1 wks slower

This filing is one of 10 about the same incident.View merged incident

Linked disclosures

Why this link?

Regulatory filings (9) · sorted by filing gap

Vermont State AGbd_01b9f682686326d72025-03-20Verified
Maine State AGbd_0cd00dfbdbde95402025-03-20Candidate
California State AGbd_23a6b5389fd0967a2025-03-20Verified
Nebraska State AGbd_345e02864b85a98e2025-03-20Verified

Show 5 more filings ↓up to 19d gap

New Hampshire State AGbd_7e42e37edfcd3dd42025-03-20Verified
Maryland State AGbd_abcfa359fc4a79152025-03-20Verified
Indiana State AGbd_df4d8a3918ca90af2025-03-20Verified
Massachusetts State AGbd_ea07fef2f30716902025-03-20Verified
Illinois State AGbd_6ae781b1003673792025-03-01 · +19dVerified

Name: OrthoMinds
norm: orthominds

Name: OrthoMinds
norm: orthominds
Industry: Technologyllm

Discovered: Nov 1, 2024
Breach occurred: Nov 17, 2024 – Nov 27, 2024
Materiality determined: —
Notification sent: Mar 20, 2025
Affected individuals: 20state-resident count only
Data types: Identity (basic)
Attack vector: Unauthorized Access
MITRE ATT&CK: T1041 Exfiltration Over C2 Channel
Threat actor: External

During the incident: Launched an investigation into the nature and scope of this potential incident
Remediated to prevent the potential for ongoing access
Conducted an extensive review of these files and folders
Reported this incident to its clients
Implemented additional technical security measures
Reviewing and enhancing existing policies and procedures
Offering complimentary access to credit monitoring through IDX
Changes made: Implemented additional technical security measures designed to prevent similar future incidents
Reviewing and enhancing existing policies and procedures
Source: Quoted from the filing itself, not independently verified.

Time to disclose: 20 weeks(139 days from discovery to filing)
Compliance flags: — (clock not assessable for this source)

Status: No extraction artifact recorded for this disclosure.

Filing propagation · 10 filings · 10 states

View merged incident ↗

Illinois State AGMar 1 · first

Vermont State AG+19d

Maine State AG+19d

California State AG+19d

Nebraska State AG+19d

New Hampshire State AG+19d

Maryland State AG+19d

Indiana State AG+19d

Massachusetts State AG+19d

Montana State AG+19d · this page

Pattern: first filing Mar 1 (IL), last Mar 20 (MT) — a 19-day rolling notification. Rolling spreads often mean counsel is filing as thresholds trip per state. Why this link?

Evidence ladder

Leak-site claim

Attacker assertion only. Establishes: claim date, group, alleged victim.

Press / market report

Unlocks: incident narrative, operational impact. Still no compliance clock.

State AG / regulator filingThis record

Unlocks: discovery date, data types, affected count, compliance clock.

SEC 8-K / victim statement

Unlocks: materiality, stated response, full audit trail. Ceiling removed.

Source URL: https://dojmt.gov/wp-content/uploads/2025/04/Consumer-notification-letter-16.pdf
DisclosureLens links to the originating regulator URL — full filing bodies are not redistributed from public surfaces (§4.5).
Filed at: Mar 20, 2025
Raw hash: f4442fba9cfb8caac6da78a9bbe7b91183cba9d95d60bf3ff059647aa23a4d03

Linked disclosures

Regulatory filings (9) · sorted by filing gap

Reporting entityOrthoMinds

Victim entityOrthoMinds

Incidentdiscovered Nov 1, 2024

Stated responseLaunched an investigation into the nature and scope of this potential incident

Complianceclock not assessable

Extraction provenanceno artifact recorded

Source provenancedojmt.gov