DisclosureLens
Leak SiteState AGConfirmed5 filings · 3 statesLifecycle stage 2 of 3: ConfirmedUnverified claimConfirmedEnforcedrhysidahigh sensitivity
Merged incident · 5 filings

JASCO Applied Sciences — July 2025 breach

Clustered 5 filings across 4 jurisdictions · filing window Jul 21, 2025 Dec 3, 2025. View entity profile → Other incidents for this victim →

Determination

Confirmed

Members

5 filings

States

3

Affected · reported

66

First → last filing

Jul 21, 2025 Dec 3, 2025

Merge confidence

100%

incident inc_000830d651cd476b · merged by human · confidence 100%

Confirmed breach. Merged as one breach: 3 regulatory filings and 2 unverified claims. The filings describe unauthorized access. Intrusion Jul 21, 2025, discovered Jul 21, 2025 — the first regulatory filing landed 128 days later. 66 individuals reported across the linked filings. Data reported: Government ID, Identity (basic), Financial account, and 2 more. Notifications rolled out on a 135-day schedule across 3 filings beginning Jul 21, 2025. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Supplemental
Notification delay
128days

Discovered → first regulatory filing

Discovery variance
91days

Range of discovered_at dates across filings

Leak precedence
128days 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
135days

Time between earliest and latest filing

Not recorded for this incident

Materiality delta · SEC filing delayno SEC 8-K in this cluster.

Regulatory clocksLeak gap Leak >90dMaine ME AG >30d · 37dFull clock table in Litigation Timeline

Sensitive data

identity_government

Incident timeline

Jul 21, 2025breach begins
Jul 21, 2025discovered · members disagree
notification delay · 128 days
Nov 26, 2025first filing
Dec 3, 2025most 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. JUL 21Leak siterhysida postfirst filing · attacker claim · unverifiedday 0
  2. OCT 7Leak siterhysida postattacker claim · unverified+78d
  3. NOV 26NH AGNH AG notice1 NH residents+128d
  4. NOV 26ME AGME AG noticestates nationwide total 66+128d
  5. DEC 3MA AGMA AG noticemost recent · 4 MA residents+135d
  6. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
Jul 21, 2025
ME AG
Discovered
Jul 21, 2025NH AGOct 20, 2025ME AGfilings disagree on discovery
Data types
Employment · Financial account · Health (basic) · Identity (basic) · Government ID
NH AG + ME AG + MA AG
Attack vector
Unauthorized Access
NH 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)

66

Sum of filed state slices

6· 9.1% of stated

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

US66
MA4
NH1
ME1

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

135 days

Cadence

~1 / 33.8d

vs. multi-state median

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