D’League Pte Ltd and subsidiaries
bd_ad67f99e232a7db4 · schema v1 · pii pii-v1
Regulator's decision — not a breach notification
This record is a regulator's decision, not the organisation's own breach notice. Breach-notification fields (discovery date, notification clock) are structurally absent — what this source establishes is the outcome and the provisions the decision cites.
Background D’League Pte. Ltd. (the “ Organisation ”) notified the Personal Data Protection Commission (the “ Commission ”) on 8 August 2025 of a personal data breach involving its systems (the “ Incident ”). The Organisation established that on or about 15 July 2025, a threat actor (“ TA ”) had accessed its systems and exfiltrated its data, before encrypting its systems. These systems contained personal data of the Organisation and its subsidiaries, namely Richard Mille Asia Pte. Ltd, Henry Jacques Asia Pte. Ltd, The Value of Time (Asia) Pte. Ltd, Surrender Pte. Ltd. 1 , Three Pleasures Pte. Ltd, Inca Holdings Pte. Ltd, Le Mondo Ryori Pte. Ltd and Shinsetsu Pte. Ltd (collectively, the “ Subsidiaries ”). The Organisation determined that the TA had likely obtained access to its systems through credentials associated with a compromised, dormant Virtual Private Network (“ VPN ”) account used by, or belonging to, a staff member or representative of the Organisation’s external IT consultant. The Incident affected the personal data of 17,626 individuals, comprising employees, former employees, non-employees and customers of the Organisation and its Subsidiaries. The types of personal data affected included a combination of names, NRIC numbers, passport copies, nationalities, dates of birth, addresses, emails, contact numbers, genders, transaction history, financial information ( including names, bank account numbers, and names of bank), employees’ hospitalisation documents and medical certificates. Upon discovery of the Incident, the Organisation took prompt remedial actions including removing all VPN user accounts, creating only essential VPN accounts, enforcing multi-factor authentication (“ MFA ”) for all VPN users and restricting VPN connections. The Organisation also notified the affected individuals. The Incident had likely occurred as the Organisation had inadequate s
P pin to compareR raw source
Incident timeline — partial
? — ?
Breach window unknown
Jun 5, 2026
Filed
—
No linked breach filing · watching
Compliance clocks stay unassessable until a breach filing is linked. This record is the regulator's action, not a breach notice. Dashed segments fill in automatically when corroboration arrives.
Evidence ladder
Attacker assertion only. Establishes: claim date, group, alleged victim.
Unlocks: incident narrative, operational impact. Still no compliance clock.
Unlocks: discovery date, data types, affected count, compliance clock.
Unlocks: materiality, stated response, full audit trail. Ceiling removed.
Source ceiling
- outcome + obligations
- fine (SGD) and affected count where a grounds document states them
- discovery date
- notification clock
See the underlying breach notice, if any.