HackingTechnologyInformationStolen CredentialsData ExfiltratedEmployee Data InvolvedGovernment IDIdentity (basic)Financial accountEmploymentMediumContained

H2O.AI, INC.

bd_b08fbb3b839e8bb6 · schema v1 · pii pii-v1

Severity

Medium

Discovered

Feb 18, 2025

Filed

Apr 23, 2026

To disclose

—

Affected

12state residents only

Linked

5 records

Confidence

66%

Full breach record for H2O.AI, INC. →

H2O.ai notified the Maryland Attorney General that a financially motivated threat actor accessed H2O systems between December 20, 2024, and January 29, 2025. The incident affected 12 Maryland residents, exposing payroll, SSNs, driver's license numbers, and addresses. H2O retained cybersecurity firms, reported to law enforcement, took the environment offline, and implemented enhanced monitoring.

J jump to incidentP pin to compareR raw source

Incident timeline

undetected · 60 days

Dec 20, 2024

Begins

Feb 18, 2025

Discovered

Apr 23, 2026

Filed

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

Linked disclosures

Why this link?

Ransomware claims (1)

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

Regulatory filings (3) · sorted by filing gap

Maine State AGbd_0ce52b580d7b1a572025-03-27 · +392dVerified
Indiana State AGbd_3becfe55f66e60f92025-03-27 · +392dVerified
Massachusetts State AGbd_415b1d6f291888ea2025-03-27 · +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: —
Affected individuals: 12state-resident count only
Data types: Identity (basic)Government IDFinancial account
Data elements: Social Security numberDate of birth
Attack vector: Unauthorized Access
MITRE ATT&CK: T1078 Valid AccountsT1041 Exfiltration Over C2 Channel
Threat actor: ExternalFinancial
Regulator citations: reported the incident to law enforcement
Initial access: valid_credentials

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
Reviewing our security controls, including segmentation between our environments
Taking the impacted environment offline
Implementing enhanced monitoring to detect and mitigate threats in real-time
Changes made: Implemented measures to enhance the security of our network systems and data
Reviewing our security controls, including segmentation between our environments
Taking the impacted environment offline
Implementing enhanced monitoring to detect and mitigate threats in real-time
Source: Quoted from the filing itself, not independently verified.

Compliance flags: — (clock not assessable for this source)

Status: No extraction artifact recorded for this disclosure.

Filing propagation · 4 filings · 4 states

View merged incident ↗

Maine State AGMar 27 · first

Indiana State AGMar 27 · first

Massachusetts State AGMar 27 · first

Maryland State AG+392d · this page

Pattern: first filing Mar 27 (ME), 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://oag.maryland.gov/resources-info/SBN%20Documents/2025/ITU-376765.pdf
DisclosureLens links to the originating regulator URL — full filing bodies are not redistributed from public surfaces (§4.5).
Filed at: Apr 23, 2026
Raw hash: a7b179c2c4f17204d9d90cbbb57b9fb05b36fe4e6996981aafcd290ec2562459

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

Complianceclock not assessable

Extraction provenanceno artifact recorded

Source provenanceoag.maryland.gov