YMCYoseph Martin Christian
Case study · Maybank · 2026

Shielding a national banking app from malware.

How the MAE app learned to spot risky devices before a scam can happen, and what it took to roll that out nationwide. I led it end to end as technical lead and team lead.

10M+
Customers on the app
3
Platforms · iOS, Android, Huawei
Sep 2026
Nationwide rollout
2
National media features

The problem

Scammers increasingly reach bank customers through the customer’s own phone. A malicious app installed from outside the official store, a screen-sharing tool or a fake overlay can let someone else watch or control a banking session.

The banking industry in Malaysia responded by requiring banks to add malware shielding to their apps. MAE already had a first version; the task in 2026 was to make it detect more risks, and to do it for an app that more than ten million people rely on.

What the feature does

Each time the app is opened, it checks the device for signs of risk and responds in proportion: a notice, guidance on how to fix it, or a restriction until the risk is resolved. It does not read or collect personal information from other apps.

  1. 01

    Risky or malicious apps

    Apps known to be harmful, or installed from outside the official stores.

  2. 02

    Unsafe device settings

    Developer mode, a rooted or jailbroken system, an emulator or a cloned app.

  3. 03

    Screen sharing and overlays

    Screen sharing, recording or mirroring, and apps that draw over the screen.

  4. 04

    Unsafe connections and tampering

    VPNs, untrusted keyboards and modified versions of the banking app itself.

Source for the feature’s behaviour: Maybank’s Malware Shielding page.

My role

I owned the technical delivery from design to production, and was the main point of contact between engineering, testing, release, security and the business.

  • App integration. The warning and restriction screens across the app, the consent flow and the controls that switch protection on.
  • App hardening. Protected builds for iOS, Android and Huawei, in every environment from test to production.
  • Build automation. Scripts and CI lanes that replaced manual security build steps.
  • Testing and governance. Penetration testing, independent attestation, and security, architecture and compliance reviews under Malaysia’s central bank (BNM) and PCI requirements.
  • Release and operations. Go/no-go assessments for each build, daily crash monitoring, incident triage and work with the vendor on root causes.
  • Handover. Dashboards and operating procedures so operations teams can run and monitor the solution on their own.

What made it hard

  1. 01

    Protecting without slowing down

    A security check at every launch must not make the app feel slower or less stable, so launch performance and crashes were watched from the first build.

  2. 02

    Telling real problems from noise

    Once protection ships, every crash gets blamed on it. Tracing each issue to its actual cause kept the rollout moving and the fixes aimed at the right place.

  3. 03

    Three platforms, three pipelines

    iOS, Android and Huawei each have their own store, signing and build rules. Automating the protected builds made releases repeatable.

  4. 04

    Many audiences at once

    The business, testers, release managers, security reviewers and the vendor each needed a different answer to the same question.

Outcome

The enhanced Malware Shielding rolled out nationwide in stages from 26 September 2026, on 3 platforms. Customers whose devices show a risk are now warned, guided or restricted before a scam can use that weakness.

Covered in national media: Lowyat.NET and RinggitPlus both reported on the launch.

What I took from it

  • Own the outcome, not the ticket. The work is done when customers are protected and the app still works well for them.
  • Decide with evidence. Find the data first, then stand behind the position.
  • Make yourself replaceable. Documentation and automation are part of the delivery, because they let others carry the product.

This page describes only what is public. Vendor names, internal figures and implementation details are left out on purpose.

Building for mobile or web?

I’m happy to compare notes.