DisclosureLens
All incidentsView linkage analytics →Get the evidence package — $79what’s inside →
Leak SiteState AGConfirmed14 filings · 11 statesLifecycle stage 2 of 3: ConfirmedUnverified claimConfirmedEnforcedransomhubhigh sensitivity
Merged incident · 14 filings

Smart ERP Solutions — July 2024 breach

Clustered 14 filings across 12 jurisdictions · filing window Jul 13, 2024 → Mar 14, 2025. View entity profile → Other incidents for this victim →

⚠ 2 cross-filing discrepancies →Merge100%

Determination

Confirmed

Members

14 filings

States

11

Affected · reported

78,713

First → last filing

Jul 13, 2024 → Mar 14, 2025

Merge confidence

100%

incident inc_705e2b1e1b3d4eda · merged by deterministic · confidence 100%

Confirmed breach. Merged as one breach: 12 regulatory filings and 2 unverified claims. Intrusion Jul 3, 2024–Jul 13, 2024, discovered Jul 13, 2024 — the first regulatory filing landed 184 days later (flagged late). 78,713 individuals reported across the linked filings. Data reported: Government ID, PII, and Identity (basic). Notifications rolled out on a 244-day schedule across 12 filings beginning Jul 13, 2024. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Supplemental
Notification delay
184days

Discovered → first regulatory filing

Discovery variance
213days

Range of discovered_at dates across filings

Leak precedence
184days 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
244days

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 >180dMaine✗ ME AG >90d · 241dFull clock table in Litigation Timeline

Sensitive data

identity_government

Incident timeline

Jul 3, 2024breach begins
Jul 13, 2024discovered · members disagree
notification delay · 184 days
Jan 13, 2025first filing
Mar 14, 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. JUL 13Leak siteransomhub postfirst filing · attacker claim · unverifiedday 0
  2. AUG 26Leak siteransomhub postattacker claim · unverified+44d
  3. JAN 13NH AGNH AG notice2 NH residents+184d
  4. MAR 1IL AGIL AG noticeno count stated+231d
  5. MAR 11OR AGOR AG noticestates nationwide total 78,713+241d
  6. MAR 11WA AGWA AG notice2,660 WA residents+241d
  7. MAR 11CA AGCA AG noticeno count stated+241d
  8. MAR 11VT AGVT AG noticeno count stated+241d
  9. MAR 11NE AGNE AG noticeno count stated+241d
  10. MAR 11MT AGMT AG notice79 MT residents+241d
  11. MAR 11IN AGIN AG noticestates nationwide total 78,713+241d
  12. MAR 11ME AGME AG noticestates nationwide total 78,713+241d
  13. MAR 11MD AGMD AG notice1,000 MD residents+241d
  14. MAR 14NH AGNH AG noticemost recent · 938 NH residents+244d
  15. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
Jul 13, 2024
NH AG
Discovered
Jul 13, 2024NH AG + IL AG + WA AG +4Jan 10, 2025MD AG + NH AGFeb 11, 2025OR AG + NE AGfilings disagree on discovery
Data types
Identity (basic) · Government ID · PII
NH AG + WA AG + CA AG +4
Attack vector
Unauthorized Access
NH 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)

78,713

Sum of filed state slices

5,615· 7.1% of stated

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

US78,713
WA2,660
MD1,000
NH938
IN914
MT79
ME24

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

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

Press / market report

No press coverage linked yet.

State AG / regulator filing12 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 25, 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

244 days

Cadence

~1 / 18.8d

vs. multi-state median

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