M1 Data Breach History

This page tracks the M1 data breach history and cybersecurity incidents affecting M1 (Singapore). BreachHistory currently indexes 1 publicly disclosed or catalogued incident spanning 2026, with approximately an unknown number of records reported as exposed across all indexed events. These totals may include overlapping datasets or third-party estimates and should not be interpreted as unique affected users.

The M1 breach timeline includes major data breaches, cyber attacks, data leaks, credential exposures, API abuse, and other security incidents. Each incident provides details on the estimated records exposed, attack method, affected data types, and supporting public sources. Currently, 0 incidents are company-confirmed.

Largest M1 Data Breaches

Indexed M1 incidents are listed below. Where a public count is unavailable, the catalog shows unknown records exposed. Open each page for attack method, data types, and sources.

• 2026 2026 M1 — customer personal data leaked Oct 30; NRIC/FIN, DOB, contact details; census unpublished — about Unknown records exposed · Catalogued incident

What Information Was Exposed?

Depending on the incident, exposed data may include email addresses, phone numbers, names, physical addresses, payment card and financial account data, bank account details, and other personal information (PII). The exact data varies between incidents, so review each breach page before assuming your information was affected.

M1 Data Breach 2026

At the time of this update, BreachHistory catalogues 1 2026 incident related to M1. Most recent entry: 2026 M1 — customer personal data leaked Oct 30; NRIC/FIN, DOB, contact details; census unpublished. New incidents are added as official disclosures, regulatory filings, or credible cybersecurity reports become available.

What To Do If You Were Affected

If you believe your account may have been involved in a M1 data breach, change any reused passwords, enable multi-factor authentication (MFA), monitor your account for suspicious activity, and be cautious of phishing emails or fake breach notifications.

This M1 breach history is maintained by BreachHistory using public disclosures, regulatory filings, security research, and clearly labelled third-party claims. For the complete breach timeline, records exposed, incident details, and AI Breach Risk Score, explore the sections on this page.