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

SinglePoint Outsourcing, Inc. — November 2023 breach

Clustered 8 filings across 6 jurisdictions · filing window Nov 28, 2023 → Apr 12, 2024. View entity profile → Other incidents for this victim →

⚠ 2 cross-filing discrepancies →Merge100%

Determination

Confirmed

Members

8 filings

States

5

Affected · reported

11,096

First → last filing

Nov 28, 2023 → Apr 12, 2024

Merge confidence

100%

incident inc_40daea3e15424938 · merged by deterministic · confidence 100%

Confirmed breach. Merged as one breach: 7 regulatory filings and 1 unverified claim. The filings describe unauthorized access. Intrusion Nov 8, 2023–Nov 9, 2023, discovered Nov 30, 2023 — the first regulatory filing landed 70 days later (flagged late). 11,096 individuals reported across the linked filings. Data reported: Government ID, Identity (basic), Financial account, and 1 more. Notifications rolled out on a 135-day schedule across 7 filings beginning Nov 28, 2023. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Notification delay
70days

Discovered → first regulatory filing

Discovery variance
42days

Range of discovered_at dates across filings

Leak precedence
71days 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 delay — no SEC 8-K in this cluster.

Regulatory clocksCalifornia✗ CA 60-day late · 74dVermont✗ VT AG >45 bdayMaine✗ ME AG >90d · 92dLeak gap⏱ Leak >30dFull clock table in Litigation Timeline

Sensitive data

financial_credentialsidentity_government

Incident timeline

Nov 8, 2023breach begins
Nov 30, 2023discovered · members disagree
notification delay · 70 days
Feb 8, 2024first filing
Apr 12, 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

  1. NOV 28Leak siteplay postfirst filing · attacker claim · unverifiedday 0
  2. FEB 8IN AGIN AG noticestates nationwide total 5,175+71d
  3. FEB 8MT AGMT AG notice8 MT residents+71d
  4. FEB 8CA AGCA AG noticeno count stated+71d
  5. FEB 12VT AGVT AG noticeno count stated+75d
  6. MAR 26CA AGCA AG noticeno count stated+118d
  7. APR 12ME AGME AG noticestates nationwide total 11,096+135d
  8. APR 12CA AGCA AG noticemost recent · no count stated+135d
  9. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
Nov 8, 2023
IN AG
Discovered
Nov 30, 2023MT AG + CA AG + VT AGJan 11, 2024ME AGfilings disagree on discovery
Data types
Financial account · Financial credentials · Identity (basic) · Government ID
MT AG + CA AG + VT AG +1
Attack vector
Unauthorized Access
MT 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)

11,096

Sum of filed state slices

50· 0.5% of stated

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

US11,096
IN40
MT8
ME2

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

135 days

Cadence

~1 / 19.3d

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.