Phillip Capital Inc reported a data breach to the Montana Attorney General. The breach was reported on 2019-02-21. The breach occurred on 2/28/2018. 26 Montana residents were affected.
Affected (this filing): 26
Clustered 2 filings across 2 jurisdictions · filing window Feb 21, 2019 → Feb 28, 2019. View entity profile → Other incidents for this victim →
incident inc_0910b8771f024420 · 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
Feb 28, 2018
When the intrusion reportedly occurred, per the linked filings
Feb 28, 2018
Reported by CALIFORNIA AG filing
Phillip Capital Inc reported a data breach to the Montana Attorney General. The breach was reported on 2019-02-21. The breach occurred on 2/28/2018. 26 Montana residents were affected.
Affected (this filing): 26
Phillip Capital Inc. disclosed a cyber-hacking incident on February 28, 2018, initiated by a phishing email from a third-party vendor. Attackers accessed employee email accounts to identify corporate clients for wire fraud. Compromised data included names, addresses, SSNs, and banking information. The company contained the breach, cooperated with law enforcement, and offered 12 months of identity monitoring to affected customers.
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.