MUJI Operator Ryohin Keikaku Breach Exposes 1.09M Plaintext Cards

Ryohin Keikaku, the operator of MUJI, confirmed a breach exposing 1.09 million credit card numbers that were stored in plaintext on legacy servers in Japan.
Table of Contents
    Add a header to begin generating the table of contents

    Ryohin Keikaku, the Japanese operator of the MUJI retail chain, has confirmed a cyberattack on its corporate systems that exposed about 1.09 million credit card numbers along with customer birth dates. The card numbers belong to holders of the co-branded MUJI Card issued with Credit Saison, and they had been stored in plaintext on legacy servers.

    Why Card Numbers Sat in Plaintext Since 2021

    The exposed data traces back to a July 2021 change to the loyalty program. Credit Saison had sent card numbers to MUJI between October 2000 and July 2021, and those records were never purged when the program changed. They remained on legacy servers in unencrypted form for years after the change.

    The cause of the retention, whether human error or a software glitch, is still under investigation, according to the company’s statement as cited by The Japan Times.

    Twenty-One Years of Transferred Records

    The transfer window spans more than two decades, from October 2000 to July 2021. Records from that entire period were never purged.

    What Attackers Could Match: Names, Cards and Birth Dates

    The exposed dataset initially lacked names, expiry dates and CVV2 codes. However, the attackers also breached separate business systems, which gave them the means to cross-reference card numbers with customer names. Expiry dates and CVV codes were not compromised.

    Limits on Direct Card Fraud

    Because expiry dates and CVV codes were not taken, the data does not allow direct fraudulent charges on its own. The risk that remains is fraud and phishing, where a criminal who holds a card number, a name and a birth date can build a convincing impersonation of a card issuer or retailer.

    Investigation Status and Pending Report

    The company’s investigation is ongoing, and a full post-incident report is pending. The breach was confirmed this month.

    Credit Saison Co-Branded MUJI Card Holders Are the Affected Group

    The people affected are holders of the Credit Saison co-branded MUJI Card. Their card numbers and birth dates were exposed in the attack on Ryohin Keikaku’s corporate systems. Credit Saison had transferred the numbers to MUJI over the entire period from October 2000 to July 2021, and the July 2021 change to the loyalty program was the point at which the old records remained in place rather than being erased. The data stayed on legacy servers until the attackers reached it.

    The company’s account also separates two sets of systems. The card dataset itself did not include names, but the attackers’ separate access to business systems supplied a way to match cards to people, which turns an anonymous list of numbers into identifiable records.

    Open Questions for Ryohin Keikaku’s Post-Incident Report

    Several points remain unanswered while the investigation continues. The company has not said whether the retention was caused by human error or a software glitch, and it has not published a full post-incident report. The exact date of the formal statement is also unconfirmed in the reporting, which relies on The Japan Times. What is established is the scale, 1.09 million card numbers, and the fact that expiry dates and CVV2 codes were not part of the exposure.

    What the MUJI Breach Reveals About Data Retention

    The incident is a retention failure as much as an intrusion. The attackers did not need to defeat encryption on a live payment system; they reached records that the business had no reason to still hold after the 2021 program change. The longer data is kept after its purpose ends, the larger the dataset that a later breach can reach.

    Card Data Handed Between Partners

    The co-branded card arrangement also shows how data moves between partners. Credit Saison sent numbers to MUJI over two decades, and MUJI’s legacy servers, rather than the card issuer’s systems, became the point of exposure. The company’s forthcoming report is expected to clarify why the purge never happened, which will determine whether the lapse was isolated or process-wide.

    Related Posts