DEV Community

Ahsan Luqman
Ahsan Luqman

Posted on Originally published at aliasfleet.com on

CDJapan data breach: 791,111 customers affected

Neowing Corporation disclosed on 18 November 2026 that a breach of its CDJapan shopping site exposed 791,111 customer membership records and 360,538 historical credit card records. The same report states that skimming code on the credit card entry page is highly likely to have captured 490 card submissions between 6 and 13 November. CDJapan is the international store of Neowing, a Tokyo company, selling anime, J-pop and games to customers outside Japan. The breach is the subject of a second report on the incident. It corrects the first notice, dated 13 November, which put the affected count at 285 cards. No card misuse has been confirmed.

Sequence of the intrusion

Access began on 5 November 2026 at about 14:55 JST. An attacker used a vulnerability in a product image page on the shopping site to gain unauthorised external access. Neowing Corporation is based in Nihonbashi, Tokyo. It runs the site under president Fumio Katagiri, and the company has not named the vulnerability. It has not named the attacker.

The bulk extraction took place the next day. Between 13:04 and 14:15 JST on 6 November, historical credit card information and customer membership information left the database in a single extraction. The window lasted 71 minutes. The company states that the extraction happened only once. No further exfiltration has been confirmed.

Later on 6 November, at 21:06 JST, the credit card information entry page was tampered with. Malicious scripts designed to steal card details were placed on the page. The scripts stayed there until 19:52 JST on 13 November. That is a span of seven days. Orders placed from a PC were exposed to the tampered page. Orders from smartphones or other devices were not affected.

Records in the bulk extraction

The bulk extraction took two sets of records. The first set holds 360,538 historical credit card records. These cover cards registered or used between 2005 and 2018. Each record holds a card number, an expiry date and a cardholder name. The company states that all of these cards have expired, and that the stored records held no security codes at any point.

The second set holds 791,111 customer membership records. These belong to customers with a history of card registration. Each record holds a name, an email address, a telephone number and a partial address. The address is limited to country, city or municipality, and postal code. No address detail more specific than the city or municipality was included in any of the 791,111 membership records extracted on 6 November.

Neowing Corporation's second report on the CDJapan breach: 360,538 historical card records and 791,111 member records leaked, with no secondary damage confirmed

The skimming took a different set of data. The tampered page was displayed 1,152 times. In 490 of those displays, the customer went on to submit card information. The company considers those 490 cases highly likely to have leaked. The submissions included card numbers, expiry dates, cardholder names and security codes.

The two thefts call for different responses. The historical card records are old and expired. The membership records attached to them hold current contact details for 791,111 people. The skimming records are few in number but current. They hold full card details, including security codes.

Differences from the first notice

The first report went up on 13 November 2026. It put the affected window at 9 to 11 November. It counted 285 cards entered or changed in that time. The second report moves the start of the skimming back three days, to 6 November, and adds the bulk database extraction from the same day. The first report did not mention the extraction at all. The end of the skimming window also moved. The code stayed on the payment page until 19:52 on 13 November.

The second report follows an investigation by an independent cybersecurity investigation firm. The company has not named the firm. Privacy Affairs, in its 19 November 2026 report on the second notice, notes a further difference. The first notice said the affected access route had been blocked on 11 November. The skimming code stayed live until 19:52 on 13 November. That reading comes from Privacy Affairs, not from the company, and the first notice itself was not re-read live for this article. What the second report states directly is that all unauthorised external access routes have now been completely blocked. All detected code has been removed.

The correction matters for customers who entered card details on a computer outside the first notice's window: those who entered them on 6 to 8 November, those who entered them on the morning of 9 November before noon, and those who submitted them after 17:00 on 11 November through 19:52 on 13 November. Under the first report, those customers had no reason to think they were affected. Under the second report, they are inside the skimming window. They should check the card used, even though the first notice gave them no cause to think the card was at risk. Anime News Network also covered the second report. Privacy Affairs described it as the only other outlet it found covering the story at publication time.

Per-service addresses and leak tracing

AliasFleet provides one email alias per service. A customer who signed up to CDJapan with a dedicated alias would see any phishing message arrive on that alias. The alias names CDJapan as the source before the message is even opened. The alias can be paused in one click. Pausing stops the phishing at that address while the real inbox stays untouched.

The leak-tracing guide explains how the arriving address identifies the source. AliasFleet does not remove an address from a breach dump. No service can do that. What per-service aliases change is what the next breach gets. They also change how clearly the leak can be traced. The 791,111 membership records in this breach hold names, email addresses and phone numbers. A phishing message built from those records can name the customer and the store, which gives the message a convincing opening line. A dedicated alias gives that message away at a glance.

Precautions stated in the notice

The notice lists precautions for affected customers. Customers who placed an order during the skimming period should review credit card statements for unfamiliar charges. Any suspicious transaction should be reported to the card issuer listed on the back of the card at once. Customers should beware of phishing emails and text messages impersonating the company or card companies. The leaked email addresses, names and other personal information may be misused for fraudulent messages that impersonate the company or a card issuer. The company states that it will never ask customers to provide a password or card information by email or SMS. Links in unfamiliar emails or text messages should not be clicked.

Customers who use the same password for other online services should change those passwords as a precaution. The notice states that no password leakage has been confirmed in this incident, so the password advice is precautionary rather than a response to a confirmed leak. The phishing warning is the more direct risk. The breach response guide covers the password and phishing steps in order.

One point in the company's reassurance needs care. The historical card records are described as expired. That is true of the cards as they stood between 2005 and 2018. Privacy Affairs notes, citing Citi, that a renewed card often keeps the same number. Only the expiry date and security code change. A customer who still holds the same card account should ask the bank whether a new number is warranted. The word expired should not be treated as the end of the matter.

Have I Been Pwned lists no CDJapan breach as of this writing. The check will not yet show this incident.

Your address is probably in this file. Check whether it is, do the password work above, and then fix the part you control: the address you hand out next time. One AliasFleet alias per service means the next leak can only point back to the service that leaked it. Founders Club is $7 a month, locked forever, instead of $12. Early members only.

Regulatory reports and company measures

Neowing submitted its initial report to Japan's Personal Information Protection Commission on 13 November 2026. It has since submitted an additional report reflecting the latest investigation findings. The company is also submitting reports to relevant overseas data protection authorities, including those in the EU and the UK. It continues to report and consult with the National Police Agency's cybercrime reporting desk while the investigation runs and the notification of customers continues. The company has not given a breakdown of affected customers by country. The number of EU and UK customers among the 791,111 is not known.

In cooperation with its payment processing company, Neowing has requested enhanced monitoring for unauthorised use of the exposed card numbers. Individual customer notification is underway by email or other appropriate means, and the company states that it will continue to fulfil orders as usual. Customer inquiries go to CDJapan Customer Support at info@cdjapan.co.jp.

As a measure to prevent recurrence, the company states that it has fixed the identified vulnerabilities. It has also strengthened its security monitoring systems. Once the investigation is complete, it will permanently and irreversibly delete all historical credit card information from 2005 to 2018 remaining in its database. The notice does not explain why card data from as far back as 2005 was still held. The company has not confirmed Privacy Affairs' suggestion that the 2018 cut-off fits the timing of Japan's revised Installment Sales Act, which took effect in June 2018.

Unanswered questions in the investigation

Several facts remain unstated. The company has not named the vulnerability in the product image page. It has not said how the skimming code was planted. It has not attributed the attack to any actor. It has not said whether card payments are back on, or how many of the 791,111 customers have been notified so far.

No confirmed misuse has been reported. The absence of confirmed misuse two weeks after the intrusion is a statement about what the investigation has found so far. It is not a guarantee.

The second report corrects the first notice on both the count and the window. The 285 figure and the 9 to 11 November window described a small, recent problem. The full picture is a bulk extraction of nearly 800,000 customer records and a week of live skimming. Customers who were told nothing on 13 November may now find they were affected after all, because the skimming window in the second report starts three days earlier.

Top comments (0)