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

Overseas Shipholding Group, Inc. — July 2024 breach

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

⚠ 2 cross-filing discrepancies →Merge100%

Determination

Confirmed

Members

9 filings

States

8

Affected · reported

8,085

First → last filing

Aug 19, 2024 → Dec 2, 2024

Merge confidence

100%

incident inc_66130b6dcd0e4b2e · merged by human · confidence 100%

Confirmed breach. Merged as one breach: 8 regulatory filings and 1 unverified claim. Intrusion Jul 31, 2024–Aug 5, 2024, discovered Aug 5, 2024 — the first regulatory filing landed 119 days later. 8,085 individuals reported across the linked filings. Data reported: Government ID, Identity (basic), and PII. Notifications rolled out on a 104-day schedule across 8 filings beginning Aug 19, 2024. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Supplemental
Notification delay
119days

Discovered → first regulatory filing

Discovery variance
84days

Range of discovered_at dates across filings

Leak precedence
104days 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
104days

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 >14 bdayLeak gap⏱ Leak >90dMaine⏱ ME AG >30d · 35dFull clock table in Litigation Timeline

Sensitive data

identity_government

Incident timeline

Jul 31, 2024breach begins
Aug 5, 2024discovered · members disagree
notification delay · 119 days
Dec 2, 2024first filing
—watching for filings

Dashed segments are unestablished, not zero — they fill in as filings merge into this incident.

Member cascade — every filing about this breach

  1. AUG 19Leak siteransomhub postfirst filing · attacker claim · unverifiedday 0
  2. DEC 2VT AGVT AG noticeno count stated+104d
  3. DEC 2MA AGMA AG notice299 MA residents+104d
  4. DEC 2MT AGMT AG notice13 MT residents+104d
  5. DEC 2CA AGCA AG noticeno count stated+104d
  6. DEC 2WA AGWA AG notice956 WA residents+104d
  7. DEC 2IN AGIN AG noticestates nationwide total 8,085+104d
  8. DEC 2ME AGME AG noticestates nationwide total 8,085+104d
  9. DEC 2NH AGNH AG noticemost recent · 92 NH residents+104d
  10. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
Aug 5, 2024
CA AG
Discovered
Aug 5, 2024WA AGOct 28, 2024VT AG + MT AG + ME AGfilings disagree on discovery
Data types
Identity (basic) · Government ID · PII
VT AG + MT AG + CA AG +4
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)

8,085

Sum of filed state slices

1,591· 19.7% of stated

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

US8,085
WA956
MA299
ME217
NH92
IN14
MT13

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

104 days

Cadence

~1 / 13d

vs. multi-state median

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