One linked filing — more sources may join as they report · filed Mar 10, 2026. View entity profile → Other incidents for this victim →
incident inc_185250d6f01a4dae · merge_method deterministic
Discovered → first regulatory filing
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, 2024 → Sep 30, 2024
When the intrusion reportedly occurred, per the linked filings
Jul 1, 2024
Reported by SEC 10-K Item 1C filing
The Company disclosed two cybersecurity incidents in its 10-K Item 1C: a July 2024 unauthorized access causing operational interruptions and a negligible September 2024 incident. Containment measures were implemented for both. The Company determined neither was material to financial results. No specific data types or attack vectors were detailed.
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.