DisclosureLens
All incidentsView linkage analytics →Get the evidence package — $7.99what’s inside →
Leak SiteState AGConfirmed8 records · 5 statesLifecycle stage 2 of 3: ConfirmedUnverified claimConfirmedEnforcedransomhubhigh sensitivity
Merged incident · 8 records

Wong Fleming — December 2024 breach

Clustered 8 records across 5 jurisdictions: 7 filings and 1 leak-site claim · filing window Jul 14, 2025 → Jan 20, 2026. View entity profile → Other incidents for this victim →

⚠ 2 cross-filing discrepancies →Merge100%

Determination

Confirmed

Members

8 records

States

5

Affected · reported

1,360

First → last filing

Jul 14, 2025 → Jan 20, 2026

Merge confidence

100%

incident inc_da1e7d29561740d9 · merged by human · confidence 100%

Confirmed breach. Merged as one breach: 7 regulatory filings and 1 unverified claim. The filings describe unauthorized access. Intrusion Dec 13, 2024–Dec 14, 2024, discovered Dec 14, 2024 — the first regulatory filing landed 212 days later; 1 later filing was flagged late. 1,360 individuals reported across the linked filings. Data reported: Government ID, Identity (basic), and PII. Notifications rolled out on a 190-day schedule across 7 filings beginning Jul 14, 2025. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Supplemental
Notification delay
212days

Discovered → first regulatory filing

Discovery variance
222days

Range of discovered_at dates across filings

Leak precedence
161days before filing

Days between the first sighting of the earliest-seen leak-site claim and the first regulatory filing. Measured from when the aggregator first saw the post, not the crew's own (often earlier) date. 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
190days

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 >180dVermont✗ VT AG >45 bdayFull clock table in Litigation Timeline

Sensitive data

identity_government

Incident timeline

Dec 13, 2024breach begins
Dec 14, 2024discovered · members disagree
notification delay · 212 days
Jul 14, 2025first filing
Jan 20, 2026most recent filing

Dashed segments are unestablished, not zero — they fill in as filings merge into this incident.

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

  1. DEC 14Leak siteransomhub postfirst record · attacker claim · unverifiedday 0
  2. JUL 14NH AGNH AG notice1 NH residents+212d
  3. AUG 29IN AGIN AG noticestates nationwide total 1,360+258d
  4. AUG 29ME AGME AG notice2 ME residents+258d
  5. AUG 29MA AGMA AG notice4 MA residents+258d
  6. AUG 29VT AGVT AG noticeno count stated+258d
  7. AUG 29NH AGNH AG notice3 NH residents+258d
  8. JAN 20NH AGNH AG noticemost recent · 1 NH residents+402d
  9. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
Dec 13, 2024 – Dec 14, 2024
NH AG
Discovered
Dec 14, 2024NH AG + VT AGJul 24, 2025ME AGfilings disagree on discovery
Data types
Identity (basic) · Government ID · PII
NH AG + ME AG + VT AG +1
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)

1,360

Sum of filed state slices

25· 1.8% of stated

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

US1,360
IN16
MA4
NH3
ME2

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

190 days

Cadence

~1 / 31.7d

vs. multi-state median

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