One linked filing — more sources may join as they report · filed Feb 19, 2026. View entity profile → Other incidents for this victim →
incident inc_b36b130e492648d7 · merge_method deterministic
Not recorded for this incident
Discovery variance · Leak precedence · Materiality delta · SEC filing delay · Filing span — no leak-site claim in this cluster; needs two dated filings.
FEDERAL
all SEC 10-K Item 1C
Earliest sighting first · deep chronology in Litigation Timeline
Jul 1, 2020
When the intrusion reportedly occurred, per the linked filings
The Company disclosed a July 2020 ransomware attack on its IT systems in its 10-K Item 1C. The incident resulted in no material financial impact. The Company maintains a comprehensive cybersecurity program including NIST framework alignment, third-party penetration testing, employee training, and incident response retainers. No specific malware family or threat actor was named.
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.