Size: 2.5GB (compressed) | Updated: 13 Feb 2026 | Note: Pay or be humiliated. | They were given multiple chances to pay the ransom, but they decided to waste time and hide instead.
Clustered 3 filings across 3 jurisdictions · filing window Feb 13, 2026 → Feb 24, 2026. View entity profile → Other incidents for this victim →
incident inc_fbec51d5299a4184 · merge_method human · confidence 100%
Discovered → first regulatory filing
Gap between first leak claim and first regulatory filing
Time between earliest and latest filing
Not recorded for this incident
Discovery variance · Materiality delta · SEC filing delay — no SEC 8-K in this cluster; needs two dated filings.
IN WA
Leak Site · State AG
Earliest sighting first · deep chronology in Litigation Timeline
Jan 28, 2026
When the intrusion reportedly occurred, per the linked filings
Jan 28, 2026
Reported by WASHINGTON AG filing
Size: 2.5GB (compressed) | Updated: 13 Feb 2026 | Note: Pay or be humiliated. | They were given multiple chances to pay the ransom, but they decided to waste time and hide instead.
Figure Technology Solutions, Inc., a finance sector entity reported a phishing incident to the Washington Attorney General. The organization became aware of the incident on 2026-01-28 and filed notice on 2026-02-23. 26,128 Washington residents were affected. 26 days elapsed between awareness and notification. 0 days to identify the breach. 0 days to contain the breach.
Affected (this filing): 26,128
Figure Technology Solutions Inc reported a data breach to the Indiana Attorney General. The breach occurred on 2026-01-28 and was reported on 2026-02-24. 204 Indiana residents were affected. 39,866 individuals affected in total.
Affected (this filing): 39,866
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. Filing summaries shown in the timeline are AI-generated extracts — verify each against its linked source.