DisclosureLens
Leak SiteState AGConfirmed6 records · 5 statesLifecycle stage 2 of 3: ConfirmedUnverified claimConfirmedEnforcedplayhigh sensitivity
Merged incident · 6 records

ALL STATES MATERIALS GROUP, INC. — August 2025 breach

Clustered 6 records across 5 jurisdictions: 5 filings and 1 leak-site claim · filed Sep 23, 2025. View entity profile → Other incidents for this victim →

⚠ 1 cross-filing discrepancy →Merge100%

Determination

Confirmed

Members

6 records

States

5

Affected · reported

3,268

First → last filing

Sep 23, 2025

Merge confidence

100%

incident inc_3a09babaa1314e8a · merged by human · confidence 100%

Confirmed breach. Merged as one breach: 5 regulatory filings and 1 unverified claim. Intrusion Aug 22, 2025–Aug 25, 2025, discovered Aug 25, 2025 — the first regulatory filing landed 29 days later. 3,268 individuals reported across the linked filings. Data reported: Government ID, Identity (basic), Financial account, and 3 more. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Supplemental
Notification delay
29days

Discovered → first regulatory filing

Discovery variance
0days

Range of discovered_at dates across filings

Leak precedence
22days before filing

Days between the first sighting of the earliest-seen leak-site claim and the first regulatory filing. Measured from when the aggregator first saw the post, not the crew's own (often earlier) date. 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
0days

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 bdayMassachusetts✓ MA credit monitoring dueMaine✓ ME AG ≤30d · 29dFull clock table in Litigation Timeline

Sensitive data

identity_government

Incident timeline

Aug 22, 2025breach begins
Aug 25, 2025discovered
notification delay · 29 days
Sep 23, 2025first filing
—watching for filings

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

Member cascade — every filing and leak-site claim in this incident

  1. AUG 25Leak siteplay postfirst record · attacker claim · unverifiedday 0
  2. SEP 23VT AGVT AG noticeno count stated+29d
  3. SEP 23MA AGMA AG notice1,826 MA residents+29d
  4. SEP 23NH AGNH AG notice44 NH residents+29d
  5. SEP 23ME AGME AG noticestates nationwide total 3,268+29d
  6. SEP 23IN AGIN AG noticemost recent · states nationwide total 3,268+29d
  7. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
Aug 22, 2025 – Aug 25, 2025
VT AG
Discovered
Aug 25, 2025· 3d undetected
VT AG + NH AG + ME AG
Data types
Employment · Financial account · Health (basic) · Identity (basic) · Government ID · PII
VT AG + NH AG + ME AG +1
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)

3,268

Sum of filed state slices

2,407· 73.7% of stated

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

US3,268
MA1,826
ME536
NH44
IN1

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

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.