One linked filing — more sources may join as they report · filed Apr 23, 2026. 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_0860dd211d2a4d23 · 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
$krb5pa$23$APTIM.COM$APTIM.COM$$9936cd67a6d3d8560aaa25bb4a7a03b0bb8dfbbdbac8fed06e9262c41dce5ee567d0f7b52928d3626e43c0a7cfac4fb1a9b90887 $krb5pa$23$aptim.com$aptim.com$f7a8e75a2c6d3610fe9f4b34bec2a...
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.