Classic site
JoomlArt logo

Breach registry

JoomlArt Data Breach

joomlart.com

What was exposed, when it happened, and which databases confirm it.

Verified
accounts
22,477
Breached
January 30, 2018
Last Update
August 7, 2020

Were you caught in this breach?

Search your email, phone number or username against every record CheckLeaked indexes.

Your address never leaves this page: it is hashed in your browser and only a short fragment of that hash is sent.

What happened

In January 2018, the Joomla template website JoomlArt inadvertently exposed more than 22k unique customer records in a Jira ticket. The exposed data was from iJoomla and JomSocial, both services that JoomlArt acquired the previous year. The data included usernames, email addresses, purchases and passwords stored as MD5 hashes. When contacted, JoomlArt advised they were aware of the incident and had previously notified impacted parties.

Compromised Info

  • Email addresses
  • Names
  • Passwords
  • Payment histories
  • Usernames

Attestation

Four independent databases catalog this breach and they do not always agree. Each lane below is one source’s own count.

HIBP22,477
DEHASHED22,477
LEAKCHECKnot attested
VIGILANTEnot attested

Sources & Link Methods

  • HIBP

FAQ

What was leaked in the JoomlArt breach?

The JoomlArt breach exposed: Email addresses, Names, Passwords, Payment histories, and Usernames.

When did the JoomlArt breach happen?

The JoomlArt breach was disclosed on January 30, 2018 and affected 22,477 records.

Am I affected by the JoomlArt breach?

Search your email, phone or username at checkleaked.cc to find out whether your data appears in the JoomlArt leak.

Advertising choice

Google Analytics stays active. Allow Google Ads, LinkedIn Ads and Reddit Ads to measure purchases and personalize advertising? Your choice won’t affect search or purchases. You can change it in Settings.

Privacy policy