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

Recent Breaches › Ster-Kinekor Data Breach (2017)

CRITICAL severityConfirmedHow we verify

Ster-Kinekor Data Breach (2017): What Was Exposed & What To Do

RBRecent Breaches Breach Intelligence·March 9, 2017

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

Ster-Kinekor Data Breach (2017)

Reported March 9, 2017. Approximately 1.6M people affected.

CRITICAL
Severity
1.6M
People affected
8
Data types exposed
March 9, 2017
Disclosed
ShareXLinkedInFacebookRedditWhatsAppTelegram

The Ster-Kinekor Data Breach (2017) (reported March 9, 2017) exposed Dates of birth, Email addresses, Genders and Names belonging to roughly 1.6M 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
CRITICAL severityConfirmed
Plaintext passwords exposed.
Corroborated by an official disclosure or a verified breach feed.
Was your email in the Ster-Kinekor Data Breach (2017) breach?
1.6M 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.

Ster-Kinekor, a South African cinema company, experienced a data breach that exposed information associated with 1.6 million unique email addresses. The incident originated from a security flaw in 2016 involving an enumeration vulnerability in the API of the company's old website. The breach was reported on March 9, 2017. While more than 6 million accounts were affected by the flaw, the unique email count stood at 1.6 million. The exposed data included names, physical addresses, dates of birth, genders, phone numbers, spoken languages, and passwords stored in plain text.

Inside the incident

The flaw allowed data to be retrieved through repeated queries against the API of Ster-Kinekor's older website platform. Public reporting at the time indicated that the vulnerability had been present during 2016 and that the resulting dataset contained extensive customer records. No official statement from the company detailing the precise start or duration of the exposure has been referenced in available records.

Scale estimates rest on the distinction between total accounts touched by the flaw and the smaller set of unique email addresses that appeared in the resulting data. The presence of plain-text passwords alongside other personal fields was noted in summaries of the exposed material.

How a breach like this happens

Enumeration vulnerabilities in APIs occur when an interface permits systematic querying that reveals whether particular records exist and returns associated data without adequate rate limiting or access controls. Attackers can iterate through possible values, such as sequential identifiers or email patterns, to compile large volumes of information over time.

Such issues often arise in legacy systems that were not designed with modern authentication or query restrictions. Once an attacker identifies the pattern, bulk extraction can proceed without triggering conventional intrusion detection if logging and monitoring are limited.

Ster-Kinekor and its sector

Ster-Kinekor operates cinema locations across South Africa and maintains customer accounts for ticket purchases, loyalty programs, and online bookings. Companies in this sector routinely collect contact details, demographic information, and authentication credentials to manage reservations and marketing communications.

A breach at a cinema chain is consequential because the data supports repeated customer interactions over years. Records that combine names, addresses, and passwords can remain useful to malicious actors long after the initial exposure.

What was likely exposed

The reported dataset included dates of birth, email addresses, genders, names, passwords, phone numbers, physical addresses, and spoken languages. Passwords were stored in plain text rather than hashed, which increases the immediate usability of any recovered credentials.

Exact confirmation of every field present in each record remains limited to the summaries published at the time of disclosure. Organisations of this type commonly retain additional transaction or preference data, yet no further categories have been verified in connection with this incident.

Why it matters

Exposure of plain-text passwords alongside identifiable information raises the possibility that affected accounts could be accessed on other services where users reused the same credentials. Physical addresses and contact details can support targeted phishing or identity-verification attempts.

For the organisation, the incident highlighted risks associated with older website infrastructure that continued to handle customer data. Remediation typically requires both closing the enumeration vector and migrating stored passwords to stronger hashing methods.

Were you affected?

Individuals can check whether their email address appears in known breach datasets by using a free exposure scanning service that queries public breach repositories. If an address is listed, the immediate step is to change the password on the affected service and on any other accounts that used the same credential.

Additional precautions include enabling multi-factor authentication where available and monitoring financial or loyalty accounts for unusual activity. Organisations that held the data have not published a public notification portal specific to this event, so direct inquiries to Ster-Kinekor remain the only route for account-specific confirmation.

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

CompanySter-Kinekor security record
73/100
DoxxScan™ · Moderate doxx risk
C- 64Below-average record

1 reported incident on record.

See Ster-Kinekor’s full breach history →

More recent breaches

The Fly on the Wall Data Breach (2017)December 31, 2017HoundDawgs Data Breach (2017)December 30, 2017Lyrics Mania Data Breach (2017)December 21, 20172fast4u Data Breach (2017)December 20, 2017

Latest breaches

Read GalaxyWarden’s full analysis of the Ster-Kinekor Data Breach (2017) →

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