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

Transak, Inc. — September 2024 breach

Clustered 9 filings across 9 jurisdictions · filed Feb 28, 2025 (dated filings only). View entity profile → Other incidents for this victim →

⚠ 1 cross-filing discrepancy →Merge100%

Determination

Confirmed

Members

9 filings

States

9

Affected · reported

23,113

First → last dated filing

Feb 28, 2025

Merge confidence

100%

incident inc_570e0c37eee842f1 · merged by deterministic · confidence 100%

Confirmed breach. Merged as one breach: 9 regulatory filings. The filings describe unauthorized access. Intrusion Sep 1, 2024, discovered Sep 23, 2024. 23,113 individuals reported across the linked filings. Data reported: Government ID, Identity (basic), Financial account, and 1 more. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Supplemental
Discovery variance
0days

Range of discovered_at dates across filings

Filing span
0days

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 clocksMaryland✗ MD AG >90dMaine⏱ ME AG >30d · 158dFull clock table in Litigation Timeline

Sensitive data

identity_government

Incident timeline

Sep 1, 2024breach begins
Sep 23, 2024discovered
Feb 28, 2025first dated filing
—watching for filings

Dashed segments are unestablished, not zero — they fill in as filings merge into this incident. Filings without a recorded filing day, or recorded as filed before the breach they report began, are not placed on this rail.

Member cascade — every filing about this breach

  1. FEB 1IL AGIL AG noticefiling day not on record · no count stated—
  2. FEB 28ME AGME AG noticefirst filing · states nationwide total 23,113day 0
  3. FEB 28MA AGMA AG notice543 MA residentsday 0
  4. FEB 28VT AGVT AG noticeno count statedday 0
  5. FEB 28MD AGMD AG noticestates nationwide total 23,113day 0
  6. FEB 28NE AGNE AG noticefiling day not on record · no count stated—
  7. FEB 28IN AGIN AG noticestates nationwide total 23,113day 0
  8. FEB 28NH AGNH AG noticestates nationwide total 23,113day 0
  9. FEB 28CA AGCA AG noticemost recent · no count statedday 0
  10. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
Sep 1, 2024
ME AG
Discovered
Sep 23, 2024· 22d undetected
IL AG + ME AG + MD AG +2
Data types
Financial account · Identity (basic) · Government ID · PII
ME AG + VT AG + MD AG +3
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)

23,113

Sum of filed state slices

1,654· 7.2% of stated

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

US23,113
MD554
MA543
IN418
NH75
ME64

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

0 days

Cadence

~1 / 0d

vs. multi-state median

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