DisclosureLens
All incidentsView linkage analytics →Get the evidence package — $7.99what’s inside →
Leak SiteState AGConfirmed12 records · 11 statesLifecycle stage 2 of 3: ConfirmedUnverified claimConfirmedEnforcedcl0phigh sensitivity
Merged incident · 12 records

HONEYWELL INTERNATIONAL INC. — May 2023 breach

Clustered 12 records across 11 jurisdictions: 11 filings and 1 leak-site claim · filing window Jun 16, 2023 → Sep 18, 2023 (dated filings only). View entity profile → Other incidents for this victim →

⚠ 2 cross-filing discrepancies →Merge100%

Determination

Confirmed

Members

12 records

States

11

Affected · reported

118,379

First → last dated filing

Jun 16, 2023 → Sep 18, 2023

Merge confidence

100%

incident inc_45dbf935d8554943 · merged by human · confidence 100%

Part of the Progress Software Corporation supply-chain incident (2023) — at least 89 organizations filed notifications naming this third party.
Confirmed breach. Merged as one breach: 11 regulatory filings and 1 unverified claim. The filings describe hacking. Intrusion May 27, 2023–May 28, 2023, discovered May 29, 2023. 118,379 individuals reported across the linked filings. Data reported: Government ID and Identity (basic). Notifications rolled out on a 94-day schedule across 10 dated filings beginning Jun 16, 2023. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Discovery variance
91days

Range of discovered_at dates across filings

Filing span
94days

Time between earliest and latest filing

Not recorded for this incident

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

Regulatory clocksWashington✗ WA AG >90dCalifornia✗ CA 60-day late · 103dVermont✗ VT AG >45 bdayLeak gap⏱ Leak >30dMassachusetts✓ MA credit monitoring dueFull clock table in Litigation Timeline

Sensitive data

identity_government

Incident timeline

May 27, 2023breach begins
May 29, 2023discovered · members disagree
Jun 16, 2023first dated filing
Sep 18, 2023most recent dated filing

Dashed segments are unestablished, not zero — they fill in as filings merge into this incident. Filings without a recorded filing day, or recorded as filed before the breach they report began, are not placed on this rail.

Member cascade — every filing and leak-site claim in this incident

  1. JAN 1IL AGIL AG noticefiling day not on record · no count stated—
  2. JUN 16MA AGMA AG noticefirst filing · 3,408 MA residentsday 0
  3. JUN 16IN AGIN AG noticestates nationwide total 118,379day 0
  4. JUL 12Leak sitecl0p postattacker claim · unverified+26d
  5. SEP 13MT AGMT AG notice157 MT residents+89d
  6. SEP 13WA AGWA AG notice2,194 WA residents+89d
  7. SEP 13OR AGOR AG noticestates nationwide total 118,379+89d
  8. SEP 13CA AGCA AG noticeno count stated+89d
  9. SEP 13SC AGSC AG notice2,240 SC residents+89d
  10. SEP 13ME AGME AG noticestates nationwide total 118,379+89d
  11. SEP 14VT AGVT AG noticeno count stated+90d
  12. SEP 18NH AGNH AG noticemost recent · 1,069 NH residents+94d
  13. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
May 27, 2023
IN AG
Discovered
May 29, 2023IL AGJun 3, 2023MT AG + WA AG + CA AG +3Aug 28, 2023OR AG + ME AGfilings disagree on discovery
Data types
Identity (basic) · Government ID
MA AG + MT AG + WA AG +5
Attack vector
Third-Party / Supply Chain
MT AG

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)

118,379

Sum of filed state slices

11,297· 9.5% of stated

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

US118,379
MA3,408
SC2,240
WA2,194
IN1,928
NH1,069
ME301
MT157

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 claim1 member

Attacker assertion only. Establishes: claim date, group, alleged victim.

Press / market report

No press coverage linked yet.

State AG / regulator filing11 members

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

SEC 8-K / victim statement

No SEC filing or victim statement yet.

Merge provenance

Method
human
Confidence
1.00 · above the 0.85 auto-merge floor
Reviewed
operator-reviewed Oct 23, 2026 · at least one link edge was human-adjudicated
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

94 days

Cadence

~1 / 10.4d

vs. multi-state median

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