DisclosureLens
All incidentsView linkage analytics →Get the evidence package — $7.99what’s inside →
Leak SiteState AGConfirmed8 filings · 6 statesLifecycle stage 2 of 3: ConfirmedUnverified claimConfirmedEnforcedmontihigh sensitivity
Merged incident · 8 filings

Amtech Software — March 2025 breach

Clustered 8 filings across 7 jurisdictions · filing window Apr 7, 2025 → Aug 29, 2025. View entity profile → Other incidents for this victim →

⚠ 1 cross-filing discrepancy →Merge100%

Determination

Confirmed

Members

8 filings

States

6

Affected · reported

4,694

First → last filing

Apr 7, 2025 → Aug 29, 2025

Merge confidence

100%

incident inc_e52916c714f4428c · merged by deterministic · confidence 100%

Confirmed breach. Merged as one breach: 6 regulatory filings and 2 unverified claims. The filings describe unauthorized access. Intrusion Mar 11, 2025–Apr 7, 2025, discovered Apr 7, 2025 — the first regulatory filing landed 144 days later (flagged late). 4,694 individuals reported across the linked filings. Data reported: Government ID and Identity (basic). Notifications rolled out on a 144-day schedule across 6 filings beginning Apr 7, 2025. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Supplemental
Notification delay
144days

Discovered → first regulatory filing

Discovery variance
0days

Range of discovered_at dates across filings

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

Time between earliest and latest filing

Not recorded for this incident

Materiality delta · SEC filing delay — no SEC 8-K in this cluster.

Regulatory clocksMaine✗ ME AG >90d · 144dVermont✗ VT AG >45 bdayLeak gap⏱ Leak >90dFull clock table in Litigation Timeline

Sensitive data

identity_government

Incident timeline

Mar 11, 2025breach begins
Apr 7, 2025discovered
notification delay · 144 days
Aug 29, 2025first 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. APR 7Leak sitemonti postfirst filing · attacker claim · unverifiedday 0
  2. MAY 7Leak sitemonti postattacker claim · unverified+31d
  3. AUG 29NE AGNE AG notice6 NE residents+144d
  4. AUG 29ME AGME AG notice4 ME residents+144d
  5. AUG 29VT AGVT AG noticeno count stated+144d
  6. AUG 29MA AGMA AG notice6 MA residents+144d
  7. AUG 29MT AGMT AG notice3 MT residents+144d
  8. AUG 29IN AGIN AG noticemost recent · states nationwide total 4,694+144d
  9. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
Mar 11, 2025 – Apr 7, 2025
NE AG
Discovered
Apr 7, 2025· 27d undetected
NE AG + ME AG + VT AG +1
Data types
Identity (basic) · Government ID
NE AG + ME AG + VT AG +2
Attack vector
Unauthorized Access
NE 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)

4,694

Sum of filed state slices

335· 7.1% of stated

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

US4,694
IN316
NE6
MA6
ME4
MT3

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

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

Press / market report

No press coverage linked yet.

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

144 days

Cadence

~1 / 20.6d

vs. multi-state median

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