Sequoia Capital Operations, LLC reported a data breach to the Montana Attorney General. The breach was reported on 2021-02-18. The breach occurred on 1/20/2021. 3 Montana residents were affected.
Affected (this filing): 3
Clustered 2 filings across 2 jurisdictions · filed Feb 18, 2021. View entity profile → Other incidents for this victim →
incident inc_92a6ae6d90734fbf · merge_method deterministic · confidence 100%
Discovered → first regulatory filing
Time between earliest and latest filing
Not recorded for this incident
Discovery variance · Leak precedence · Materiality delta · SEC filing delay — no leak-site claim in this cluster; no SEC 8-K in this cluster; needs two dated filings.
CA MT
all State AG
Earliest sighting first · deep chronology in Litigation Timeline
Jan 20, 2021
When the intrusion reportedly occurred, per the linked filings
Jan 20, 2021
Reported by CALIFORNIA AG filing
Sequoia Capital Operations, LLC reported a data breach to the Montana Attorney General. The breach was reported on 2021-02-18. The breach occurred on 1/20/2021. 3 Montana residents were affected.
Affected (this filing): 3
Sequoia Capital Operations, LLC notified the California AG of a cybersecurity incident where an unauthorized third party gained remote access to one employee's business email mailbox on or about January 20, 2021. The apparent aim was a wire diversion scam. The breach date listed on the form is January 7, 2021. Fewer than 1,000 California residents were affected. Personal information including names and potentially other PII was exposed. The company engaged cybersecurity experts, remediated the configuration issue, enhanced security protections, and offered 24 months of credit monitoring.
Affected (this filing): 1,000
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.