One linked filing — more sources may join as they report · filed Feb 25, 2017. View entity profile → Other incidents for this victim →
incident inc_f0edfbb148ad4ddc · 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.
WA
all State AG
Earliest sighting first · deep chronology in Litigation Timeline
Feb 6, 2017
Reported by WASHINGTON AG filing
Blue Mercury, Inc., a business sector entity reported a malware incident to the Washington Attorney General. The organization became aware of the incident on 2017-02-06 and filed notice on 2017-02-25. 778 Washington residents were affected. 19 days elapsed between awareness and notification. 346 days to identify the breach. 0 days to contain the breach.
Affected (this filing): 778
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.