DCS Card Centre Pte Ltd
bd_18a70d55cf6f8511 · schema v1 · pii pii-v2
Full breach record for DCS Card Centre 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 DCS Card Centre Pte Ltd (the “Organisation”) notified the Personal Data Protection Commission (the “Commission”) on 20 February 2026 of a personal data breach involving its Credit Card Management System (the “Incident”). The Organisation is a non-bank financial institution which issues credit and charge cards. The Organisation’s Credit Card Management System (the “System”) was hosted in a virtual private cloud environment. The Organisation established that unknown threat actor(s) (“TA”) had accessed the System on 19 February 2026, by exploiting internal Application Programming Interface (“API”) endpoints which were publicly accessible over the Internet at the time of the Incident. The API endpoints were supposed to be accessible only within a trusted internal network for internal service communications and were not intended to be exposed to the public Internet. The API endpoints became publicly exposed after IP whitelisting, a perimeter access control, was removed by the Organisation in December 2025 to accommodate operating a third-party solution. After gaining access, the TA exfiltrated personal data from the System. The Organisation’s IT team discovered the Incident on the same day. The data breach affected 22,076 individuals and the types of personal data affected included a combination of names, residential address, personal email address, passport and other national identification document numbers, mobile phone number, date of birth, nationality, with a smaller number of income information and full credit card numbers (without CVV). There was no evidence of public exposure or misuse of the affected personal data. Upon discovery of the Incident, the Organisation took prompt remedial actions including implementing Web Application Firewall (“WAF”) blacklisting rules, encrypting data at rest, enforcing digital signing of inter-service data requests and im
P pin to compareR raw source
Incident timeline — partial
? — ?
Breach window unknown
Oct 26, 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.