Malca-Amit Singapore Pte Ltd
bd_6ae992d5f9ea9e38 · schema v1 · pii pii-v1
Full breach record for Malca-Amit Singapore 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 Malca-Amit Singapore Pte. Ltd. (the “ Organisation ”) notified the Personal Data Protection Commission (the “ Commission ”) on 10 August 2024 of a personal data breach stemming from a cyber incident involving the compromise of a limited number of servers in its network (the “ Incident ”). I nvestigations revealed that the threat actor (“ TA ”) had most likely gained access to the Organisation’s system using a domain user account and thereafter performing network scanning and lateral movement from the SonicWall VPN. The malicious activities targeted the hosts on the VMware virtualization platform. The TA encrypted some of the Organisation’s files which contained the personal data of 5,834 individuals who were the Organisation’s employees and customers. The types of personal data affected included various combinations of name, address, email address, NRIC number, passport information, photograph, date of birth, bank account information and salary information (which only impacted its employees). Upon discovery of the Incident, the Organisation took prompt remedial actions including physically disconnected the site network and backbone connectivity, eradicated all known TA activity remnants in the network and ceased data backups and checked the integrity of all systems. 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 9 December 2024. As part of the Undertaking, the Organisation will be implementing the following: (a) Strengthened Password Policy; (b) 2FA Enforced on Security Appliances; (c) 2FA Enforced for Remote Access; (d) Continuous Backup of Virtualization Environments; (e) Implementation of SentinelOne XDR for Enhanced Threat D
P pin to compareR raw source
Incident timeline — partial
? — ?
Breach window unknown
Jan 23, 2025
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.