Unity Technologies SF — March 2025 breach

Clustered 5 filings across 5 jurisdictions · filing window Oct 2, 2025 → Oct 10, 2025 (dated filings only). View entity profile → Other incidents for this victim →

⚠ 1 cross-filing discrepancy →Merge100%

Determination

Confirmed

Members

5 filings

States

Affected · reported

428

First → last dated filing

Oct 2, 2025 → Oct 10, 2025

Merge confidence

100%

incident inc_c0eb921c45734b72 · merged by deterministic · confidence 100%

Confirmed breach. Merged as one breach: 5 regulatory filings. The filings describe hacking. Intrusion Mar 13, 2025–Aug 26, 2025, discovered Aug 26, 2025 — the first regulatory filing landed 37 days later. 428 individuals reported across the linked filings. Data reported: Identity (basic), Financial account, PII, and 2 more. Notifications rolled out on a 8-day schedule across 4 dated filings beginning Oct 2, 2025. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Notification delay

37days

Discovered → first regulatory filing

Discovery variance

0days

Range of discovered_at dates across filings

Filing span

8days

Time between earliest and latest filing

Not recorded for this incident

Leak precedence · Materiality delta · SEC filing delay — no leak-site claim in this cluster; no SEC 8-K in this cluster.

Regulatory clocksMaine⏱ ME AG >30d · 44dFull clock table in Litigation Timeline

No cross-filing comparison data available for this incident.

The weekly clock on records like this one

The Disclosure Clock is a weekly briefing on what landed in the disclosure record, and the gap between the criminals' post and the regulator's filing — measured on the whole record, with the method shown.

Weekly. Double opt-in, one-click unsubscribe, and the address goes nowhere else.