On August 14, threat actors gained access to two of Berlin’s Senate administration networks. Before they were detected and disconnected, they had already exfiltrated an estimated 5.79 terabytes of data — roughly 1.44 million files — from government systems that hold some of the most sensitive documents any administration keeps.
The attackers, working under the name Rhysida, posted a ransom demand of 30 bitcoin (approximately $2.4 million) on August 28. Berlin’s Governing Mayor refused to pay. Rhysida responded by publishing the data.
Among the files: passport scans, ID documents, email addresses, phone numbers, banking account numbers (IBANs), plaintext login credentials for internal government systems, Bundesrat committee protocols, active court case files, and classified-material handling records.
What Was Actually Exposed
The published data included personal information tied to 12,076 individuals. That’s not a faceless data set of usernames and hashed passwords — it’s names, government-issued ID scans, contact information, and in some cases financial details, associated with real people who interacted with Berlin’s government services.
Sixteen thousand email addresses and nearly twelve thousand phone numbers were in the dump. One hundred and forty-eight IBANs — bank account numbers — were exposed alongside names.
The breach also reached into the administrative machinery of government itself. Bundesrat committee protocols, classified documents, and active disciplinary case files were among the leaked material, including more than 400 files tied to a specific ongoing lawsuit before the Berlin Administrative Court.
For the 12,076 individuals whose personal information was exposed, this isn’t an abstract security statistic. Government ID scans tied to names and contact information represent a meaningful identity theft risk. IBAN exposure alongside personal identifiers enables financial fraud. And the nature of government records means that some of what was exposed — health records, legal documents, employment records — reflects circumstances people disclosed in contexts of necessity rather than choice.
The Seven-Day Window
The breach illustrates a consistent pattern in major ransomware incidents: the gap between initial access and detection.
Rhysida had access to Berlin’s networks for seven days before the affected administrations were disconnected from the state network. During that time, 5.79 terabytes of data moved out. Modern ransomware groups prioritize data exfiltration before encryption precisely because stolen data can be used for extortion independently — you don’t need to lock systems if you can threaten to release what you’ve already taken.
Seven days is a long time to move data. It’s also not unusual. The 2026 Canvas breach, which extracted 3.65 TB from the learning management system used by thousands of schools, also involved a dwell period where attackers operated undetected. The Foxconn breach, where 8 TB of supply chain data was taken, followed a similar pattern.
Detection speed is improving across the industry, but the gap between “attackers are in” and “we know attackers are in” remains the central vulnerability in most large-scale breaches. The data is usually gone before the incident response begins.
Why Government Systems Are High-Value Targets
Personal data held by government services is qualitatively different from personal data held by commercial platforms — and that difference makes it more valuable to attackers.
When you store photos in Google Photos or files in Dropbox, you’ve chosen to share that data with a commercial service. The relationship is voluntary, and in principle you can leave and take your data with you. Government data is different. You can’t opt out of having the tax authority hold your financial records, the passport office hold your travel documents, or the health ministry hold your vaccination records. The data accumulates because services are mandatory, not because you chose a product.
This makes government data valuable in a specific way. It’s more likely to be accurate, more likely to be comprehensive, and more likely to represent the full picture of a person’s legal and social status. A stolen government ID scan is more useful for identity fraud than a stolen social media profile precisely because it has the weight of official verification behind it.
Ransomware groups have increasingly targeted public sector organizations — hospitals, schools, and government agencies — because these entities typically have critical data, aging infrastructure, stretched IT security budgets, and legal or operational constraints on shutting down systems that make paying ransoms more attractive. Berlin refused, which is the principled position and the one that most security experts recommend. But the refusal doesn’t undo the data exposure; it only determines whether additional money changes hands.
The Files You Trust to Public Services
It’s worth thinking concretely about what categories of personal data flow through government administrative systems.
Tax authorities hold income records, employer information, bank account details, and in many countries property records. Passport offices hold scanned copies of identifying documents, facial photographs, and travel history. Health systems hold diagnosis records, prescription histories, vaccination records, and mental health information. Courts hold legal records that may include financial disputes, family law proceedings, criminal histories, and civil cases. Social services hold housing records, disability documentation, and in some cases information about family composition and custody arrangements.
Most people have some of their data in most of these systems. The data doesn’t expire when circumstances change. A medical record from a decade ago remains in the system. A tax filing from when you had a different job is still there. A legal record from a dispute you resolved years ago sits in a court database somewhere.
When a government system is breached, the exposure reaches across this accumulated history. The Berlin breach included “an active disciplinary case with more than 400 files tied to a lawsuit before the Berlin Administrative Court.” That’s not metadata — it’s the substantive content of a legal proceeding that was supposed to be confidential.
What You Can Control
You can’t opt your government records out of government systems. The data that Berlin’s administration held about those 12,076 individuals was held because of mandatory administrative processes, not because those people made an active choice to share it.
What you can control is where your personal copies live.
Many people store their own copies of government-adjacent documents — scanned passports, tax documents, medical records, legal correspondence — in commercial cloud services without thinking carefully about the security and privacy implications. These copies may be more accessible to attackers than the original government systems, which at least have institutional security programs, however imperfect.
The breach is also a reminder about the documents you create and store for your own reference. When you photograph your passport for travel backup, when you scan a medical letter to send to a specialist, when you save a copy of a legal document for your records — where those files live matters.
Choosing Where Personal Documents Live
For the personal copies of sensitive documents — ID scans, medical records, financial documents, legal correspondence — the storage decision deserves more deliberate thought than most people give it.
The common default is some combination of photos saved to camera roll (backed up automatically to Google or Apple), files emailed to yourself, and documents saved in general-purpose cloud storage. Each of these involves a commercial platform whose business model, security practices, and data handling terms may not be well-suited to documents as sensitive as a passport scan or a health record.
The Berlin breach is a reminder of what happens when sensitive documents are accessible from systems with insufficient access controls. The parallel for personal storage is choosing services that limit access to your files, use strong encryption, and are explicit about what happens to your data.
daftei stores photos, documents, and files privately — with TLS 1.3 in transit and AES-256 encryption at rest. There are no ads, no data sales, and no AI training on your content. On iOS, Android, and the web at /app, it’s designed specifically for personal files that deserve more careful treatment than a general-purpose cloud storage account. The free tier offers 5GB; unlimited storage is available on Pro for $5.99/month, $44.99/year, or a one-time $89.99 lifetime payment (₹249/month or ₹1,799/year in India). If you delete your account, your files are permanently erased after a 30-day grace window — not archived, not retained for analytics.
The Ransom Refusal and What It Changes
Berlin’s decision not to pay is the right one by almost any analysis. Paying ransoms funds future attacks, and payment doesn’t guarantee the attackers delete what they’ve taken. In most ransomware cases involving data exfiltration, the stolen data is eventually published or sold regardless of payment.
What the refusal doesn’t do is undo the breach. The passport scans, the IBANs, the court records, the personal files — those are now published and effectively permanent. The 12,076 individuals whose information was in that dump live with the consequences whether or not Berlin paid.
The breach will likely result in improved security for Berlin’s government systems. Incident response, access control improvements, better detection — these follow from public breaches that generate political accountability. The seven-day window that allowed 5.79 TB of exfiltration will be harder to sustain in future incidents.
That doesn’t help the people whose data is already out.
The Lesson for Personal Document Management
The practical takeaway from incidents like Berlin’s breach isn’t primarily about what government should do better, though that conversation is necessary. It’s about the documents you hold yourself and where you store them.
The passport scan you emailed to yourself when you renewed your travel document. The medical letter you photographed to forward to a specialist. The financial statement you saved to your desktop. The legal correspondence you stored in a shared cloud folder.
Each of these is a sensitive document that exists on systems you’ve chosen, subject to the security and privacy practices of the services you’re using. The Berlin breach involved government systems you didn’t choose. Your personal document storage involves services you did choose — and that means you have meaningful control over those decisions in a way the 12,076 affected Berlin residents did not.
Treating sensitive personal documents with the care they deserve means choosing storage solutions that are transparent about encryption, access controls, and what happens to your data if the company is acquired, breached, or shut down.
Government systems will continue to be targeted because they hold high-value data at scale. What you can do is ensure that your own copies of sensitive documents are held somewhere with clear, privacy-respecting terms — rather than scattered across email inboxes and general-purpose cloud storage accounts that weren’t designed with that responsibility in mind.