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

KULICKE AND SOFFA INDUSTRIES, INC. — May 2024 breach

Clustered 9 filings across 6 jurisdictions · filing window May 28, 2024 → Nov 22, 2024. View entity profile → Other incidents for this victim →

⚠ 1 cross-filing discrepancy →Merge100%

Determination

Confirmed

Members

9 filings

States

6

Affected · reported

1,105

First → last filing

May 28, 2024 → Nov 22, 2024

Merge confidence

100%

incident inc_235987cdcc2f4b71 · merged by deterministic · confidence 100%

Confirmed breach. Merged as one breach: 9 regulatory filings. Intrusion May 12, 2024–May 12, 2024, discovered May 12, 2024 — the first regulatory filing landed 16 days later (flagged late). 1,105 individuals reported across the linked filings. Data reported: Government ID, PII, IP / system, and 2 more. Notifications rolled out on a 178-day schedule across 9 filings beginning May 28, 2024. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Supplemental
Notification delay
16days

Discovered → first regulatory filing

Discovery variance
0days

Range of discovered_at dates across filings

Filing span
178days

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.

Regulatory clocksMaine✗ ME AG >90d · 149dVermont✗ VT AG >45 bdayCalifornia✗ CA 60-day late · 193dMassachusetts✓ MA credit monitoring dueFull clock table in Litigation Timeline

Sensitive data

identity_government

Incident timeline

May 12, 2024breach begins
May 12, 2024discovered
notification delay · 16 days
May 28, 2024first filing
Nov 22, 2024most 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. MAY 28SEC 8-KSEC 8-K noticefirst filing · no count statedday 0
  2. JUN 12SEC 8-KSEC 8-K noticeno count stated+15d
  3. JUL 9MA AGMA AG notice6 MA residents+42d
  4. JUL 9ME AGME AG noticestates nationwide total 949+42d
  5. OCT 7VT AGVT AG noticeno count stated+132d
  6. OCT 8ME AGME AG noticestates nationwide total 1,105+133d
  7. OCT 8IN AGIN AG noticestates nationwide total 1,105+133d
  8. OCT 10CA AGCA AG noticeno count stated+135d
  9. NOV 22CA AGCA AG noticemost recent · no count stated+178d
  10. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
May 12, 2024
ME AG
Discovered
May 12, 2024
SEC 8-K + ME AG + VT AG +1
Data types
Financial account · Identity (basic) · Government ID · IP / system · PII
SEC 8-K + ME AG + MA AG +2
Attack vector
Unauthorized Access
SEC 8-K

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

Count reconciliation

per-state reported counts

Nationwide (stated in a filing)

1,105

Sum of filed state slices

9· 0.8% of stated

99% of the stated total lives in states whose filings carry no count — the dashed share shrinks as filings land.

US1,105
MA6
ME2
IN1

State AGs report only their own residents; teal bars show each state's reported slice. The gray US row is the nationwide total reported in a linked filing.

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 filing7 members

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

SEC 8-K / victim statement2 members

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

178 days

Cadence

~1 / 22.3d

vs. multi-state median

22.3× 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.