LiveBreach Intelligence: data breaches, leaks & ransomware, tracked as they surfaceOngoing protection: GalaxyWarden →
Recent BreachesData breach tracker

Recent Breaches › Hemmakväll Data Breach (2015)

HIGH severityConfirmedHow we verify

Hemmakväll Data Breach (2015): What Was Exposed & What To Do

RBRecent Breaches Breach Intelligence·July 8, 2015

SourceBreach data provided in part by Have I Been Pwned, used under CC BY 4.0.

Hemmakväll Data Breach (2015)

Reported July 8, 2015. Approximately 47K people affected.

HIGH
Severity
47K
People affected
5
Data types exposed
July 8, 2015
Disclosed
ShareXLinkedInFacebookRedditWhatsAppTelegram

The Hemmakväll Data Breach (2015) (reported July 8, 2015) exposed Email addresses, Names, Passwords and Phone numbers belonging to roughly 47K people. If you have an account with them, your information may now be circulating on the open web and with data brokers. Here’s exactly what happened, how to check if you were affected, and what to do next.

Severity & verification
HIGH severityConfirmed
Account credentials exposed.
Corroborated by an official disclosure or a verified breach feed.
Was your email in the Hemmakväll Data Breach (2015) breach?
47K accounts were exposed here. See if yours is one — and every other breach it’s in. 15-sec check, no card.

By running your scan you agree to the Terms and Conditions and the Privacy Policy, and to GalaxyWarden emailing you the results of this scan.

In July 2015, records from the Swedish video store chain Hemmakväll were accessed without authorization and later appeared in a public dump. The incident involved information on roughly 47,000 individuals, including email addresses, names, phone numbers, physical addresses, and passwords. For the people whose details were exposed, the event created lasting questions about how their contact information and login credentials might be used by others.

The breach was reported on 8 July 2015. Public information states that the data was dumped online after the intrusion, but further technical details such as the exact entry method or duration of access have not been disclosed.

Breaking down the breach

The records originated from Hemmakväll’s customer database. They contained names, email addresses, physical addresses, phone numbers, and passwords. The passwords had been stored using the MD5 hashing algorithm, which was already considered weak at the time. Nearly 50,000 records were placed in a publicly accessible location, according to reports from the period.

How a breach like this happens

Incidents involving retail or service databases often begin with an attacker obtaining access to a company’s systems through unpatched software, weak remote-access controls, or compromised credentials. Once inside, the attacker can locate and copy customer tables. In some cases the data is then posted publicly, either to demonstrate the intrusion or to distribute the information further. The use of outdated password hashing such as MD5 makes any recovered credentials easier to process offline.

Who is Hemmakväll?

Hemmakväll operated as a video rental chain in Sweden. Companies in this sector maintain records of customers who rent or purchase media, typically storing contact details to manage accounts, process payments, and communicate about orders or returns. A breach at such an organization therefore touches ordinary transactional information that many households used for routine entertainment services.

What data was at risk

The disclosed records included email addresses, names, phone numbers, physical addresses, and passwords. The exact contents of every record remain unconfirmed beyond these categories. Organizations of this type commonly hold additional fields such as payment references or rental history, yet no further data types have been verified in public reports of this incident.

Why it matters

Contact details combined with passwords can be tested against other online accounts, since many people reuse credentials. Physical addresses and phone numbers may be used for unsolicited contact or to support more targeted attempts at fraud. For the organization, the event highlighted the long-term consequences of storing customer information without stronger protective measures such as modern password hashing.

If your data was in this breach

Change any password still in use that matches the leaked credentials, and avoid reusing it elsewhere. Enable multi-factor authentication on accounts that support it. Review statements from banks or services for unexpected activity. Readers can run a free exposure scan of their email address against known breach data to check for additional appearances of their information.

AICompiled with AI assistance from public sources and published under our editorial standards.

Editorial & sourcing policy
Recent Breaches is a breach-monitoring service and news aggregator. We do not exfiltrate, host, purchase, or redistribute stolen data, and we do not hold the data claimed in leak-site listings. Incidents are compiled from publicly accessible sources and threat-intelligence platforms and are reported as claims attributed to their source. We promptly correct or remove material shown to be inaccurate — write to support@galaxywarden.com or press@recentbreaches.com.
Check if you’re exposed →

How this breach connects

Company

Method

CompanyHemmakväll security record
74/100
DoxxScan™ · Moderate doxx risk
B- 78Above-average record

1 reported incident on record.

See Hemmakväll’s full breach history →

More recent breaches

Trillian Data Breach (2015)December 27, 2015QuinStreet Data Breach (2015)December 14, 2015Aternos Data Breach (2015)December 6, 2015DaniWeb Data Breach (2015)December 1, 2015

Latest breaches

Read GalaxyWarden’s full analysis of the Hemmakväll Data Breach (2015) →

Verified breach. Breach data provided in part by Have I Been Pwned, used under CC BY 4.0.

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.

ShareXLinkedInFacebookRedditWhatsAppTelegram