Skip to content
Cloud Security Breaches

People Central Pte. Ltd. (2026): what the sources say about the cloud incident

People Central Pte. Ltd. disclosed the incident on 8 Jan 2026. The ledger reads the access path as exposed network services and request paths. The cloud or provider involved: AWS. Every field rests on the primary sources listed below. Fields no primary source states read not public.

Open the ledger · Report a correction

Disclosed
8 Jan 2026
Incident window
29 April 2024 (extortion email); discovered by 3 May 2024
Cloud or provider
AWS
What was exposed
The PDPC decision states personal data of 95,000 employees of the company's clients was put at risk (including name, identity card number, salary, bank account number and address), plus 24,765 emergency contacts and children. The threat actor deleted databases and likely exfiltrated data, and data was found for sale on the dark web.
How access was gained
The decision says the company, a cloud-based HR software provider, had Remote Desktop Protocol access open to the internet without two-factor authentication on its AWS cloud servers, settings allowed inbound traffic from all IP addresses in the cloud environment, and SQL injection vulnerabilities were present with no web application firewall.
Access path
Exposed network services and request paths
Kind of control that addresses it
close management ports to the internet, restrict cloud network rules to known addresses, require MFA for remote access, and test web applications for injection

In the words of the source

“Remote Desktop Protocol ( RDP ) access had been open to the internet and did not require two-factor authentication ( 2FA ).” (regulator filing, PDPC decision: People Central Pte. Ltd.)

Primary sources

If a field is wrong or a newer primary source exists, write to the editor with the entry name in the subject.

Sources

  1. PDPC decision: People Central Pte. Ltd., read 16 Nov 2026

Last reviewed 16 Nov 2026.