DisclosureLens
All incidentsView linkage analytics →Get the evidence package — $79what’s inside →
SEC 8-KState AGConfirmed10 filings · 10 statesLifecycle stage 2 of 3: ConfirmedUnverified claimConfirmedEnforcedhigh sensitivity
Merged incident · 10 filings

SENSATA TECHNOLOGIES, INC. — March 2025 breach

Clustered 10 filings across 10 jurisdictions · filing window Apr 9, 2025 → Jun 24, 2025. View entity profile → Other incidents for this victim →

⚠ 2 cross-filing discrepancies →Merge100%

Determination

Confirmed

Members

10 filings

States

10

Affected · reported

6,482

First → last filing

Apr 9, 2025 → Jun 24, 2025

Merge confidence

100%

incident inc_60f433cfd4894f8d · merged by deterministic · confidence 100%

Confirmed breach. Merged as one breach: 10 regulatory filings. The filings describe a ransomware attack. Intrusion Mar 28, 2025–Apr 6, 2025, discovered Apr 6, 2025 — the first regulatory filing landed 3 days later. 6,482 individuals reported across the linked filings. Data reported: Government ID, PII, IP / system, and 6 more. Notifications rolled out on a 76-day schedule across 10 filings beginning Apr 9, 2025. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Supplemental
Notification delay
3days

Discovered → first regulatory filing

Discovery variance
47days

Range of discovered_at dates across filings

Materiality delta
3days

Discovery to SEC materiality determination

SEC filing delay
0days

Materiality determination to SEC 8-K filing

Filing span
76days

Time between earliest and latest filing

Not recorded for this incident

Leak precedence — no leak-site claim in this cluster.

Regulatory clocksVermont⏱ VT AG >14 bdayMassachusetts✓ MA credit monitoring dueCalifornia✓ CA 60-day OK · 47dMaine✓ ME AG ≤30d · 13dFull clock table in Litigation Timeline

Sensitive data

financial_credentialsidentity_government

Incident timeline

Mar 28, 2025breach begins
Apr 6, 2025discovered · members disagree
notification delay · 3 days
Apr 9, 2025first filing
Jun 24, 2025most recent filing

Dashed segments are unestablished, not zero — they fill in as filings merge into this incident.

Member cascade — every filing about this breach

  1. APR 9SEC 8-KSEC 8-K noticefirst filing · no count statedday 0
  2. JUN 1IL AGIL AG noticeno count stated+53d
  3. JUN 5MA AGMA AG notice4,131 MA residents+57d
  4. JUN 5CA AGCA AG noticeno count stated+57d
  5. JUN 5VT AGVT AG noticeno count stated+57d
  6. JUN 5IN AGIN AG notice187 IN residents+57d
  7. JUN 5NH AGNH AG notice69 NH residents+57d
  8. JUN 5NE AGNE AG notice5 NE residents+57d
  9. JUN 5ME AGME AG notice362 ME residents+57d
  10. JUN 24RI AGRI AG noticemost recent · 1,728 RI residents+76d
  11. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
Mar 28, 2025 – Apr 6, 2025
CA AG
Discovered
Apr 6, 2025SEC 8-K + CA AG + VT AG +3May 23, 2025IL AG + ME AGfilings disagree on discovery
Data types
Financial account · Financial credentials · Health (basic) · Identity (basic) · Government ID · IP / system · PCI · PHI · PII
SEC 8-K + RI AG + IL AG +6
Attack vector
Ransomware
SEC 8-K

Each fact cites the member filing that establishes it; when filings conflict, every value shows with its source.

Affected residents by state

per-state reported counts

MA4,131
RI1,728
ME362
IN187
NH69
NE5

State AGs report only their own residents; teal bars show each state's reported slice.

Evidence ladder — rungs this incident occupies

Leak-site claim

No leak-site claim on record for this incident.

Press / market report

No press coverage linked yet.

State AG / regulator filing9 members

Unlocks: discovery date, data types, affected count, compliance clock.

SEC 8-K / victim statement1 member

Unlocks: materiality, stated response, full audit trail. Ceiling removed.

Merge provenance

Method
deterministic
Confidence
1.00 · above the 0.85 auto-merge floor
Audit
Every link edge records its method, confidence and model + prompt versions (100% is the strongest edge).

Merges are reversible — a wrong link can be detached with its audit trail intact. How merging works.

Filing velocity

Spread

76 days

Cadence

~1 / 8.4d

vs. multi-state median

9.5× slower

About this clustering

DisclosureLens links filings into incidents through layered matchers: deterministic rules (same source document, multistate filings of one breach, tight-window same-victim pairs), a weighted-similarity scorer for cross-source candidates, and an operator review queue for everything uncertain. Each link records its own method and confidence — shown per filing in the timeline below. The system defaults to NOT merging when uncertain, because a false merge (collapsing two unrelated breaches) is more harmful than a false split (showing related filings separately); uncertain pairs route to human review instead of auto-merging. This page states only what the linked filings agree on; each filing's own account stays on its own record, linked from the timeline below.

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.