GLOBALClaimed by FogFirst sighting
Posted to leak site Jan 14, 2025bd_5d22e4c60755f14e
15 GB
Clustered 3 filings across 3 jurisdictions · filing window Jan 14, 2025 → Jan 31, 2025. View entity profile → Other incidents for this victim →
incident inc_2a59897afa744830 · merge_method human · confidence 100%
Discovered → first regulatory filing
Range of discovered_at dates across filings
Gap between first leak claim and first regulatory filing
Time between earliest and latest filing
Not recorded for this incident
Materiality delta · SEC filing delay — no SEC 8-K in this cluster.
MD NH
Leak Site · State AG
Earliest sighting first · deep chronology in Litigation Timeline
Oct 30, 2024
When the intrusion reportedly occurred, per the linked filings
Oct 30, 2024
Reported by MARYLAND AG, NEW HAMPSHIRE AG filings
15 GB
SciTech Services, Inc. notified the Maryland Attorney General of a security incident detected on October 30, 2024, involving unauthorized access and encryption of systems. The incident affected 182 Maryland residents, exposing names, addresses, SSNs, and potentially DOB, driver's license, passport, financial account, and physical examination data. SciTech engaged a cybersecurity firm, contained the breach, and offered 12 months of credit monitoring.
Affected (this filing): 182
SciTech Services, Inc. notified affected individuals of a security incident discovered on October 30, 2024, involving unauthorized access, encryption, and exfiltration of systems containing employment verification, tax, and financial account information. The company engaged a cybersecurity firm, notified law enforcement, and provided credit monitoring services.
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.