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

Continental AG — July 2022 breach

Clustered 6 filings across 6 jurisdictions · filing window Nov 3, 2022 → Aug 28, 2023. View entity profile → Other incidents for this victim →

⚠ 2 cross-filing discrepancies →Merge100%

Determination

Confirmed

Members

6 filings

States

5

Affected · reported

5,365

First → last filing

Nov 3, 2022 → Aug 28, 2023

Merge confidence

100%

incident inc_a2ee717830ee4a02 · merged by deterministic · confidence 100%

Confirmed breach. Merged as one breach: 5 regulatory filings and 1 unverified claim. The filings describe unauthorized access. Intrusion Jul 1, 2022–Aug 5, 2022, discovered Aug 1, 2022 — the first regulatory filing landed 379 days later (flagged late). 5,365 individuals reported across the linked filings. Data reported: Government ID, Identity (basic), Financial account, and 2 more. Notifications rolled out on a 298-day schedule across 5 filings beginning Nov 3, 2022. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Notification delay
379days

Discovered → first regulatory filing

Discovery variance
3days

Range of discovered_at dates across filings

Leak precedence
285days 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
298days

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

Sensitive data

identity_government

Incident timeline

Jul 1, 2022breach begins
Aug 1, 2022discovered · members disagree
notification delay · 379 days
Aug 15, 2023first filing
Aug 28, 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. NOV 3Leak sitelockbit_3 postfirst filing · attacker claim · unverifiedday 0
  2. AUG 15VT AGVT AG noticeno count stated+285d
  3. AUG 15IN AGIN AG noticestates nationwide total 5,365+285d
  4. AUG 23ME AGME AG noticestates nationwide total 5,365+293d
  5. AUG 24NH AGNH AG notice18 NH residents+294d
  6. AUG 28MA AGMA AG noticemost recent · 16 MA residents+298d
  7. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
Jul 4, 2022 – Aug 5, 2022
VT AG
Discovered
Aug 1, 2022VT AGAug 4, 2022ME AG + NH AGfilings disagree on discovery
Data types
Employment · Financial account · Health (basic) · Identity (basic) · Government ID
VT AG + ME AG + NH AG +1
Attack vector
Unauthorized Access
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)

5,365

Sum of filed state slices

429· 8.0% of stated

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

US5,365
IN393
NH18
MA16
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 filing5 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 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

298 days

Cadence

~1 / 59.6d

vs. multi-state median

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