One linked filing — more sources may join as they report · filed Nov 13, 2025. View entity profile → Other incidents for this victim →
incident inc_d9075a116bbd4538 · 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; no SEC 8-K in this cluster; needs two dated filings.
Credentials · Identity (basic)
MD
all State AG
Earliest sighting first · deep chronology in Litigation Timeline
Jan 4, 2025 → Jan 6, 2025
When the intrusion reportedly occurred, per the linked filings
Jan 6, 2025
Reported by MARYLAND AG filing
TIAA reported a cybersecurity incident involving one Maryland resident. An unauthorized individual accessed the resident's TIAA account between January 4 and January 6, 2025, using valid credentials obtained from an unknown external source. TIAA reset the credentials, placed additional authentication monitoring, and offered 24 months of complimentary credit monitoring.
Affected (this filing): 1
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.