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

WORLD LEARNING INC. — April 2023 breach

Clustered 8 records across 6 jurisdictions: 7 filings and 1 leak-site claim · filing window Jul 12, 2023 → Nov 27, 2023. View entity profile → Other incidents for this victim →

⚠ 2 cross-filing discrepancies →Merge100%

Determination

Confirmed

Members

8 records

States

6

Affected · reported

3,022

First → last filing

Jul 12, 2023 → Nov 27, 2023

Merge confidence

100%

incident inc_4dcc358b3d4e42d1 · merged by human · confidence 100%

Confirmed breach. Merged as one breach: 7 regulatory filings and 1 unverified claim. Intrusion Apr 6, 2023–Jun 6, 2023, discovered Jun 1, 2023 — the first regulatory filing landed 41 days later; 2 later filings were flagged late. 3,022 individuals reported across the linked filings. Data reported: Government ID and Identity (basic). Notifications rolled out on a 138-day schedule across 7 filings beginning Jul 12, 2023. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Supplemental
Notification delay
41days

Discovered → first regulatory filing

Discovery variance
5days

Range of discovered_at dates across filings

Leak precedence
35days 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
138days

Time between earliest and latest filing

Not recorded for this incident

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

Regulatory clocksVermont✗ VT AG >45 bdayWashington✗ WA AG >90dLeak gap⏱ Leak >90dMaine⏱ ME AG >30d · 174dFull clock table in Litigation Timeline

Sensitive data

identity_government

Incident timeline

Apr 6, 2023breach begins
Jun 1, 2023discovered · members disagree
notification delay · 41 days
Jul 12, 2023first filing
Nov 27, 2023most 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. JUN 7Leak sitelockbit_3 postfirst record · attacker claim · unverifiedday 0
  2. JUL 12VT AGVT AG noticeno count stated+35d
  3. NOV 27VT AGVT AG noticeno count stated+173d
  4. NOV 27MT AGMT AG notice5 MT residents+173d
  5. NOV 27WA AGWA AG notice1,331 WA residents+173d
  6. NOV 27ME AGME AG noticestates nationwide total 3,022+173d
  7. NOV 27NH AGNH AG notice41 NH residents+173d
  8. NOV 27MA AGMA AG noticemost recent · 114 MA residents+173d
  9. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
Apr 6, 2023 – Jun 1, 2023
VT AG
Discovered
Jun 1, 2023VT AGJun 6, 2023VT AG + MT AG + WA AG +2filings disagree on discovery
Data types
Identity (basic) · Government ID
VT AG + MT AG + WA AG +3
Attack vector
Phishing
VT 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)

3,022

Sum of filed state slices

1,525· 50.5% of stated

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

US3,022
WA1,331
MA114
NH41
ME34
MT5

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

138 days

Cadence

~1 / 23d

vs. multi-state median

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