DisclosureLens
All incidentsView linkage analytics →Get the evidence package — $7.99what’s inside →
State AGConfirmed10 filings · 10 statesLifecycle stage 2 of 3: ConfirmedUnverified claimConfirmedEnforcedhigh sensitivity
Merged incident · 10 filings

360training.com, Inc. — July 2025 breach

Clustered 10 filings across 10 jurisdictions · filing window Feb 24, 2026 → Feb 25, 2026 (dated filings only). View entity profile → Other incidents for this victim →

⚠ 2 cross-filing discrepancies →Merge100%

Determination

Confirmed

Members

10 filings

States

10

Affected · reported

24,594

First → last dated filing

Feb 24, 2026 → Feb 25, 2026

Merge confidence

100%

incident inc_f3e0a043be954a8d · merged by deterministic · confidence 100%

Confirmed breach. Merged as one breach: 10 regulatory filings. The filings describe unauthorized access. Intrusion Jul 27, 2025–Jan 19, 2026, discovered Nov 25, 2025 — the first regulatory filing landed 91 days later (flagged late). 24,594 individuals reported across the linked filings. Data reported: Government ID, PII, Financial account, and 2 more. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Supplemental
Notification delay
91days

Discovered → first regulatory filing

Discovery variance
55days

Range of discovered_at dates across filings

Filing span
1days

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 clocksWashington✗ WA AG >90dMaine⏱ ME AG >30d · 91dFull clock table in Litigation Timeline

Sensitive data

identity_government

Incident timeline

Jul 27, 2025breach begins
Nov 25, 2025discovered · members disagree
notification delay · 91 days
Feb 24, 2026first dated filing
Feb 25, 2026most recent dated filing

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 24IN AGIN AG noticefirst filing · states nationwide total 24,594day 0
  2. FEB 24CA AGCA AG noticeno count statedday 0
  3. FEB 24WA AGWA AG notice642 WA residentsday 0
  4. FEB 24NE AGNE AG noticefiling day not on record · no count stated—
  5. FEB 24NH AGNH AG notice145 NH residentsday 0
  6. FEB 24VT AGVT AG noticeno count statedday 0
  7. FEB 25ME AGME AG noticestates nationwide total 24,594+1d
  8. FEB 25TX AGTX AG noticestates nationwide total 24,594+1d
  9. FEB 25MA AGMA AG noticemost recent · 323 MA residents+1d
  10. MAR 1IL AGIL AG noticefiling day not on record · no count stated—
  11. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
Nov 25, 2025
IN AG
Discovered
Nov 25, 2025WA AG + NH AG + IL AGNov 26, 2025NE AG + ME AGJan 19, 2026TX AGfilings disagree on discovery
Data types
Financial account · Identity (basic) · Government ID · PCI · PII
CA AG + WA AG + NE AG +6
Attack vector
Unauthorized Access
CA 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)

24,594

Sum of filed state slices

3,757· 15.3% of stated

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

US24,594
TX2,391
WA642
MA323
IN207
NH145
ME49

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

1 days

Cadence

~1 / 0.1d

vs. multi-state median

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