HackingTechnologyInformationData ExfiltratedRansom DemandedTargetedIdentity (basic)Government IDFinancial accountEmploymentMediumContained

H2O.AI, INC.

bd_0ce52b580d7b1a57 · schema v1 · pii pii-v1

Severity

Medium

Discovered

Feb 18, 2025

Filed

Mar 27, 2025

To disclose

5 weeks

Affected · nationwide

7341 in this filing

Linked

5 records

Confidence

66%

Full breach record for H2O.AI, INC. →

H2O.ai experienced an external system breach (hacking) between Dec 20, 2024, and Jan 29, 2025. Discovered Feb 18, 2025, after a financially motivated group claimed to have stolen data. 734 individuals affected, including 1 Maine resident. Data included names, SSNs, driver's licenses, and financial info. H2O retained cybersecurity firms, notified law enforcement, and enhanced network security. Offered 12 months of Experian IdentityWorks.

J jump to incidentP pin to compareR raw source

Maine clockDiscovered Feb 18, 2025 → Filed with AG Mar 27, 202537d ⏱ ME AG >30d5 weeks discovery → filing

⚠ unattributedNo provenance was recorded for this discovery date and it matches no other date on the record. It may be correct, but it is not independently grounded.

Incident timeline

undetected · 60 days

discovery → filing · 5 weeks / 37 days

Dec 20, 2024

Begins

Feb 18, 2025

Discovered

Mar 27, 2025

Filed

vs. sector median

6 wks faster

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

A leak claim by linkc about this victim was first seen 36 days before this filing.View originating leak claim

Linked disclosures

Why this link?

Ransomware claims (1)

Leak Sitelinkcbd_e73774e23c960a082025-01-29 · +56dVerified by operator

Regulatory filings (3) · sorted by filing gap

Indiana State AGbd_3becfe55f66e60f92025-03-27Verified
Massachusetts State AGbd_415b1d6f291888ea2025-03-27Verified by operator
Maryland State AGbd_b08fbb3b839e8bb62026-04-23 · +392dVerified by operator

Name: H2O.AI, INC.
norm: h2oai
Domain: h2o.ai

Name: H2O.AI, INC.
norm: h2oai
Domain: h2o.ai
Industry: Technologyllm

Discovered: Feb 18, 2025
Breach occurred: Dec 20, 2024 – Jan 29, 2025
Undetected for: 60 daysoccurrence → discovery
Materiality determined: —
Notification sent: Mar 27, 2025
Affected individuals: 734state + nationwide
Data types: Identity (basic)Government IDFinancial accountEmployment
Attack vector: Unauthorized Access
MITRE ATT&CK: T1190 Exploit Public-Facing ApplicationT1078 Valid AccountsT1041 Exfiltration Over C2 Channel
Threat actor: ExternalFinancial
Regulator citations: Notified law enforcement
Initial access: exploit_public_facing

During the incident: Retained leading cybersecurity firms to assist in responding to this claim and to help conduct an investigation
Immediately reported the incident to law enforcement and continue to cooperate with their investigation
Changes made: Implemented numerous measures to enhance the security of our network systems and data
Source: Quoted from the filing itself, not independently verified.

Time to disclose: 5 weeks(37 days from discovery to filing)
Compliance flags: ME AG >30d · 37dLeak >30d
Discovery-date grounding: unattributedNo provenance was recorded for this discovery date and it matches no other date on the record. It may be correct, but it is not independently grounded.
Clock breakdown: Statute Window Elapsed Threshold Status
Maine
Discovered: Feb 18, 2025
→ Filed with AG: Mar 27, 2025
37d 30 days (soft) ME AG >30d

Statute	Window	Elapsed	Threshold	Status
Maine	Discovered: Feb 18, 2025 → Filed with AG: Mar 27, 2025	37d	30 days (soft)	ME AG >30d

Status: No extraction artifact recorded for this disclosure.

Filing propagation · 4 filings · 4 states

View merged incident ↗

Indiana State AGMar 27 · first

Massachusetts State AGMar 27 · first

Maine State AGMar 27 · first · this page

Maryland State AG+392d

Pattern: first filing Mar 27 (IN), last Apr 23 (MD) — a 392-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://www.maine.gov/agviewer/content/ag/985235c7-cb95-4be2-8792-a1252b4f8318/48013dcb-0301-4373-b69a-20a30bbfe666.html
DisclosureLens links to the originating regulator URL — full filing bodies are not redistributed from public surfaces (§4.5).
Filed at: Mar 27, 2025
Raw hash: 16f5d6b218a91fe161a4d7598a839e229b4ce477901917ba39d1794fbc7e2bee

Linked disclosures

Ransomware claims (1)

Regulatory filings (3) · sorted by filing gap

Reporting entityH2O.AI, INC.

Victim entityH2O.AI, INC.

Incidentdiscovered Feb 18, 2025

Stated responseRetained leading cybersecurity firms to assist in responding to this claim and to help conduct an investigation

ComplianceME AG >30d

Extraction provenanceno artifact recorded

Source provenancewww.maine.gov