All incidents View linkage analytics →Get the evidence package — $79 what’s inside →

Confirmed8 filings · 7 statesUnverified claimConfirmedEnforcedakirahigh sensitivity

Merged incident · 8 filings

Visionary Integration Professionals — September 2023 breach

Clustered 8 filings across 8 jurisdictions · filing window Oct 19, 2023 → Jun 3, 2024. View entity profile → Other incidents for this victim →

⚠ 1 cross-filing discrepancy →Merge100%

Determination

Confirmed

Members

8 filings

States

Affected · reported

3,433

First → last filing

Oct 19, 2023 → Jun 3, 2024

Merge confidence

100%

incident inc_7fa66b14df31446b · merged by deterministic · confidence 100%

Confirmed breach. Merged as one breach: 7 regulatory filings and 1 unverified claim. The filings describe unauthorized access. Intrusion Sep 21, 2023, discovered Sep 21, 2023 — the first regulatory filing landed 207 days later (flagged late). 3,433 individuals reported across the linked filings. Data reported: Government ID, PII, Identity (basic), and 2 more. Notifications rolled out on a 228-day schedule across 7 filings beginning Oct 19, 2023. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Supplemental

Notification delay

207days

Discovered → first regulatory filing

Discovery variance

0days

Range of discovered_at dates across filings

Leak precedence

179days 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

228days

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 >45 bdayMaine✗ ME AG >90d · 256dLeak gap⏱ Leak >90dFull clock table in Litigation Timeline

Sensitive data

identity_government

Incident timeline

Sep 21, 2023breach begins

Sep 21, 2023discovered

notification delay · 207 days

Apr 15, 2024first filing

Jun 3, 2024most recent filing

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

Member cascade — every filing about this breach

OCT 19Leak siteakira postfirst filing · attacker claim · unverifiedoperator-confirmedday 0
APR 15IN AGIN AG noticestates nationwide total 3,433auto-linked+179d
APR 15CA AGCA AG noticeno count statedauto-linked+179d
APR 15MT AGMT AG notice3 MT residentsauto-linked+179d
APR 15VT AGVT AG noticeno count statedauto-linked+179d
APR 15NH AGNH AG notice3 NH residents+179d
APR 16MA AGMA AG notice37 MA residentsauto-linked+180d
JUN 3ME AGME AG noticemost recent · states nationwide total 3,433auto-linked+228d
Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window: Sep 21, 2023
Discovered: Sep 21, 2023
Data types: Financial account · Identity (basic) · Government ID · PCI · PII
Attack vector: Unauthorized Access

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,433

Sum of filed state slices

49· 1.4% of stated

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

US3,433

MA37

IN5

MT3

NH3

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 claim1 member

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

Press / market report

No press coverage linked yet.

State AG / regulator filing7 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 9, 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

228 days

Cadence

~1 / 32.6d

vs. multi-state median

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