Orchid Hotel Pte Ltd
bd_78bb9545699d7ec7 · schema v1 · pii pii-v1
Full breach record for Orchid Hotel Pte Ltd →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 Orchid Hotel Pte Ltd (the “ Organisation ”) notified the Personal Data Protection Commission (the “ Commission ”) on 13 March 2024 of a ransomware attack on its servers (the “ Incident ”). The personal data, which included the name, NRIC, date of birth, email address, and telephone number, scanned copy of passport and credit card information (last 4 digits) of 680,000 individuals was encrypted Investigations revealed that the threat actor (“ TA ”) gained access through the Remote Desktop Protocol and successfully compromised the local and domain administrator accounts. At the time of the Incident, sensitive data, i.e. NRIC, passport and credit card information, was encrypted at rest. The Organisation’s firewall logs did not detect any abnormalities, anomalous outbound traffic or evidence to suggest that data had been exfiltrated. Upon discovering the Incident, the Organisation took prompt remedial actions. This included engaging a third-party vendor to conduct comprehensive security assessment and data handling practices and also implementing stronger password standards and multi-factor authentication (“ MFA ”) for all accounts. Voluntary Undertaking Having considered the circumstances of the case, the Commission accepted a voluntary undertaking (the “ Undertaking ”) from the Organisation to improve its compliance with the Personal Data Protection Act 2012 (the “ PDPA ”). The Undertaking was executed on 21 August 2024. As part of the Undertaking, the Organisation will be implementing the following: (a) Change all IP addresses and passwords for affected servers; (b) Perform a full reformat and rebuild of impacted systems to ensure a clean and secure environment. All network assets would be assessed, and all remote access credentials changed. A VAPT is scheduled; (c) Conduct another round of anti-virus scans across all servers and endpoints to identify and re
P pin to compareR raw source
Incident timeline — partial
? — ?
Breach window unknown
Oct 23, 2024
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.