DisclosureLens
State AGConfirmed2 filings · 2 statesLifecycle stage 2 of 3: ConfirmedUnverified claimConfirmedEnforcedmoderate sensitivity
Merged incident · 2 filings

'47 BRAND, LLC — April 2019 breach

Clustered 2 filings across 2 jurisdictions · filing window Sep 16, 2019 Sep 24, 2019. View entity profile → Other incidents for this victim →

Determination

Confirmed

Members

2 filings

States

2

Affected · reported

24

First → last filing

Sep 16, 2019 Sep 24, 2019

Merge confidence

95%

incident inc_2c14e569e080452e · merged by deterministic · confidence 95%

Confirmed breach. Merged as one breach: 2 regulatory filings. The filings describe unauthorized access. Intrusion Apr 30, 2019–May 7, 2019, discovered May 1, 2019 — the first regulatory filing landed 138 days later. 24 individuals reported across the linked filings. Data reported: PII, Identity (basic), Financial account, and 1 more. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Notification delay
138days

Discovered → first regulatory filing

Discovery variance
0days

Range of discovered_at dates across filings

Filing span
8days

Time between earliest and latest filing

Not recorded for this incident

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

Incident timeline

Apr 30, 2019breach begins
May 1, 2019discovered
notification delay · 138 days
Sep 16, 2019first filing
Sep 24, 2019most 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. SEP 16MT AGMT AG noticefirst filing · 13 MT residentsday 0
  2. SEP 24NH AGNH AG noticemost recent · 11 NH residents+8d
  3. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
Apr 30, 2019May 1, 2019
MT AG
Discovered
May 1, 2019· 1d undetected
MT AG + NH AG
Data types
Credentials · Financial account · Identity (basic) · PII
MT AG + NH AG
Attack vector
Unauthorized Access
MT AG

Each fact cites the member filing that establishes it; when filings conflict, every value shows with its source.

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 filing2 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
0.95 · above the 0.85 auto-merge floor
Audit
Every link edge records its method, confidence and model + prompt versions (95% is the strongest edge).

Merges are reversible — a wrong link can be detached with its audit trail intact. How merging works.

Filing velocity

Spread

8 days

vs. multi-state median

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