DisclosureLens
SINGAPOREUnknownLow

Yamato Transport Pte Ltd

bd_abcde9eb7823651a · schema v1 · pii pii-v1

Severity

Low

Discovered

Filed

Mar 27, 2025

To disclose

Affected

Not disclosed

Confidence

90%
Full breach record for Yamato Transport 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 On 6 September 2024, a client of Yamato Transport (S) Pte. Ltd. (the “ Organisation ”) notified the Personal Data Protection Commission (the “ Commission ”) of a data breach incident (the “ Incident ”) involving the Organisation. The Organisation had notified all of its clients, whom it had acted as a data intermediary, of the Incident. Subsequently, other affected clients also notified the Commission. The Incident involved unauthorised access to the Organisation’s server, which stored its clients’ data. As the Organisation’ employee data were also affected, it also notified the Commission on 4 October 2024. Investigations revealed that the threat actor (“ TA ”) had gained access to the Organisation’s system by exploiting a zero-day vulnerability to gain initial access to the Organisation’s environment. Thereafter, the TA further exploited vulnerability of the Organisation's system and executed a ransomware. The exfiltrated files contained the personal data of 320,482 individuals, belonging to the Organisation's clients and employees . The types of personal data affected include various combination of name, address, email address, phone number and other information. Upon discovery of the Incident, the Organisation took prompt remedial actions including, but not limited to, disconnecting the affected servers, patching the zero-day vulnerability, resetting passwords for all users, blocking the TA’s IP address and isolating all affected servers and terminating internet connections. 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 20 January 2025. As part of the Undertaking, the Organisation will be implementing the following: (a) Enh

Incident timeline — partial

? — ?

Breach window unknown

Mar 27, 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

Leak-site claim

Attacker assertion only. Establishes: claim date, group, alleged victim.

Press / market report

Unlocks: incident narrative, operational impact. Still no compliance clock.

State AG / regulator filingThis record

Unlocks: discovery date, data types, affected count, compliance clock.

SEC 8-K / victim statement

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.