Home All Victims Keepz

Keepz

killsec

This record tracks a ransomware attack claimed by the killsec group against Keepz. 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.

583days open
t1 · Published t2 · Pending
Jan 25, 2025Not disclosed yet
Business Category
Communication / Marketing
Employees
51-100
Discovered
2025-01-25
Published
January 25, 2025
Disclosed / Notified
Not disclosed yet
Victim ID
wJL1I1v48mCy

Attack Summary

Keepz is a cutting-edge digital payment solution provider based in Tbilisi, Georgia, offering innovative tools for businesses to streamline transactions. The company’s flagship product is its QR-based payment system, which enables businesses to accept payments without physical terminals or user registration.

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.

file_tree.png
finance_2024.xlsx
passport_scan.jpg
contract_signed.pdf
Sign in or explore HaveIBeenRansom to view the full leak gallery.
View leak gallery →

Dark Web Exposure

Findings for keepz.me — indexed by HaveIBeenRansom.
0
found in Infostealer logs
4
found in Traditional breaches
0
found in Ransomware leaks
cutout.pro - @bereza_bd.rar
DataClub · breach
••• emails
Leak volumes are locked
Sign in to reveal how many records each source exposed.
Want the complete picture — passwords, machines, full leak files? It's all searchable on HaveIBeenRansom.
Search this victim →
Visit Website Original Post View Group: killsec
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.