This record tracks a ransomware attack claimed by the
interlock group against
North Stonington Elementary School. It collects the publicly disclosed attack details — sector, location and
timeline — as published on the operator's leak site and indexed by Breach House.
Window Zero
EXPOSURE GAP
Window Zero is the time the breach stayed in the open before
anyone said so — the gap between when the attack was first discovered
on the operator's leak site (t1) and when it was publicly disclosed (t2).
The wider this window, the longer victims, staff and customers were exposed with no warning.
322days open
t1 · Published
t2 · Pending
Business Category
Education
Published
October 13, 2025
Disclosed / Notified
Not disclosed yet
Attack Summary
North Stonington Public Schools have two public schools and 736 students, strives to create a safe environment for themselves, their school, and their students. However, their "Safety First" slogan has recently changed! Despite having extensive resources and support, North Stonington Public Schools has a very poor IT security team that is doing a poor job! With our help, over 3 TB of confidential data was exposed, meaning all student data, including the entire history and documentation, is now in our hands!
Leak Screenshots
SAMPLE
Proof-of-breach screenshots the operator posted from the stolen data. Previews are
redacted and locked — the originals are available on HaveIBeenRansom.
Dark Web Exposure
Findings for northstonington.k12.ct.us
— indexed by HaveIBeenRansom.
0
found in Infostealer logs
632+
found in Traditional breaches
39+
found in Ransomware leaks
VerificationsIO_BF.7z.011
Kedr | Forum · breach
••• emails
Chegg_BF.7z
B F R e p o V 3 F i l e s · breach
••• emails
McGraw Hill, Inc. (mheducation.com)
shinyhunters · breach
••• emails
OnlinerSpambot_BF.7z
B F R e p o V 3 F i l e s · breach
••• emails
2844Breaches_BF.7z
B F R e p o V 3 F i l e s · breach
••• emails
LKnet reserve chat · breach
••• emails
+ 17 more leak sources locked
Leak volumes are locked
Sign in to reveal how many records each source exposed and the remaining 20 sources.
Legal Disclaimer:
This ransomware victim record reflects information published on the operator's leak site.
Breach.house only records what the operators themselves publish in the
open. We take screenshots of their public pages and keep the proof
material they post there, so that a listing can be verified and its status
tracked over time. We do not purchase data, we do not solicit or encourage
its publication, we do not access any private system, and we do not alter
anything we record. Nothing is offered for download here, and detailed
content is not published on this page or anywhere else on the public site:
access to it is restricted to vetted customers under contract, for
incident response, due diligence and cyber-resilience work.
Breach.house is not affiliated with, and does not act on behalf of, the
operators who publish this material. If you represent an organisation or
individual named here and want a record reviewed or removed, contact us
and we will act on it.