The M1 data breach is a 30 October 2026 incident at M1, a Singapore telecommunications company, in which customer personal data was exposed. M1 told affected customers on 6 November 2026 that names, NRIC or FIN numbers, dates of birth, mobile numbers, email addresses and residential addresses were involved. Payment card details, financial or banking information and customer account access were not compromised, according to the company. The breach has been contained. M1 gave no victim count, and none has appeared in reporting. The Personal Data Protection Commission (PDPC) said on 6 November that it is aware of the incident and is investigating.
Disclosure of the M1 breach
The disclosure came by email. No public notice page was found at the time of writing. M1 sent the email to affected customers on 6 November 2026. AsiaOne reported that one reader received it at about 8pm that evening. CNA saw the same email. It published the contents the same day. The Straits Times and The Business Times carried the same account on 6 November, and a search found no public notice page from M1 at the time of writing, so the customer email as reported by the four outlets is how the breach reached the public.
M1 apologised in the email. CNA quoted the passage as follows:
"M1 takes the security and confidentiality of information entrusted to us very seriously. We regret that this data breach has occurred and apologise for the concern it has caused you." Affected customers will be alerted by email or letter, according to M1. A customer who has received neither has no confirmation from M1 either way. No victim count and no full notification list have been published.
M1 breach data categories
Six categories of customer data appear in the email. They are residential addresses, email addresses, mobile numbers, dates of birth, NRIC or FIN numbers and names. An NRIC number is a Singapore identity card number. A FIN number identifies a foreigner resident in Singapore. The Straits Times listed the same items in its own wording: customer names, identity card details, dates of birth, mobile numbers, email addresses and addresses. The email gave no breakdown of how many customers had each category exposed, and no source said whether every affected customer had all six categories exposed or only some of them.
| Data category | Status in the breach |
|---|---|
| Email addresses | Exposed |
| Customer names | Exposed |
| NRIC/FIN numbers | Exposed |
| Dates of birth | Exposed |
| Mobile numbers | Exposed |
| Residential addresses | Exposed |
| Payment card details | Not compromised, per M1 |
| Financial or banking information | Not compromised, per M1 |
| Customer account access | Not compromised, per M1 |
M1 also stated what the breach did not touch. No payment card details were compromised, and no financial or banking information was compromised. Customer account access was not compromised either. The four outlets repeated the statement. The file holds identity data, not payment data, and its use is impersonation and targeted phishing rather than direct theft from a bank account.
M1 described the data as exposed. No source states whether the data left M1's systems or was only accessed. This article claims neither.
M1 response to the breach
The breach has been contained, according to M1. Services and business operations were unaffected throughout the incident, according to the company. Both statements were reported by The Business Times and The Straits Times on 6 November.
M1 told customers to remain vigilant. Customers should exercise caution when responding to unsolicited calls, messages or emails, and verify the identities of those who contact them through official channels. That advice sits at the centre of the response. The exposed data gives an attacker the details needed to make a fake call, message or email look genuine.
M1 said it has been working closely with the relevant authorities and third-party specialists on the ongoing investigations. The email and the reporting that followed it gave no further detail about the investigation.
PDPC response to the M1 breach
In a media reply on 6 November, the Personal Data Protection Commission said it is aware of the incident and is investigating the case. The Straits Times and The Business Times reported the media reply. AsiaOne reported that the PDPC told it the same. The PDPC regulates personal data protection in Singapore. No statement from the PDPC beyond the media reply was available at the time of writing. No enforcement action has been reported.
AsiaOne also reported a remark from Gwenda Fong, chief executive of the Cyber Security Agency of Singapore. She urged businesses on 6 November to review their security. The remark was made on the same day as the M1 disclosure, against the background of a recent run of reported breaches in Singapore.
Phishing risk from the M1 breach
That combination is dangerous for phishing. Together, a name, a date of birth, a mobile number, a home address and an email address give an attacker enough detail to write a message that appears to come from a bank, a delivery company or a government agency. The recipient is addressed by name, with correct personal details. The NRIC number adds a document number to that set. That makes impersonation attempts harder to spot.
An email address on its own does not open the mailbox behind it. Reading mail needs a password, a live session or provider access. The address alone supplies none of those. The guide on whether someone can read emails with only an email address sets that out. Reading M1 customers' email is not the risk here. The risk is convincing messages sent to those addresses, made to look legitimate with the other exposed details. The phone numbers and home addresses serve the same purpose by call or text. The guide on how phishing uses a leaked email describes that mechanism. A leaked address becomes the delivery channel. The other leaked details become the material that makes the message persuasive.
Steps for M1 customers
Receipt of the email confirms that a customer's data was involved. Customers without the email have no confirmation either way. M1 said it will alert affected customers by email or letter, and no victim count or full notification list has been published.
M1's stated advice is vigilance and caution with unsolicited calls, messages or emails. Senders should be verified through official channels before a customer responds. The advice covers every message that claims to come from M1, a bank, a delivery service or a government agency and asks for action, a password or a payment.
The guide on how to check if an email was leaked describes how to check whether an email address appears in known breach data. The check uses Have I Been Pwned. That database records which addresses appear in known breach datasets. Have I Been Pwned held no listing for the M1 breach at the time of writing. For this incident, the check has no answer yet. Once a listing appears, the guide is the method to use.
Each account that uses the exposed email address should have its own password, and a second factor should be switched on where one is offered. No passwords were exposed in the M1 breach, according to M1, so no password reset follows directly from the breach itself. Bank accounts need separate treatment. A bank account should keep a permanent real dedicated address used only for financial accounts, never an alias. Recovery, statements and fraud alerts depend on that address.
An M1 customer address is probably in this file. Check whether it is, do the password work above, and then fix the part you control: the address you hand out next time. One AliasFleet alias per service means the next leak can only point back to the service that leaked it. Founders Club is $7 a month, locked forever, instead of $12. Early members only.
M1 breach investigation
The investigation continues. M1 said it is working with the relevant authorities and third-party specialists. The PDPC said it is investigating. The attack vector remains undisclosed. How the attacker gained access has not been reported anywhere. M1's email dates the intrusion to 30 October 2026. No source has stated a wider window. This article does not claim the access lasted one day, or longer than one day.
No confirmed misuse has been reported for the exposed data. M1 has disclosed no victim count. Whether the data was copied out of M1's systems or only accessed has not been stated. This article claims neither. Only a fresh statement from M1 or the PDPC will close those gaps. A follow-up must be measured against a fresh statement, not against speculation.
Other Singapore disclosures in November 2026
A separate breach was disclosed the same day, 6 November 2026, by Doctor Anywhere, a Singapore healthcare provider. The statement gave no date for the unauthorised access. It gave no customer count. It did not name the type of data compromised. Doctor Anywhere reported the incident to the PDPC and filed a police report. Clinical records were not affected, according to the company. The Doctor Anywhere incident is separate from the M1 breach.
AsiaOne also recorded a recent run of reported breaches in Singapore. It named MoneySmart and Amadeus. Amadeus supports booking processes for Singapore Airlines. MoneySmart's disclosure came on 3 November 2026. Those incidents are separate, and this article does not cover them.
A telco breach took place on 30 October 2026 and was disclosed on 6 November. Identity data was exposed. Payment data and account access were unaffected according to M1. No victim count was disclosed. The PDPC is investigating. Affected customers will hear from M1 by email or letter, and customers who have already heard should treat unsolicited contact with the caution M1 described.
Top comments (0)