ZenWeb - Blog - Data Breach Notification Malaysia: Steps After a Leak

Data Breach Notification Malaysia: Steps After a Leak

November 1, 2026

Share this post:

Data Breach Notification Malaysia: Steps After a Leak
TL;DR: Data breach notification in Malaysia has been mandatory since 1 June 2025. A business whose personal data breach causes, or is likely to cause, significant harm must notify the Personal Data Protection Commissioner within 72 hours. A breach affecting more than 1,000 people counts too. Affected customers must be told within 7 days of that notice if harm is likely. Every breach, reported or not, goes into a register kept for at least two years.

A leaked lead spreadsheet. A newsletter with every address in the CC line. A hacked WooCommerce plugin. For most SMEs, the first personal data breach starts in marketing, not the server room.

This guide covers the rules from the website, e-commerce and lead generation side. It comes from ZenWeb, a Malaysian Google Partner agency with 500+ clients. We build websites, lead forms and tracking; we are not a law firm. Every rule below comes from the Commissioner’s Data Breach Notification Guideline (Version 1.0, issued 25 February 2025), as at October 2026.

This post is general information, not legal or tax advice. Please confirm your own position with a licensed lawyer, and check the latest guidance on the Commissioner’s website before you act.

Worried your forms or plugins are the weak spot?

We audit WordPress sites for exposed form data, stale plugins and loose admin access before anything leaks. See our web development services →

Before the detail, this short explainer from a Malaysian law firm walks through the mandatory regime as it was introduced in 2025.

Mandatory Data Breach Notification in Malaysia (HHQ)

Source video: HHQ on YouTube. Recorded in April 2025; check the Commissioner's website for the current rules.

1. What Counts as a Personal Data Breach in Malaysia?

Quick Answer: A personal data breach is any event that leads, or is likely to lead, to the breach, loss, misuse or unauthorised access of personal data. It can be accidental or deliberate, internal or external. Sending customer data to the wrong person, a misconfigured system or a hacker extracting records all count, as does losing access to data.

Section 12B of the Personal Data Protection Act 2010, added by the Personal Data Protection (Amendment) Act 2024, created the duty. The Commissioner’s Data Breach Notification Guideline lists examples in paragraph 4.2. Translated into marketing terms, these are the ones we see most:

  • Wrong recipient. A lead export or invoice emailed to the wrong person.
  • System misconfiguration. A form-entries folder left publicly indexable, or a lead sheet shared as “anyone with the link”.
  • Unlawful access. A hacker gets into WordPress admin or the CRM and pulls customer lists.
  • Loss of availability. Ransomware locks the customer database, or you lose the key to encrypted backups.

Not every website incident triggers data breach notification in Malaysia. A defaced homepage or scraped blog content is a security or copyright problem; see our steps for when your website content is copied. Prevention sits in our guide to PDPA security for web systems; this post covers what happens after a leak.

Key takeaway: If personal data went somewhere it should not, or you can no longer reach it, treat it as a breach first and assess it second.

2. When Must You Notify the Commissioner? The Significant Harm Test

Quick Answer: Under data breach notification in Malaysia, you must notify the Commissioner only when a breach causes or is likely to cause “significant harm”. That covers risk of physical harm or financial loss, misuse for illegal purposes, sensitive personal data, data that could enable identity fraud, or significant scale, meaning more than 1,000 affected people. Telling customers uses the same test minus the scale limb.

Paragraphs 5.2, 5.3 and 8.2 of the guideline set the test. The table shows who you must tell under each limb.

Significant harm criteria and who must be notified, as at October 2026
Significant harm criteria and who must be notified under each.
Criterion (para 5.2)Notify CommissionerNotify affected peopleMarketing example
Physical harm, financial loss, credit or property damageYesYesCustomer home addresses plus order history leaked
Misuse for illegal purposesYesYesLead list stolen and used for scam calls
Sensitive personal dataYes, at any volumeYesForm answers on religious belief or health
Combined data enabling identity fraudYesYesNames with IC numbers and phone numbers
Significant scale (more than 1,000 people)YesNot by scale aloneNewsletter sent with 3,000 addresses in CC

Source: Personal Data Protection Commissioner, Data Breach Notification Guideline, paragraphs 5.2, 5.3 and 8.2; examples are ZenWeb’s. As at October 2026. Licence.

The sensitive data row is why we push clients to remove unnecessary questions from lead forms; our guide to sensitive personal data in lead forms explains which fields qualify. Card data is a separate risk again, covered by the PCI DSS rules for small online stores.

Key takeaway: Volume alone can trigger a report to the Commissioner. One sensitive field can trigger it at any volume. Fewer fields and fewer stored records mean fewer reportable breaches.

3. When Does the 72-Hour Clock Start?

Quick Answer: Notify the Commissioner as soon as practicable and no later than 72 hours from the breach. The guideline’s examples start the clock when you are told of a loss, realise a mis-send, or confirm your system was compromised. If your agency or software vendor holds the data, it starts when they tell you or you find clear evidence, whichever is earlier.

Paragraph 6.1 says 72 hours “from the occurrence”, while the worked examples in paragraph 6.2 count from awareness or confirmation. That wording gap is not fully settled, so plan on the earlier reading. The guideline gives no extension for weekends or public holidays. Here is the full timeline.

Data breach notification in Malaysia: deadlines from detection to record-keeping
Breach notification deadlines from detection to record retention.
WhenWhat must happenGuideline paragraph
Hour 0Incident detected or reported; preliminary investigation begins6.2
Within 72 hoursNotify the Commissioner with all mandatory form fields6.1, 7.2
After 72 hours (if late)Written reasons for the delay with supporting evidence7.7
Within 7 days of noticeNotify affected people, if significant harm is likely9.1
Within 30 days of noticeSend remaining details in phases7.5
At least 2 yearsKeep the breach register, including unreported breaches14.1

Source: ZenWeb compilation from the Commissioner’s Data Breach Notification Guideline (Version 1.0, 25 February 2025), as at October 2026. Licence.

Agencies and SaaS tools are usually data processors. Under paragraph 12 the duty does not apply to them directly, so your contract must require them to tell you promptly. For overseas tools, also check cross-border data transfer under PDPA.

Key takeaway: Assume the clock started the moment someone noticed. Three days pass quickly when the leak is found on a Friday evening.

4. Steps After a Data Leak: The First 72 Hours

Quick Answer: Contain first, then assess, then report. Isolate the affected system, disable compromised logins and stop whatever caused the leak. Work out what data, how many people and which systems were involved. Decide whether the significant harm test is met, file with the Commissioner inside 72 hours, and log everything in your breach register.

Paragraph 13 of the guideline covers containment and assessment. Here is our data breach notification Malaysia checklist for a website or marketing leak:

  1. Contain the leak. Take the exposed form, folder or plugin offline and revoke public share links.
  2. Lock down access. Reset WordPress, hosting, CRM and ad account passwords; remove unknown admin users; turn on two-factor login.
  3. Preserve evidence. Keep server logs, plugin logs and screenshots before cleaning up.
  4. Count who is affected. Export the affected records and remove duplicates. CRM export tools built for data portability under PDPA make this much faster.
  5. Classify the data. Note IC numbers, financial details or sensitive fields, then run the significant harm test.
  6. Brief your contact point. Your DPO, or a senior named representative if you do not need one, leads the report.
  7. File the notification. Submit within 72 hours and wait for the Commissioner’s confirmation notice.
  8. Record the decision. Add the breach to your register, including why you did or did not notify.

Not sure if you need a DPO? Read who must appoint a data protection officer in Malaysia. Here is an illustrative, not client-based, use of the 72 hours.

Illustrative 72-hour response plan for an SME website leak (hours per phase)
Illustrative split of the 72-hour window by response phase.
PhaseHoursShare of 72 hours
Confirm the breach (hours 0–6)6
Contain and lock down (hours 6–18)12
Count and classify data (hours 18–42)24
Prepare the form and approvals (hours 42–60)18
File and get confirmation (hours 60–72)12

Source: Illustrative scenario by ZenWeb; 72-hour limit from paragraph 6.1 of the Commissioner’s Data Breach Notification Guideline, as at October 2026. Licence.

Counting usually takes longest, because leads sit in several tools. Leave a filing buffer in case the online form or email fails.

Key takeaway: You do not need every answer to file on time. Submit the mandatory fields inside 72 hours and send the rest in phases within 30 days.

Need the website side cleaned up fast?

We help lock down WordPress, close exposed form folders and pull the logs your lawyer and DPO will ask for. Read our WordPress website security guide →


5. How to Report a Data Breach to the Commissioner

Quick Answer: Use one of three channels in paragraph 7.1: the online notification form on the Department of Personal Data Protection website, the Annex B form emailed to dbnpdp@pdp.gov.my, or a hard copy of Annex B delivered to the Commissioner. The report only counts as submitted once you receive the Commissioner’s confirmation notice.

The online route is the Lapor DBN page, and the Commissioner publishes a DBN report guide for organisations. The Annex B form asks for these details, so prepare them as you assess:

  • Basics. New report or update, and whether you are filing within 72 hours; if not, reasons with evidence.
  • The breach. When and how you found out, how data was affected, the suspected cause and the system involved.
  • The data. Where it is stored, types of data, number of people affected, and whether non-Malaysians are included.
  • Harm and response. Likely harm, containment steps, actions for affected people, and contact with any threat actor.
  • Other notices. Other regulators told, and a sample customer notice.

One point is unclear: the guideline cites “Circular No. 2/2025”, while the Commissioner’s website lists the data breach circular as No. 1/2025. Ask your lawyer which to cite. Critical information infrastructure entities also notify the National Cyber Security Agency; see the Cyber Security Act 2024 and your website for who that covers.

Key takeaway: Keep a blank copy of the Annex B form in your incident folder now. Filling it in for the first time during a live breach costs hours you do not have.

6. Do You Have to Tell Customers About a Data Breach?

Quick Answer: Yes, if the breach is likely to cause them significant harm. Tell them directly and individually, in plain language, within 7 days of notifying the Commissioner. Explain what happened, the likely consequences, what you are doing, what they can do, and who to contact. Send it separately from newsletters or promotions.

Paragraph 10 lists email, SMS, direct messaging and post as individual channels. A website or social media notice is allowed only where direct contact is impractical, such as outdated contact details. Three practical rules:

  • Use a plain, non-promotional email. No banners or discount codes; the guideline wants it separate from regular messages.
  • Do not hide it in WhatsApp broadcasts. If you use WhatsApp, send a one-to-one style message with the required details; our guide to WhatsApp marketing and PDPA covers consent for that channel.
  • Prepare for requests. Customers often ask what you hold after a breach. Follow the PDPA steps for access and deletion requests.

One exception from the guideline’s examples: if strong security made the data unreadable to the attacker, customers may not need a notice, though the Commissioner still does.

Key takeaway: A breach notice is a service message, not a campaign. Draft a plain template now so nobody adds a promo banner under pressure.

7. Common Marketing and Website Leaks: Which Ones Are Notifiable?

Quick Answer: For data breach notification in Malaysia, most marketing leaks turn on two facts: how many people are affected and whether the data includes IC numbers, financial details or sensitive fields. A small mis-sent list of names and emails is usually record-only. A large exposed lead sheet or any leak with IC numbers usually needs a report to the Commissioner.

The table applies the test to scenarios we see on SME websites. It is ZenWeb’s reading, not an official ruling.

Marketing and website breach scenarios against the notification test, as at October 2026
Six marketing breach scenarios and likely notification duties.
ScenarioCommissionerCustomers
200 lead names and emails sent to the wrong vendorUnlikelyUnlikely
Newsletter sent with 3,000 addresses visible in CCYes (scale)Assess
Public lead sheet with 1,500 names and phone numbersYes (scale)Assess
Form entries with IC numbers exposed by a plugin flawYesYes
Online store database with addresses and orders stolenYesLikely
Ransomware locks the CRM with no backupYesLikely

Source: ZenWeb’s reading of paragraphs 5.2 to 8.3 of the Commissioner’s Data Breach Notification Guideline, as at October 2026. Interpretation only; confirm with a lawyer. Licence.

Check two newer leak routes. Session recordings can capture typed form fields; see heatmaps and session recordings under PDPA. Server-side ad events send customer data to platforms; read Meta Conversions API and PDPA.

Key takeaway: “Unlikely” still means “record it”. Every scenario in the table goes into your breach register, reported or not.

8. Breach Register, Response Plan and Penalties

Quick Answer: Data breach notification in Malaysia also means record-keeping. Keep a breach register for at least two years, covering every breach including those you did not report. Have a written response plan with escalation steps, roles, containment, notification decisions, communications and a post-incident review. Failing to notify under section 12B can mean a fine of up to RM250,000, up to two years’ jail, or both.

The penalty is stated in paragraph 2.2 of the Commissioner’s guideline. Paragraph 14 says the register should record, at minimum:

  • Description. When you found out, root cause, data types, people and records affected, system involved.
  • Consequences. The likely effect on the people involved.
  • Chronology. The events leading to the breach.
  • Response. Containment and recovery steps taken.
  • Notifications. What you reported and to whom, or why you did not.

Holding less data shrinks future breaches. Set a retention period using our guide to how long you can keep leads under PDPA. After any fix to your forms, re-test them as part of your normal CRO process so security changes do not quietly break conversions. For the wider duty list, see our PDPA compliance checklist for marketers.

Key takeaway: The register is your evidence. A well-kept log of small, unreported incidents shows the Commissioner you take the rules seriously.

9. Conclusion: Prepare Before the Leak, Not During It

Data breach notification in Malaysia is a 72-hour test of preparation. As at October 2026, you must notify the Commissioner when a breach risks significant harm or affects more than 1,000 people, tell affected customers within 7 days if harm is likely, and log every incident for two years. Have three things ready: a short response plan, a blank Annex B form, and forms that collect only the data they need. For the website side, our web development team can help.


10. Frequently Asked Questions

1. Is data breach notification in Malaysia mandatory?

Yes. Since 1 June 2025, section 12B of the Personal Data Protection Act 2010 requires data controllers to notify the Commissioner of breaches that cause or are likely to cause significant harm, and to notify affected people where harm is likely.

2. How long do I have to report a data breach in Malaysia?

No later than 72 hours to the Commissioner, and no later than 7 days after that notice to affected people. Missing details can follow in phases within 30 days.

3. Do small businesses have to report breaches?

Yes. Size is not part of the test; the type of data and the number of people affected are.

4. Does my marketing agency have to report a breach of my leads?

Not directly. The guideline says the duty sits with the data controller, so your contract should require your agency or vendor to tell you promptly and help you report.

5. Can ZenWeb file the notification for me?

No. ZenWeb handles the website and marketing side, such as securing forms, plugins and tracking. Confirm your notification duties with a licensed lawyer.

Cite this page: ZenWeb (2026). Data Breach Notification Malaysia: Steps After a Leak. https://zenweb.my/blog/data-breach-notification-malaysia/

You may quote our data with this credit and a link. See our Terms of Use.

Make your website harder to leak

Talk to ZenWeb about lean lead forms, secure plugins and PDPA-friendly tracking, so a bad day stays small. We handle the website side; your lawyer handles the legal advice.

Book a free consultation →

Table of Contents
Table of Contents

Get A Free Proposal

Complete the form and our team will contact you to discuss your goals. Let’s grow your business.