This record tracks a ransomware attack claimed by the
funksec group against
kuzstu-nf.ru. 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.
595days open
t1 · Published
t2 · Pending
Published
January 13, 2025
Disclosed / Notified
Not disclosed yet
Attack Summary
kuzstu-nf.ru was named by the funksec ransomware group as a targeted organization. It operates in the Other sector. The affected entity is based in Russian Federation. The incident was first observed on January 13, 2025. The entry is documented by Breach House from public leak-site sources and is provided for situational awareness only.
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 kuzstu-nf.ru
— indexed by HaveIBeenRansom.
0
found in Infostealer logs
33+
found in Traditional breaches
0+
found in Ransomware leaks
@StormBaseAdapter - ГосУслуги.part01.rar
⚡️𝙎𝙏𝙊𝙍𝙈 Dаtа Ваsе · breach
••• emails
S7RU.7z.001
DBs Backup · breach
••• emails
gosuslugi.ru - @StormAndDataBase.zip
⚡️𝙎𝙏𝙊𝙍𝙈 Dаtа Ваsе · breach
••• emails
Exploit.in.rar
LKnet reserve chat · breach
••• emails
+ 15 more leak sources locked
Leak volumes are locked
Sign in to reveal how many records each source exposed and the remaining 18 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.