DisclosureLens
All incidentsView linkage analytics →Get the evidence package — $7.99what’s inside →
State AGConfirmed9 filings · 9 statesLifecycle stage 2 of 3: ConfirmedUnverified claimConfirmedEnforcedhigh sensitivity
Merged incident · 9 filings

Blade HQ — January 2021 breach

Clustered 9 filings across 9 jurisdictions · filing window Apr 19, 2021 → Apr 24, 2021. View entity profile → Other incidents for this victim →

⚠ 2 cross-filing discrepancies →Merge100%

Determination

Confirmed

Members

9 filings

States

9

Affected · reported

90,000

First → last filing

Apr 19, 2021 → Apr 24, 2021

Merge confidence

100%

incident inc_959e59b379aa43ee · merged by deterministic · confidence 100%

Confirmed breach. Merged as one breach: 9 regulatory filings. The filings describe unauthorized access. Intrusion Jan 7, 2021–Apr 11, 2021, discovered Mar 18, 2021 — the first regulatory filing landed 32 days later. 90,000 individuals reported across the linked filings. Data reported: Identity (basic), Financial account, Financial credentials, and 1 more. Notifications rolled out on a 5-day schedule across 9 filings beginning Apr 19, 2021. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Notification delay
32days

Discovered → first regulatory filing

Discovery variance
13days

Range of discovered_at dates across filings

Filing span
5days

Time between earliest and latest filing

Not recorded for this incident

Leak precedence · Materiality delta · SEC filing delay — no leak-site claim in this cluster; no SEC 8-K in this cluster.

Regulatory clocksWashington⏱ WA AG >30dOregon✓ OR AG ≤45dSouth Carolina✓ SC CRA notice dueCalifornia✓ CA 60-day OK · 19dMaine✓ ME AG ≤30d · 29dFull clock table in Litigation Timeline

Sensitive data

financial_credentials

Incident timeline

Jan 7, 2021breach begins
Mar 18, 2021discovered · members disagree
notification delay · 32 days
Apr 19, 2021first filing
Apr 24, 2021most 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. APR 19NH AGNH AG noticefirst filing · 651 NH residentsday 0
  2. APR 19OR AGOR AG noticestates nationwide total 90,000day 0
  3. APR 19SC AGSC AG notice1,334 SC residentsday 0
  4. APR 19CA AGCA AG noticeno count statedday 0
  5. APR 19WA AGWA AG notice3,090 WA residentsday 0
  6. APR 20MT AGMT AG notice469 MT residents+1d
  7. APR 20ME AGME AG noticestates nationwide total 90,000+1d
  8. APR 21IN AGIN AG noticestates nationwide total 90,000+2d
  9. APR 24MA AGMA AG noticemost recent · 1,863 MA residents+5d
  10. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
Jan 7, 2021 – Apr 11, 2021
NH AG
Discovered
Mar 18, 2021NH AG + SC AG + WA AGMar 22, 2021OR AG + ME AGMar 25, 2021MT AGMar 31, 2021CA AGfilings disagree on discovery
Data types
Financial account · Financial credentials · Identity (basic) · PCI
NH AG + SC 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)

90,000

Sum of filed state slices

10,122· 11.2% of stated

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

US90,000
WA3,090
IN2,158
MA1,863
SC1,334
NH651
ME557
MT469

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 claim

No leak-site claim on record for this incident.

Press / market report

No press coverage linked yet.

State AG / regulator filing9 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 Jun 12, 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

5 days

Cadence

~1 / 0.6d

vs. multi-state median

1.8× faster

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.