In July 2025, a huge data exposure sent shockwaves through Sweden. An unprotected server leaked personal and corporate data. Cybernews discovered it during their routine scanning. The database stored well over 100 million records, dated between 2019 and 2024.
What Data Was Exposed and How?
The server used Elasticsearch and was left accessible without authentication. The leak included personal identity numbers, full names, birth data, and address histories—both local and foreign. It also contained financial and behavioral data: tax records, debt history, bankruptcy filings, citizenship status, and event logs.
Researchers traced naming conventions like “dwh*” to Risika, a Nordic analytics firm. Yet the actual server likely belonged to a downstream client licensed to use their data. Risika firmly denied owning or operating this specific archive.
Lessons for Organizations and Eye World Readers
This incident shows how dangerous cloud misconfigurations can be. A single lapse created a massive vulnerability. Eye World warns businesses to audit partner-managed infrastructure and enforce access controls.
Organizations must treat third-party data handlers with scrutiny. Supply chain security can’t be an afterthought. Audits must be ongoing—not one-time.
Protecting sensitive data requires runtime monitoring and strong authentication. Encryption and access policies alone are not enough. Intelligence platforms must detect anomalies in real time to prevent exposures.
Summary
- In July 2025, over 100 million Swedish records leaked.
- Data included identity numbers, addresses, tax, and event logs.
- Leak linked to Risika data but likely occurred at downstream partner.
- Highlights risks of misconfigured cloud servers and partner negligence.
- Organizations must audit third parties and adopt real-time security monitoring.
By covering this breach through Eye World’s perspective, our readers gain insights into real-world risks and prevention strategies. Let me know when you’re ready to send the next article!
