sumperk.cz Listed by SafePay Ransomware Group: Ransomware Claim — What’s Alleged & What To Do
sumperk.cz was listed by the SafePay ransomware group on 28 September 2026. The group claims to hold data on an undisclosed number of individuals; anyone connected to the organisation should verify their status and follow standard breach-response steps.
A ransomware group known as SafePay has listed sumperk.cz on its leak site, raising concern for anyone who uses the city’s main public website for local information or online services. As of writing, the city has not publicly confirmed that an incident occurred, and independent verification is not available in the material at hand. What is known is limited to the group’s claim and the date that claim was reported.
For residents, businesses, and others who interact with a municipal portal, the practical question is conditional: if systems or files connected to that portal were accessed without authorisation, personal and administrative data of the kind local government sites often handle could be at risk. Until more is confirmed, people should treat the listing as an allegation and prepare accordingly rather than assume their records are already exposed.
What is being claimed
According to the listing, SafePay has named sumperk.cz on its extortion-oriented leak site. The claim was reported on September 28, 2026. Public detail in the available record does not state how many people might be affected, which systems were involved, whether any ransom demand was made, or what method the group says it used. The types of data allegedly taken are not disclosed in that record.
SafePay’s appearance of a name on a leak site is a pressure tactic common to ransomware crews: they assert they hold material and threaten publication to force payment or attention. That assertion is not the same as a claimed breach. The organisation behind sumperk.cz has not, on the information provided here, publicly confirmed the incident. Timing beyond the reported listing date, scale, and technical path of any intrusion remain undisclosed.
Who is SafePay?
SafePay is known in public reporting as a ransomware and extortion actor. Groups of this type typically encrypt systems, exfiltrate copies of data, and post victim names on dedicated leak sites when they want leverage. They often blend technical intrusion with public shaming and countdown-style threats. Their listings are marketing for the crew as much as evidence; they can exaggerate, recycle older material, or list organisations prematurely.
Well-documented patterns for such actors include double extortion—locking systems while also claiming to hold stolen files—and selective publication of samples to prove access. None of that general pattern proves what happened in this specific case. For sumperk.cz, the only incident-specific point in the given facts is that SafePay has listed the site and that the listing was reported on the date above. Claims about volumes of data, file names, or internal access should be read as the group’s unverified statements unless confirmed elsewhere.
About sumperk.cz
sumperk.cz is described as the official website serving as the city’s principal digital information and service portal for residents, businesses, visitors, and others. Municipal portals of this kind are the public face of local administration: news, forms, contacts, service directories, and sometimes authenticated or semi-authenticated interactions with city offices.
A listing that names a city portal matters because local government sites sit at the junction of civic life and personal data. People use them for routine needs—permits, announcements, business contacts, tourism information—and may have submitted identity, address, or case-related details through related channels over time. Consequence here is not theatrical; it is about trust in everyday public services and the sensitivity of records a city may hold. That does not establish that any particular record set was taken; it explains why an unverified claim against such a portal draws attention.
The information in question
The available facts state that data types named as exposed are not disclosed. The number of people affected is unknown. It would be inaccurate to treat any inventory of stolen fields as established.
If files or databases connected to a municipal information and service portal were copied, organisations in this sector typically hold or process items such as names and contact details, correspondence with residents or firms, service requests, public-register extracts, staff or contractor directory information, and operational documents. Some cities also handle more sensitive case files through linked systems. Whether any of that applies here is unconfirmed. The leak-site description, when groups provide one, is attacker marketing, not an audited catalogue. Readers should keep the conditional frame: only if material was actually taken would those typical categories become relevant to personal risk.
Why it matters
For individuals, the real-world stakes of a municipal-data incident—if one occurred—include phishing and social engineering that reference local services, misuse of contact details, and fraud that exploits knowledge of an address, a case, or a business relationship with the city. Identity-related harm is possible when government-adjacent records are involved, but that remains hypothetical until contents and scope are verified.
For the organisation, a public listing can disrupt confidence in digital services, force costly verification and recovery work, and create legal and notification duties if a breach is later established under applicable law. A leak-site post alone does not prove negligence, poor architecture, or failed detection; it proves only that a crew chose to name the domain. What the listing establishes is the existence of an allegation and a date on which that allegation was reported. What it does not establish is confirmed theft, confirmed file lists, or confirmed impact on any named resident.
If your data was involved
If you use sumperk.cz or have submitted information to the city through related channels, treat the situation as a precaution exercise rather than a claimed personal breach. Watch for unexpected messages that cite city services, invoices, or “urgent” account issues; verify any such contact through official channels you already trust, not through links in the message. Consider updating passwords on accounts that reuse credentials you may have used with public portals, and enable multi-factor authentication where it is offered. Monitor bank and important accounts for unfamiliar activity if you have shared financial or identity details with local administration.
Keep records of any suspicious contact. Follow official notices from the city if and when they publish guidance. You can also run a free exposure scan of your email address to check whether that address has already appeared in known breach datasets elsewhere—useful context, though it will not by itself confirm or deny this specific claim. Until the organisation or a competent authority confirms facts, the responsible stance is calm vigilance, not panic, and not acceptance of an extortion crew’s word as settled truth.
AICompiled with AI assistance from public sources and published under our editorial standards.
How this breach connects
More recent breaches
toyokiki-thailand.com Listed by SafePay Ransomware Groupdeom.be Listed by SafePay Ransomware Groupdd-automation.ch Listed by SafePay Ransomware Groupryomo.co.jp Listed by SafePay Ransomware GroupLatest breaches
Read GalaxyWarden’s full analysis of the sumperk.cz Listed by SafePay Ransomware Group →
Publicly posted by safepay — unverified claim, pending independent verification
Breach listings — particularly those originating from ransomware or leak sites — are third-party claims that may be unverified, incomplete, or inaccurate. A listing does not by itself confirm that a breach occurred or that any specific data was exposed. Severity is an automated assessment, not a definitive rating. Verification status is shown where available.
Attributions to threat groups and methods reflect public reporting and, in some cases, unverified claims made by the groups themselves; they may be incomplete or later revised. Recent Breaches and GalaxyWarden are independent and are not affiliated with, and do not endorse, any company or group named on this page. This information is aggregated from public sources for awareness only and is not legal, security, or investment advice.