Kingsmen Creatives Ltd.
bd_740af0fab744caa9 · schema v1 · pii pii-v1
Full breach record for Kingsmen Creatives 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 29 April 2025, Kingsmen Creatives Ltd. (the “ Organisation ”) notified the Personal Data Protection Commission (the “ Commission ”) of a personal data breach involving a ransomware attack which affected multiple servers and a user’s laptop (the “ Incident ”). The Organisation established that the threat actor (“ TA ”) likely gained access to its system on 26 April 2025 using credentials from a compromised Virtual Private Network (“VPN”) account. Exploiting other system vulnerabilities, the TA encrypted the Organisation’s files containing the personal data of 445 individuals, who were the Organisation’s current (342 individuals) and former (103 individuals) employees. The types of personal data affected included names, NRIC numbers, NRIC copies, dates of birth, contact information (mobile numbers, email addresses and home addresses), bank account details (bank name and bank account number) and next-of-kin details (names, mobile numbers and relationship to the employee). Upon discovery of the Incident, the Organisation took prompt remedial actions including isolating affected network systems, blocking all incoming traffic from the firewall while allowing only outbound connectivity on weekdays, resetting all account passwords and retaining only a single administrative account on the Domain Controller. The Organisation also notified the affected individuals. The Incident had likely occurred as the Organisation had inadequate security measures prior to the Incident including a weak password policy, absence of regular access reviews, absence of a documented incident response plan and no implementation of multi -factor authentication (“MFA”) for VPN and privileged accounts. Voluntary Undertaking Having considered the circumstances of the case, the Commission accepted a voluntary undertaking (the “ Undertaking ”) from the Organisation to improve its compliance w
J jump to incidentP pin to compareR raw source
Incident timeline — partial
? — ?
Breach window unknown
May 7, 2026
Filed
—
Corroborated · see linked filings
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.
Linked disclosures
Why this link?Ransomware claims (2)
- Leak Siteembargobd_a8a3e4ebc44e10a32025-05-02 · +370dVerified by operator
- Leak Siteembargobd_7ae3ee5196edc14a2025-04-30 · +372dCandidate
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.