Parksite Inc. — December 2023 breach
Clustered 10 records across 6 jurisdictions: 9 filings and 1 leak-site claim · filing window May 3, 2024 → Jul 8, 2024 (dated filings only). View entity profile → Other incidents for this victim →
incident inc_9a4a673475f5483a · merged by deterministic · confidence 100%
Litigation Timing
SupplementalDiscovered → first regulatory filing
Range of discovered_at dates across filings
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.
Time between earliest and latest filing
Not recorded for this incident
Materiality delta · SEC filing delay — no SEC 8-K in this cluster.
Sensitive data
identity_governmentIncident timeline
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 and leak-site claim in this incident
- JAN 17Leak sitecactus postfirst record · attacker claim · unverifiedoperator-confirmedday 0
- MAY 3VT AGVT AG noticeno count statedoperator-confirmed+107d
- JUN 1IL AGIL AG noticefiling day not on record · no count statedauto-linked—
- JUN 7ME AGME AG noticestates nationwide total 7,886operator-confirmed+142d
- JUN 7MA AGMA AG notice255 MA residentsoperator-confirmed+142d
- JUN 7IN AGIN AG noticestates nationwide total 8,577auto-linked+142d
- JUN 10NH AGNH AG notice44 NH residentsauto-linked+145d
- JUL 2ME AGME AG noticestates nationwide total 8,577auto-linked+167d
- JUL 2VT AGVT AG noticeno count statedauto-linked+167d
- JUL 8NH AGNH AG noticemost recent · 8 NH residentsoperator-confirmed+173d
- Watching for additional filings — new sources merge into this incident automatically.
Roll-up facts — reconciled across members
- Breach window
- Dec 25, 2023 – Jan 16, 2024 ME AG
- Discovered
- Dec 25, 2023IL AGJan 16, 2024ME AG + NH AG + VT AGfilings disagree on discovery
- Data types
- Financial account · Identity (basic) · Government ID · PCI · PII VT AG + NH AG + ME AG +1
- Attack vector
- Unauthorized Access ME 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)
8,577
Sum of filed state slices
344· 4.0% of stated
96% of the stated total lives in states whose filings carry no count — the dashed share shrinks as filings land.
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
Attacker assertion only. Establishes: claim date, group, alleged victim.
No press coverage linked yet.
Unlocks: discovery date, data types, affected count, compliance clock.
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 23, 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
66 days
Cadence
~1 / 9.4d
vs. multi-state median
11.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.