The Oddle Company Pte Ltd
bd_a89b585f2c14ae43 · schema v1 · pii pii-v1
Full breach record for The Oddle Company 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 The Oddle Company Pte Ltd (the “ Organisation ”) notified the Personal Data Protection Commission (the “ Commission ”) on 27 March 2024 of a data security incident that had occurred on 25 March 2024 in which their customers’ personal data was disclosed without authorisation (“ Incident ”). The Organisation established that the Incident was a result of unauthorised access to an internal employee account whereby the threat actor (“ TA ”) installed malicious code snippets on the checkout pages of certain merchants. This malicious code would load a third-party JavaScript script, which, when detecting a mobile browser, would hide the legitimate payment input form and layer a separate set of input fields on top of the legitimate payment input form. As a result of the Incident, the personal data of 7,358 individuals, from Singapore, Taiwan, Malaysia, and Hong Kong, was affected. The types of personal data affected included a combination of the full name, personal email address, contact number, and full credit card information. Upon discovery of the Incident, the Organisation took prompt remedial actions including the notification of all affected individuals, and the review of the code base to ensure no secret key is stored in the repository. Additionally, the Organisation would verify all scripts before they are allowed to go live and would also detect and monitor new IP addresses. 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 29 August 2024. As part of the Undertaking, the Organisation will be implementing the following: (a) Implement IP whitelisting for all customers’ login to reduce risk of unauthorised access from unknown IP addre
P pin to compareR raw source
Incident timeline — partial
? — ?
Breach window unknown
Jul 31, 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.