Japanese payments company PayCloud Holdings has disclosed another data breach involving up to 31,000 code records, nearly four weeks after reporting the exposure of 1.42 million prepaid-card records. The November 18 announcement confirms that attackers compromised a second server operated by subsidiary Value Design, extending the scope of an investigation that had previously found no additional unauthorized access.
The Tokyo-listed company, which trades on the Tokyo Stock Exchange Growth Market under code 4015, discovered the additional exposure on November 14. It traced the intrusion to October 19, the same date associated with its earlier Value Card security incident, and invalidated the affected codes on November 16.
PayCloud acknowledged that some of the newly exposed codes might have been used without authorization. It has not established a confirmed financial loss or disclosed how many customers were directly affected.
Second compromised server discovered weeks after initial breach
The newly identified breach affected a dedicated website developed and operated by Value Design for business customers, rather than the Value Card server involved in the company’s October 23 disclosure.
According to PayCloud’s November 18 regulatory filing, an unauthorized third party manipulated functions on the website to retrieve files stored on its server and extract code information.
The company said the activity was difficult to distinguish from ordinary website operations, explaining why investigators failed to identify the separate intrusion during their initial assessment.
It was another server, not simply another count from the first one.
In its October announcement, PayCloud had stated that its investigation had identified no effects from unauthorized access beyond the incident already disclosed. The November 18 filing explicitly acknowledges that the latest discovery contradicts that earlier assessment.
The old assurance, then, did not hold up.
PayCloud says its subsequent investigation found no evidence that the same unauthorized activity occurred on dates other than October 19. It also reports that preventive measures for the newly affected website have been completed.
The disclosure does not identify the attacker, name the affected corporate clients or provide technical details explaining how the unauthorized operations bypassed the website’s security controls.
Combined exposure reaches approximately 1.46 million records
The additional 31,000 records were not included in the 1,424,748 records disclosed on October 23, according to the company.
The original incident involved Value Design’s Value Card service, which supports merchant-issued prepaid electronic money. Attackers exploited a web-server vulnerability and obtained card ID numbers, PINs and balance information.
PayCloud provided the following breakdown of the original exposure:
- 569,224 issued Value Card IDs.
- 855,524 unissued IDs that had not yet been purchased by end users.
- 1,424,748 total ID, PIN and balance records.
Adding the newly disclosed maximum of approximately 31,000 code records brings the combined reported exposure to approximately 1.46 million records. That is an increase of about 2.2% over the original figure.
The two categories should not be treated as identical. The first disclosure concerned Value Card credentials and balances, while the second concerns code information stored on a seperately operated server. PayCloud has not identified the number of distinct individuals represented by the combined records.
Neither disclosure identified personal information within the exposed datasets. Nevertheless, the October incident involved payment credentials that could potentially be used to access stored value, while the latest filing raises concerns about unauthorized use of the additional codes.
Japan’s Financial Services Agency explains in its guidance on prepaid payment instruments that electronically recorded numbers and other identifiers can constitute prepaid payment instruments when issued in exchange for value and used to purchase goods or services. Notification and registration requirements depend on the issuer’s business model.
The rules provide context for the stored-value services supported by Value Design, although the available disclosures do not establish the specific regulatory classification of the newly exposed codes.
PayCloud invalidates codes as misuse remains under investigation
PayCloud disabled the newly identified codes on November 16 and began notifying customers through the affected website.
The company warned that the invalidation could inconvenience some users, but did not disclose how many codes were active, their monetary value or whether replacement codes would be issued.
The codes have been disabled, and that brings its own inconvenience for some customers.
The company’s wording on potential misuse also differs from its October disclosure.
For the original Value Card breach, PayCloud said it had addressed the risk of unauthorized use involving issued IDs and had not identified actual financial damage. In the November update, it acknowledged the possibility that some newly exposed codes had been improperly used, without confirming an amount or number of incidents.
That leaves the financial impact unresolved. Invalidating compromised codes can prevent subsequent use, but the company’s filing does not establish whether any codes were succesfully redeemed before the November 16 intervention.
A comparable issue arose in the Tria card-balance exploit, where the company ultimately reimbursed 636 affected customers following unauthorized withdrawals from card-related infrastructure. The PayCloud incident involves different systems, and no equivalent confirmed customer losses or reimbursement arrangements have been disclosed.
PayCloud said it plans to report the latest incident to Japan’s Personal Information Protection Commission. The planned notification should not be interpreted as a finding that personal information was exposed or that the company violated data-protection requirements.
Security review expands to custom-built payment systems
The second breach has prompted PayCloud to broaden the security review announced after the October incident.
The company initially committed to reassessing vulnerabilities across its services with external security specialists. Its November 18 filing extends that review explicitly to systems individually developed and operated for corporate customers.
That puts the individually developed customer systems under the microscope as well.
The revised scope addresses a limitation revealed by the latest discovery: security assessments focused on the originally compromised Value Card environment did not identify malicious activity on the separate customer website.
PayCloud has not disclosed the total number of custom-built systems under examination, their security architecture or whether any share infrastructure with the compromised servers.
The investigation also follows other disclosures involving Japanese financial-service technology providers. In November, Monex Securities reported potential exposure of 1.13 million email records and 1,592 identity-verification images associated with an external account-opening system.
Monex’s incident involved different systems and potentially sensitive personal information, while PayCloud’s disclosures concern payment credentials and codes. Neither company has publicly established a connection between the attacks.
For PayCloud, the expanded investigation creates an additonal operational consideration alongside the potential cost of customer remediation. The company must now assess individually developed systems that were not explicitly covered by the original investigation’s stated scope.
The company has not quantified expenses related to external forensic specialists, security upgrades, code replacement or potential customer compensation. It said the financial implications of both incidents remain under examination and that it will disclose any material impact on earnings.
The final bill, at this stage, is still an unknown.
The next relevent disclosures will be the results of the wider system review, the outcome of investigations into possible unauthorized code use and any quantified financial impact. Until then, the confirmed exposure stands at approximately 1.46 million records across two separately compromised server environments, with the number of affected customers and actual losses still undetermined.
Johan Shamshad is Editor-in-Chief at Dave Finances, covering financial markets, digital assets, trading platforms, brokers, fintech, payments and regulation. Since 2023, he has also worked as an editor at Gulf News, the UAE English-language newspaper published by Al Nisr Publishing LLC. His work focuses on market-moving developments, company disclosures, regulatory changes and trading infrastructure, with an emphasis on primary-source verification and practical context for traders and investors.

