HackingManufacturingManufacturingCustomer Data InvolvedTargetedIdentity (basic)Government IDHighContained

Michigan Sugar Company

bd_c27a4f8157aac5e7 · schema v1 · pii pii-v1

Severity

High

Discovered

Aug 14, 2025

Filed

Jan 30, 2026

To disclose

24 weeks

Affected · nationwide

16,6892 in this filing

Linked

5 records

Confidence

65%

Full breach record for Michigan Sugar Company →

Michigan Sugar Company experienced an external system breach (hacking) on August 14, 2025. The incident affected 16,689 individuals nationwide, including 2 Maine residents. Compromised data included names and Social Security numbers. The company engaged third-party cybersecurity specialists, notified affected individuals on January 30, 2026, and offered 12 months of credit monitoring and identity restoration services.

J jump to incidentP pin to compareR raw source

Maine clockDiscovered Aug 14, 2025 → Filed with AG Jan 30, 2026169d ⏱ ME AG >30d24 weeks discovery → filing

⚠ occurrence dateThe stored discovery date equals the breach OCCURRENCE date. Detection is normally later, so this OVERSTATES the delay — a 'late' verdict here may not be real.

Incident timeline

discovery → filing · 24 weeks / 169 days

Aug 14, 2025

Begins

Aug 14, 2025

Discovered

Jan 30, 2026

Filed

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

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

Linked disclosures

Why this link?

Ransomware claims (1)

Leak Siteakirabd_d993d62d6acfe8452025-09-05 · +147dVerified by operator

Regulatory filings (3) · sorted by filing gap

Nebraska State AGbd_05e5bf9ee6fe57e62026-01-30Verified
Massachusetts State AGbd_0a725cddec96a1092026-01-30Verified by operator
Indiana State AGbd_ac95a673b1f6884a2026-01-30Verified

Name: Michigan Sugar Company
norm: michigan sugar
Domain: michigansugar.com
Industry: manufacturing

Name: Michigan Sugar Company
norm: michigan sugar
Domain: michigansugar.com
Industry: manufacturing
Industry: Manufacturingllm

Discovered: Aug 14, 2025
Breach occurred: Aug 14, 2025
Undetected for: 0 daysoccurrence → discovery
Materiality determined: —
Notification sent: Jan 30, 2026
Affected individuals: 16,689state + nationwide
Data types: Identity (basic)Government ID
Attack vector: Unauthorized Access
MITRE ATT&CK: T1190 Exploit Public-Facing ApplicationT1078 Valid Accounts
Threat actor: External
Regulator citations: providing written notice of this incident to relevant state regulators
Initial access: exploit_public_facing

During the incident: Launched an investigation, with the assistance of third-party cybersecurity specialists
Conducted a thorough and comprehensive review to determine what information was accessible
Moved quickly to investigate and respond to the incident
Assess the security of MSC systems
Identify potentially affected individuals
Providing access to credit monitoring services for one (1) year, through IDX
Providing impacted individuals with guidance on how to better protect against identity theft and fraud
Changes made: Working to implement additional safeguards and training to its employees
Source: Quoted from the filing itself, not independently verified.

Time to disclose: 24 weeks(169 days from discovery to filing)
Compliance flags: ME AG >30d · 169dME resident >60d · 169dLeak >90d
Discovery-date grounding: occurrence dateThe stored discovery date equals the breach OCCURRENCE date. Detection is normally later, so this OVERSTATES the delay — a 'late' verdict here may not be real.
Clock breakdown: Statute Window Elapsed Threshold Status
Maine
Discovered: Aug 14, 2025
→ Filed with AG: Jan 30, 2026
169d 30 days (soft) ME AG >30d
Maine
Discovered: Aug 14, 2025
→ Notified: Jan 30, 2026
169d 60 days (analyst band; statutory cap is 30 days) ME resident >60d

Statute	Window	Elapsed	Threshold	Status
Maine	Discovered: Aug 14, 2025 → Filed with AG: Jan 30, 2026	169d	30 days (soft)	ME AG >30d
Maine	Discovered: Aug 14, 2025 → Notified: Jan 30, 2026	169d	60 days (analyst band; statutory cap is 30 days)	ME resident >60d

Status: No extraction artifact recorded for this disclosure.

Filing propagation · 4 filings · 4 states

View merged incident ↗

Nebraska State AGJan 30 · first

Massachusetts State AGJan 30 · first

Indiana State AGJan 30 · first

Maine State AGJan 30 · first · 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.

Source URL: https://www.maine.gov/agviewer/content/ag/985235c7-cb95-4be2-8792-a1252b4f8318/044131fe-1fa4-416e-bbd8-904dc12a7e5b.html
DisclosureLens links to the originating regulator URL — full filing bodies are not redistributed from public surfaces (§4.5).
Filed at: Jan 30, 2026
Raw hash: b3016b92a4a72c0286278af3f29ac3008799eddeab324eec86216467154a5c49

Linked disclosures

Ransomware claims (1)

Regulatory filings (3) · sorted by filing gap

Reporting entityMichigan Sugar Company

Victim entityMichigan Sugar Company

Incidentdiscovered Aug 14, 2025

Stated responseLaunched an investigation, with the assistance of third-party cybersecurity specialists

ComplianceME AG >30d

Extraction provenanceno artifact recorded

Source provenancewww.maine.gov