Droege Computing Service reported a data breach to the Montana Attorney General. The breach was reported on 2017-10-11. The breach occurred on 9/26/2017. 25 Montana residents were affected.
Affected (this filing): 25
Clustered 2 filings across 2 jurisdictions · filed Oct 11, 2017. View entity profile → Other incidents for this victim →
incident inc_5c46cbbfff2447f1 · 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
Sep 26, 2017
When the intrusion reportedly occurred, per the linked filings
Sep 28, 2017
Reported by CALIFORNIA AG filing
Droege Computing Service reported a data breach to the Montana Attorney General. The breach was reported on 2017-10-11. The breach occurred on 9/26/2017. 25 Montana residents were affected.
Affected (this filing): 25
Droege Computing Services, Inc. disclosed that its StampAuctionNetwork (SAN) server was hacked on September 26, 2017. The breach occurred through the company's main offices rather than directly targeting the SAN server. Affected data includes customer names and payment card information. The company contained the incident, engaged experts for a security review, and removed credit card data from the affected system.
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.