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

Recent Breaches › iPmart Data Breach (2015)

CRITICAL severityConfirmedHow we verify

iPmart Data Breach (2015): What Was Exposed & What To Do

RBRecent Breaches Breach Intelligence·July 1, 2015

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

iPmart Data Breach (2015)

Reported July 1, 2015. Approximately 2.5M people affected.

CRITICAL
Severity
2.5M
People affected
4
Data types exposed
July 1, 2015
Disclosed
ShareXLinkedInFacebookRedditWhatsAppTelegram

The iPmart Data Breach (2015) (reported July 1, 2015) exposed Dates of birth, Email addresses, Passwords and Usernames belonging to roughly 2.5M 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
Account credentials exposed.
Corroborated by an official disclosure or a verified breach feed.
Was your email in the iPmart Data Breach (2015) breach?
2.5M 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.

The iPmart forum, later rebranded as Mobi NUKE, suffered a data breach in 2015 that exposed records belonging to more than 2 million users. The incident was first reported on 1 July 2015, with an additional 368,000 accounts added to public breach repositories in March 2016, bringing the confirmed total above 2.4 million. The exposed information included usernames, email addresses, dates of birth, IP addresses and passwords stored as salted hashes.

Breaking down the breach

The breach occurred on a vBulletin-based discussion forum operated by iPmart. Attackers obtained a copy of the user database containing over 2 million records. Passwords were protected by salted hashes, yet the implementation was weak enough that many could be cracked in a short time. The compromise was made public in July 2015; a further batch of 368,000 accounts surfaced the following year.

How a breach like this happens

Forum platforms running older versions of bulletin-board software are frequent targets because they often contain unpatched vulnerabilities that allow unauthorised database access. Once inside, attackers typically extract the user table. When password hashes are generated with outdated or poorly implemented salting routines, automated tools can test large numbers of common passwords against the stolen data in a short period. The resulting cracked credentials, together with any accompanying personal details, are then circulated on public breach archives.

Who is iPmart?

iPmart operated an online forum focused on mobile devices and related technology topics. Such platforms maintain user accounts to support discussion threads, private messaging and community features. Because members often register with personal email addresses and dates of birth, the site accumulated a substantial collection of identifiable information over time. A breach at a long-running forum therefore affects individuals who may have created accounts years earlier and no longer actively monitor the service.

The information in question

The records confirmed as exposed include usernames, email addresses, dates of birth, IP addresses and passwords stored as salted hashes. The exact contents of every account remain unconfirmed beyond these categories. Organisations that run discussion forums commonly store these data types to manage registrations and display user information; whether additional fields were present has not been disclosed.

The real-world impact

Individuals whose details appeared in the dataset face an elevated risk that their email addresses and any cracked passwords could be used in attempts to access other online accounts. Re-use of the same password across services increases this possibility. For the organisation, the incident highlighted the long-term consequences of retaining user data on legacy forum software without strong password-storage practices. No financial loss figures or statements from iPmart have been made public.

What to do if you're exposed

Change the password on the affected account and on any other service where the same password was used. Enable two-factor authentication wherever available. Review recent account activity for signs of unauthorised access. Readers can run a free exposure scan of their email address against known breach data to determine whether their information appears in this or other documented incidents.

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

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

1 reported incident on record.

See iPmart’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, 2015Nihonomaru Data Breach (2015)December 1, 2015

Latest breaches

Read GalaxyWarden’s full analysis of the iPmart 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