DisclosureLens
All incidentsView linkage analytics →Get the evidence package — $7.99what’s inside →
Leak SitePressState AGConfirmed10 filings · 6 statesLifecycle stage 2 of 3: ConfirmedUnverified claimConfirmedEnforcedhigh sensitivity
Merged incident · 10 filings

CONTINENTAL AEROSPACE TECHNOLOGIES, INC. — February 2024 breach

Clustered 10 filings across 7 jurisdictions · filing window Feb 12, 2024 → Mar 25, 2025. View entity profile → Other incidents for this victim →

⚠ 2 cross-filing discrepancies →Merge100%

Determination

Confirmed

Members

10 filings

States

6

Affected · reported

2,605

First → last filing

Feb 12, 2024 → Mar 25, 2025

Merge confidence

100%

incident inc_e094bcd83c0d4cce · merged by deterministic · confidence 100%

Confirmed breach. Merged as one breach: 6 regulatory filings, 1 press report and 3 unverified claims. The filings describe unauthorized access. Intrusion Feb 12, 2024–Feb 13, 2024, discovered Feb 13, 2024 — the first regulatory filing landed 394 days later (flagged late). 2,605 individuals reported across the linked filings. Data reported: Government ID, Identity (basic), Financial account, and 1 more. Notifications rolled out on a 407-day schedule across 6 filings beginning Feb 12, 2024. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Supplemental
Notification delay
394days

Discovered → first regulatory filing

Discovery variance
272days

Range of discovered_at dates across filings

Leak precedence
395days 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
407days

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

Sensitive data

identity_government

Incident timeline

Feb 12, 2024breach begins
Feb 13, 2024discovered · members disagree
notification delay · 394 days
Mar 13, 2025first filing
Mar 25, 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. FEB 12Leak sitekraken postfirst filing · attacker claim · unverifiedday 0
  2. FEB 12Leak siteplay postattacker claim · unverifiedday 0
  3. FEB 20Leak siteplay postattacker claim · unverified+8d
  4. MAR 13IN AGIN AG noticestates nationwide total 2,605+395d
  5. MAR 13MD AGMD AG notice9 MD residents+395d
  6. MAR 13ME AGME AG noticestates nationwide total 2,605+395d
  7. MAR 13MT AGMT AG notice3 MT residents+395d
  8. MAR 13NE AGNE AG noticeno count stated+395d
  9. MAR 25NH AGNH AG noticemost recent · 2 NH residents+407d
  10. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
Feb 13, 2024
IN AG
Discovered
Feb 13, 2024MD AG + MT AG + NH AGNov 11, 2024ME AG + NE AGfilings disagree on discovery
Data types
Financial account · Identity (basic) · Government ID · PII
MD AG + ME AG + MT AG +1
Attack vector
Unauthorized Access
ME 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)

2,605

Sum of filed state slices

30· 1.2% of stated

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

US2,605
IN13
MD9
ME3
MT3
NH2

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

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

Press / market report1 member

Unlocks: incident narrative, operational impact. Still no compliance clock.

State AG / regulator filing6 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 May 30, 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

407 days

Cadence

~1 / 45.2d

vs. multi-state median

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