Stallcup & Associates, CPAs reported a data breach to the Montana Attorney General. The breach was reported on 2016-09-21. The breach occurred on 7/11/2016. 1 Montana residents were affected.
Affected (this filing): 1
Clustered 2 filings across 2 jurisdictions · filed Sep 21, 2016. View entity profile → Other incidents for this victim →
incident inc_697387df94cf474e · 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
Jul 11, 2016
When the intrusion reportedly occurred, per the linked filings
Jul 11, 2016
Reported by CALIFORNIA AG filing
Stallcup & Associates, CPAs reported a data breach to the Montana Attorney General. The breach was reported on 2016-09-21. The breach occurred on 7/11/2016. 1 Montana residents were affected.
Affected (this filing): 1
Stallcup & Associates, CPAs experienced a ransomware incident on July 11, 2016, where network files were encrypted. The firm detected the virus within an hour and contained it. No evidence of data exfiltration was found, but client tax information (including SSNs, bank account details, and W-2s) was on the affected drives. The firm engaged forensic investigators, notified the FBI and credit agencies, and offered 12 months of identity protection to affected individuals.
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.