Skip to content
Cloud Security Breaches

GeniusU Pte. Ltd. (2022): what the sources say about the cloud incident

GeniusU Pte. Ltd. disclosed the incident on 21 Apr 2022. What was exposed, as the sources state it: The PDPC decision states about 1.26 million users' first and last name, email address, location and last sign-in IP address were accessed and exfiltrated from a staging application database.

Open the ledger · Report a correction

Disclosed
21 Apr 2022
Incident window
before 12 January 2021
Cloud or provider
GitHub
What was exposed
The PDPC decision states about 1.26 million users' first and last name, email address, location and last sign-in IP address were accessed and exfiltrated from a staging application database.
How access was gained
The decision says the likely cause was a compromise of a developer's GitHub password, which let the threat actor into the company's GitHub environment; database login credentials had been stored in the codebase there, so the actor reached and exfiltrated the database. The staging database held real personal data.
Access path
Leaked access keys and secrets; also Stolen user credentials and session tokens
Kind of control that addresses it
keep database credentials out of code repositories, require MFA on every developer account, and keep real personal data out of test environments

In the words of the source

“As the Organisation had stored the login credentials to the Database in the codebase in its GitHub environment, the threat actor was able to gain access to and exfiltrate personal data stored in the Database.” (regulator filing, PDPC decision: GeniusU Pte. Ltd. (summary of the decision))

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: GeniusU Pte. Ltd. (summary of the decision), read 16 Nov 2026

Last reviewed 16 Nov 2026.