DisclosureLens
UnknownCustomer Data InvolvedPIIIdentity (basic)Financial accountLow

Hunneman

bd_45ba64fb08e90dce · schema v1 · pii pii-v1

Severity

Low

Discovered

—

Filed

Feb 5, 2026

To disclose

—

Affected

229state residents only

Linked

4 filings

Confidence

67%
Full breach record for Hunneman →

Hunneman notified Massachusetts residents of a data security incident via a letter dated February 3, 2026. The notice offers 24 months of credit monitoring and identity theft protection through IDX. The letter does not specify the nature of the breach, the dates of occurrence or discovery, the number of affected individuals, or the specific types of data compromised, though it references credit reports and security freezes, implying potential exposure of financial or identity data.

Leak gap clock⏱ Leak >30d
⚠ no discovery dateNo discovery date was extracted, so no notification clock can be evaluated.

Incident timeline — partial

? — ?

Breach window unknown

Feb 5, 2026

Filed

—

Corroborated · see linked filings

Compliance clocks stay unassessable until a regulatory filing lands. Dashed segments fill in automatically when corroboration arrives.

This filing is one of 4 about the same incident.View merged incident
A leak claim by interlock about this victim predates this filing by 35 days.View originating leak claim

Linked disclosures

Why this link?

Ransomware claims (1)

Regulatory filings (2) · sorted by filing gap

Filing propagation · 3 filings · 3 states

View merged incident ↗
New Hampshire State AGFeb 4 · first
Maine State AGFeb 4 · first
Massachusetts State AG+1d · this page

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.