SciTech Services, Inc.
bd_5d22e4c60755f14e · schema v1 · pii pii-v1
Full breach record for SciTech Services, Inc. →Threat-actor claim — not a regulatory filing
This row is a claim by the ransomware group Fog on its public extortion blog. It has not been validated by the victim or any regulator. Treat attribution and counts as the threat actor's assertion until a regulatory filing or victim disclosure corroborates them.
Source: Ransomware.live
Post text · scraped from the leak site
15 GB
J jump to incidentP pin to compareR raw source
Incident timeline — mostly unverified
? — ?
Breach window unknown
Jan 14, 2025
Claim posted
—
Corroborated · see linked filings
Compliance clocks stay unassessable until a regulatory filing lands. Dashed segments fill in automatically when corroboration arrives.
Claim → filing
—
Compliance clock
Not assessable
Linked disclosures
Why this link?Regulatory filings (3) · sorted by filing gap
- Massachusetts State AGbd_5e6735b93c8b31f42025-01-31 · +16dVerified by operator
- Maryland State AGbd_81f5af5d562e10242025-01-31 · +16dVerified by operator
- New Hampshire State AGbd_e74be2fa052a5c1a2025-01-31 · +16dVerified
Filing propagation · 4 filings · 3 states
View merged incident ↗Pattern: first filing Jan 14, last Jan 31 (NH) — a 16-day rolling notification. Rolling spreads often mean counsel is filing as thresholds trip per state. Why this link?
Evidence ladder
Attacker assertion only. Establishes: claim date, group, alleged victim.
Unlocks: incident narrative, operational impact. Still no compliance clock.
Unlocks: discovery date, data types, affected count, compliance clock.
Unlocks: materiality, stated response, full audit trail. Ceiling removed.
Source ceiling
- actor name
- victim claim
- ransom/leak status
- discovery date
- materiality
- notification
- affected count
- confirmed data types
- compliance clock
The ✕ fields stay blank until a regulatory filing or victim disclosure lands.
fog
According to ransomware.live, Fog, which uses the .flocked extension for encrypted files, was first observed in May in campaigns by Storm-0844, a threat actor known for distributing Akira. By June, Storm-0844 was deploying Fog more than Akira.