One linked filing — more sources may join as they report · filed Nov 30, 2023. View entity profile → Other incidents for this victim →
Attribution, victim identity, and counts shown here derive from a threat actor's public extortion-blog claims, aggregated by ransomware.live. They have not been validated by the victim or any regulator. Treat them as the threat actor's assertion until a regulatory filing or victim disclosure corroborates them.
incident inc_de2b8efbf31448d3 · merge_method deterministic
Not recorded for this incident
Discovery variance · Leak precedence · Materiality delta · SEC filing delay · Filing span — no SEC 8-K in this cluster; needs two dated filings.
all Leak Site
Earliest sighting first · deep chronology in Litigation Timeline
www.wakeassoc.com We have over 400GB of data from Wakefield and AssociatesThey refuse to come to discuss a deal with us. If you do not contact us soon all this information will be shared to their clients/partners and the world to see.proof 1.jpg 331.01 KBproof 2.jpg 59.34 KBproof 3.jpg 119.89 KBproof 4.jpg 59.26 KBproof 5.jpg 75.65 KBproof 6.jpg 78.77 KB
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.