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

Northern Safety Co., Inc. — June 2024 breach

Clustered 9 filings across 4 jurisdictions · filing window Jun 7, 2024 → Dec 2, 2024. View entity profile → Other incidents for this victim →

⚠ 1 cross-filing discrepancy →Merge100%

Determination

Confirmed

Members

9 filings

States

3

Affected · reported

1,873

First → last filing

Jun 7, 2024 → Dec 2, 2024

Merge confidence

100%

incident inc_6dae7426fa9e4fa7 · merged by human · confidence 100%

Confirmed breach. Merged as one breach: 4 regulatory filings and 5 unverified claims. The filings describe a ransomware attack. Intrusion Jun 7, 2024, discovered Jun 7, 2024 — the first regulatory filing landed 171 days later. 1,873 individuals reported across the linked filings. Data reported: Government ID and Identity (basic). Notifications rolled out on a 178-day schedule across 4 filings beginning Jun 7, 2024. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Notification delay
171days

Discovered → first regulatory filing

Discovery variance
0days

Range of discovered_at dates across filings

Leak precedence
171days 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
178days

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 >90dFull clock table in Litigation Timeline

Sensitive data

identity_government

Incident timeline

Jun 7, 2024breach begins
Jun 7, 2024discovered
notification delay · 171 days
Nov 25, 2024first filing
Dec 2, 2024most 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. JUN 7Leak siteblack_basta postfirst filing · attacker claim · unverifiedday 0
  2. JUN 7Leak siteblack_basta postattacker claim · unverifiedday 0
  3. SEP 16Leak siteapt73 postattacker claim · unverified+101d
  4. SEP 16Leak siteblack_basta postattacker claim · unverified+101d
  5. OCT 23Leak siteapt73 postattacker claim · unverified+138d
  6. NOV 25IN AGIN AG noticestates nationwide total 1,873+171d
  7. NOV 25NH AGNH AG notice3 NH residents+171d
  8. NOV 25MA AGMA AG notice4 MA residents+171d
  9. DEC 2NH AGNH AG noticemost recent · 3 NH residents+178d
  10. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
Jun 7, 2024
IN AG
Discovered
Jun 7, 2024
NH AG
Data types
Identity (basic) · Government ID
NH AG + MA AG
Attack vector
Ransomware· Black Basta
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,873

Sum of filed state slices

56· 3.0% of stated

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

US1,873
IN49
MA4
NH3

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

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

Press / market report

No press coverage linked yet.

State AG / regulator filing4 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

178 days

Cadence

~1 / 22.3d

vs. multi-state median

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