DisclosureLens
All incidentsView linkage analytics →Get the evidence package — $79what’s inside →
Leak SiteState AGConfirmed6 filings · 5 statesLifecycle stage 2 of 3: ConfirmedUnverified claimConfirmedEnforcedakirahigh sensitivity
Merged incident · 6 filings

Posillico, Inc. — December 2025 breach

Clustered 6 filings across 6 jurisdictions · filing window Jan 5, 2026 → Jan 14, 2026. View entity profile → Other incidents for this victim →

⚠ 2 cross-filing discrepancies →Merge100%

Determination

Confirmed

Members

6 filings

States

5

Affected · reported

9,876

First → last filing

Jan 5, 2026 → Jan 14, 2026

Merge confidence

100%

incident inc_af35d9400dc9459e · merged by deterministic · confidence 100%

Confirmed breach. Merged as one breach: 5 regulatory filings and 1 unverified claim. The filings describe unauthorized access. Intrusion Dec 8, 2025, discovered Dec 8, 2025 — the first regulatory filing landed 36 days later. 9,876 individuals reported across the linked filings. Data reported: Government ID and Identity (basic). Notifications rolled out on a 9-day schedule across 5 filings beginning Jan 5, 2026. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Notification delay
36days

Discovered → first regulatory filing

Discovery variance
29days

Range of discovered_at dates across filings

Leak precedence
8days 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
9days

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 >30d · 36dTexas✓ TX AG ≤30dMassachusetts✓ MA credit monitoring dueFull clock table in Litigation Timeline

Sensitive data

identity_government

Incident timeline

Dec 8, 2025breach begins
Dec 8, 2025discovered · members disagree
notification delay · 36 days
Jan 13, 2026first filing
Jan 14, 2026most 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. JAN 5Leak siteakira postfirst filing · attacker claim · unverifiedday 0
  2. JAN 13ME AGME AG noticestates nationwide total 9,876+8d
  3. JAN 13IN AGIN AG noticestates nationwide total 9,876+8d
  4. JAN 14NH AGNH AG notice4 NH residents+9d
  5. JAN 14TX AGTX AG noticestates nationwide total 9,876+9d
  6. JAN 14MA AGMA AG noticemost recent · 22 MA residents+9d
  7. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
Dec 8, 2025
ME AG
Discovered
Dec 8, 2025ME AG + NH AGJan 6, 2026TX AGfilings disagree on discovery
Data types
Identity (basic) · Government ID
ME AG + NH AG + TX 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)

9,876

Sum of filed state slices

1,061· 10.7% of stated

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

US9,876
TX1,021
MA22
IN11
NH4
ME3

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

9 days

Cadence

~1 / 1.8d

vs. multi-state median

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