DisclosureLens
All incidentsView linkage analytics →Get the evidence package — $79what’s inside →
State AGConfirmed10 filings · 7 statesLifecycle stage 2 of 3: ConfirmedUnverified claimConfirmedEnforcedplayhigh sensitivity
Merged incident · 10 filings

STANLEY STEEMER INTERNATIONAL, INC. — February 2023 breach

Clustered 10 filings across 7 jurisdictions · filing window Oct 6, 2023 → Dec 4, 2023. View entity profile → Other incidents for this victim →

⚠ 2 cross-filing discrepancies →Merge100%

Determination

Confirmed

Members

10 filings

States

7

Affected · reported

67,921

First → last filing

Oct 6, 2023 → Dec 4, 2023

Merge confidence

100%

incident inc_e73b61a929d44bd8 · merged by deterministic · confidence 100%

Confirmed breach. Merged as one breach: 10 regulatory filings. Intrusion Feb 10, 2023–Mar 6, 2023, discovered Mar 6, 2023 — the first regulatory filing landed 214 days later (flagged late). 67,921 individuals reported across the linked filings. Data reported: Government ID, Financial account, Identity (basic), and 4 more. Notifications rolled out on a 59-day schedule across 10 filings beginning Oct 6, 2023. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Supplemental
Notification delay
214days

Discovered → first regulatory filing

Discovery variance
185days

Range of discovered_at dates across filings

Filing span
59days

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 clocksWashington✗ WA AG >90dCalifornia✗ CA 60-day late · 254dLeak gap✗ Leak >180dOregon✗ OR AG >45dFull clock table in Litigation Timeline

Sensitive data

financial_credentialsidentity_government

Incident timeline

Feb 10, 2023breach begins
Mar 6, 2023discovered · members disagree
notification delay · 214 days
Oct 6, 2023first filing
Dec 4, 2023most 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. OCT 6WA AGWA AG noticefirst filing · 1,497 WA residentsday 0
  2. NOV 15CA AGCA AG noticeno count stated+40d
  3. NOV 15NH AGNH AG notice13 NH residents+40d
  4. NOV 15MA AGMA AG notice515 MA residents+40d
  5. NOV 15MT AGMT AG notice55 MT residents+40d
  6. NOV 15OR AGOR AG noticestates nationwide total 66,978+40d
  7. NOV 15ME AGME AG noticestates nationwide total 66,978+40d
  8. DEC 4NH AGNH AG notice14 NH residents+59d
  9. DEC 4ME AGME AG noticestates nationwide total 67,921+59d
  10. DEC 4CA AGCA AG noticemost recent · no count stated+59d
  11. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
Feb 10, 2023 – Mar 6, 2023
WA AG
Discovered
Mar 6, 2023WA AG + CA AG + NH AG +1Sep 7, 2023OR AG + ME AGfilings disagree on discovery
Data types
Financial account · Financial credentials · Health (basic) · Identity (basic) · Government ID · PHI · PII
WA AG + MA AG + ME AG +3
Attack vector
Ransomware
WA 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)

67,921

Sum of filed state slices

2,098· 3.1% of stated

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

US67,921
WA1,497
MA515
MT55
ME17
NH14

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 filing10 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
deterministic
Confidence
1.00 · above the 0.85 auto-merge floor
Reviewed
operator-reviewed Aug 9, 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

59 days

Cadence

~1 / 6.6d

vs. multi-state median

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