DisclosureLens
All incidentsView linkage analytics →Get the evidence package — $79what’s inside →
Leak SiteState AGConfirmed8 filings · 7 statesLifecycle stage 2 of 3: ConfirmedUnverified claimConfirmedEnforcedakirahigh sensitivity
Merged incident · 8 filings

Hospitality Staffing Solutions — March 2023 breach

Clustered 8 filings across 8 jurisdictions · filing window Jun 29, 2023 → Aug 18, 2023. View entity profile → Other incidents for this victim →

⚠ 2 cross-filing discrepancies →Merge100%

Determination

Confirmed

Members

8 filings

States

7

Affected · reported

104,660

First → last filing

Jun 29, 2023 → Aug 18, 2023

Merge confidence

100%

incident inc_2be41a5686194a66 · merged by deterministic · confidence 100%

Confirmed breach. Merged as one breach: 7 regulatory filings and 1 unverified claim. The filings describe unauthorized access. Intrusion Mar 2, 2023–Jun 2, 2023, discovered Jun 2, 2023 — the first regulatory filing landed 61 days later. 104,660 individuals reported across the linked filings. Data reported: Government ID, Identity (basic), Financial account, and 1 more. Notifications rolled out on a 50-day schedule across 7 filings beginning Jun 29, 2023. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Notification delay
61days

Discovered → first regulatory filing

Discovery variance
26days

Range of discovered_at dates across filings

Leak precedence
34days before filing

Days between the first leak-site claim and the first regulatory filing. Positive = the claim came first (public exposure before disclosure). Negative = the claim trailed the filing, so there was no pre-disclosure leak. Counts regulatory filings only — press coverage is not a regulatory disclosure.

Filing span
50days

Time between earliest and latest filing

Not recorded for this incident

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

Regulatory clocksLeak gap⏱ Leak >30dMaine⏱ ME AG >30d · 40dFull clock table in Litigation Timeline

Sensitive data

identity_government

Incident timeline

Mar 2, 2023breach begins
Jun 2, 2023discovered · members disagree
notification delay · 61 days
Aug 2, 2023first filing
Aug 18, 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. JUN 29Leak siteakira postfirst filing · attacker claim · unverifiedday 0
  2. AUG 2IN AGIN AG noticestates nationwide total 104,660+34d
  3. AUG 7MT AGMT AG notice7 MT residents+39d
  4. AUG 7CA AGCA AG noticeno count stated+39d
  5. AUG 7ME AGME AG noticestates nationwide total 104,660+39d
  6. AUG 7MA AGMA AG notice603 MA residents+39d
  7. AUG 16NH AGNH AG notice3 NH residents+48d
  8. AUG 18SC AGSC AG noticemost recent · 2,304 SC residents+50d
  9. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
Mar 2, 2023
IN AG
Discovered
Jun 2, 2023MT AG + CA AG + NH AG +1Jun 28, 2023ME AGfilings disagree on discovery
Data types
Financial account · Identity (basic) · Government ID · PII
MT AG + CA AG + ME AG +3
Attack vector
Unauthorized Access
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)

104,660

Sum of filed state slices

4,314· 4.1% of stated

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

US104,660
SC2,304
IN1,396
MA603
MT7
NH3
ME1

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 filing7 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 22, 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

50 days

Cadence

~1 / 7.1d

vs. multi-state median

6.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.