Country : United States of America - Exfiltraded data : yes - Encrypted data : yes
Clustered 3 filings across 3 jurisdictions · filing window Jul 29, 2024 → Sep 19, 2024. View entity profile → Other incidents for this victim →
incident inc_003759d233954241 · merge_method deterministic · confidence 100%
Discovered → first regulatory filing
Gap between first leak claim and first regulatory filing
Time between earliest and latest filing
Not recorded for this incident
Discovery variance · Materiality delta · SEC filing delay — no SEC 8-K in this cluster; needs two dated filings.
CA VT
Leak Site · State AG
Earliest sighting first · deep chronology in Litigation Timeline
Jun 23, 2024
When the intrusion reportedly occurred, per the linked filings
Jun 23, 2024
Reported by VERMONT AG filing
Country : United States of America - Exfiltraded data : yes - Encrypted data : yes
The Gill Corporation experienced a cyber-attack in late June 2024, likely on June 23, 2024, where an unauthorized third party encrypted files and accessed/acquired personal information of former employees. Affected data includes names, Social Security Numbers, driver's license numbers, bank account numbers, and W-2 forms. The investigation is ongoing. The company has removed the exploited vulnerability, deployed additional security measures, and offered credit monitoring to affected former employees.
The Gill Corporation notified former employees of a cyber-attack in late June 2024 where an unauthorized third party encrypted files and backup systems. Personal information accessed included names, SSNs, driver's license numbers, and bank account numbers. The incident is under investigation, and credit monitoring services are being offered.
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.