Olam Group Limited
bd_7ec0b9baf9bf6344 · 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 Olam Group Limited (the “ Organisation ”) notified the Personal Data Protection Commission (the “ Commission ”) on 4 December 2024 of a ransomware incident involving its servers (the “ Incident ”). The Organisation established that the threat actor (“ TA ”) had successfully connected to the VPN located in one of its overseas entities using valid credentials from a user account. By leveraging the user account, the TA gained the privileges of user accounts which enabled lateral movement across the Organisation’s network and data exfiltration from the Organisation’s servers. The Incident affected 42,351 individuals (largely involving the Organisation’s former, existing and potential employees) and the types of personal data affected varied by individuals, including a combination of names, addresses, personal email addresses, telephone numbers, dates of birth, photographs, national identification numbers, health information, financial information, life/health insurance information, demographic information, and professional and educational information. Upon discovery of the Incident, the Organisation took prompt remedial actions including disabling the specific VPN service to which the initial access was traced to, resetting the passwords, blocking outbound and inbound internet access to servers by the TA, and implemented dark web monitoring. The Organisation also notified the relevant affected individuals. The Incident had likely occurred due to delay in the renewal process of the VPN license in one of many jurisdictions where the Organisation operates, which enabled the validation of domain membership. The Organisation also did not have proper Multi-factor Authentication (“ MFA ”) processes as the second check of authentication had been configured but was not enforced due to the license expiry as noted. The Organisation also had weak password policies in place
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.