Skip to the content
MoneySmart confirmed a data breach affecting customers in Singapore and Hong Kong after an unauthorised third party accessed its internal IT systems and copied personal data. The company discovered the unauthorised access on 29 October and
MoneySmart · Singapore, Singapore3 November 2026Verified

MoneySmart confirmed a data breach affecting customers in Singapore and Hong Kong after an unauthorised third party accessed its internal IT systems and copied personal data. The company discovered the unauthorised access on 29 October and

MoneySmart identified and halted unauthorised access to its systems on 29 October. The breach impacted customers located in Singapore and Hong Kong.

01

What happened

The company experienced a security incident involving unauthorised access to customer data.

Verification record

Verdict
Verified
Headline supported
Supported
Evidence standing
Verified
Corroboration
Not assessed
  • The material retrieved was the record itself.
  • The source was reachable when the record was checked.
  • Actor confirmed: MoneySmart.
  • Date confirmed: 3 November 2026.

Discrepancies

None recorded.

02

What the source states

MoneySmart confirmed a data breach affecting customers in Singapore and Hong Kong after an unauthorised third party accessed its internal IT systems and copied personal data. The company discovered the unauthorised access on 29 October and stopped it subsequently.

03

Where it sits in the system

This event highlights operational risks regarding data security for financial technology firms operating in the region.

Boundary of the record

  • ·This record has been read against its source. The reading establishes what the source states, and nothing beyond it.
  • ·The address resolved to a listing page or an unrelated page rather than the record itself, so it is not presented as a source.
  • ·Discrepancy against the source: The page does not report a data breach at MoneySmart.
  • ·Discrepancy against the source: The page is a general news index and not an announcement record for the claimed event.
  • ·The address resolved to a listing page rather than the announcement itself, so it is not presented as the source.
  • ·Located from the listing page at https://sbr.com.sg/news, which is preserved as the discovery provenance, and read at its own address.
  • ·Reading established by the recovery worker after the record was held. The evidence is the page at the address recorded here, read against its own statement.

No interpretation is recorded. Discovery produces candidates and stops.

04

What this does not establish

The boundary of the record is stated with it, and travels wherever it is displayed.

Provenance

  1. Source date

    3 November 2026

    When the source is dated.

  2. Observation date

    3 November 2026

    When the event occurred, as the source states it.

  3. Retrieval date

    6 November 2001

    When Lawton obtained the material.

  4. Publication date

    15 November 2026

    When the item entered the feed.

  5. Checked

    15 November 2026

    When the record was read against its source.

05

How we know

The record keeps four dates apart: when the source is dated, when the event occurred, when Lawton obtained the material, and when the item entered the feed. They are not interchangeable, and none is substituted for a missing one.

The intelligence judgment

Corporate signal discovered in Singapore.

Decision state
Not Established
Editorial state
Development

Related published developments