Megachem Ltd
bd_e0a07479da63dfdd · schema v1 · pii pii-v1
Full breach record for Megachem 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 Megachem Limited (the “ Organisation ”) notified the Personal Data Protection Commission (the “ Commission ”) on 6 May 2025 that a threat actor (“ TA ”) had executed a ransomware attack that compromised its IT environment, resulting in its file servers being encrypted and data exfiltrated subsequently (the “ Incident ”). The Organisation established that the TA had gained unauthorised access to the Organisation’s servers located in Singapore. The TA exfiltrated the Organisation’s files containing personal data of 34 individuals which comprised its staff and service providers. The types of affected personal data included a combination of names, telephone numbers, email addresses and 2 scanned copies of passports. Upon discovery of the Incident, the Organisation took prompt remedial actions including: (a) Immediate containment and system restoration from clean backups; (b) Deployment of Two-Factor Authentication for remote VPN access; (c) Enhancement of endpoint and server security; (d) Enforcement of password protection guidelines; and (e) Engagement of IT vendors for vulnerability assessment proposals. The ransomware attack had likely occurred as the Organisation had inadequate security measures including the incomplete deployment of Multi-Factor Authentication for remote VPN access, lack of 24/7 threat monitoring for its endpoints and servers, and the absence of vulnerability assessments and scans prior to the Incident. 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 7 November 2025. As part of the Undertaking, the Organisation will be implementing the following: (a) Complete roll out Two-Factor Authentication to all staff; (b)
P pin to compareR raw source
Incident timeline — partial
? — ?
Breach window unknown
Dec 4, 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.