Fraud
3 min

Mule Accounts and Session Hijacks: The Next Fraud Challenge for Philippine Payments

Written by
Greg Storm
Published on
November 26, 2025

TLDR

The Bangko Sentral ng Pilipinas (BSP) is intensifying its focus on digital fraud, driven by a sharp rise in mule accounts, session hijacks, and social engineering scams. Under BSP Circular 1213, financial institutions are now required to strengthen their fraud management frameworks and move toward dynamic, multi-factor authentication across digital channels. These regulatory changes signal a shift from reactive fraud response to proactive authentication control. Mule networks and hijacked sessions thrive on weak or static verification systems — meaning stronger, device-bound authentication is now essential. Ideem’s Zero-Trust Secure Module (ZSM) and Passkeys+ help institutions comply with BSP guidance while improving checkout conversion by making secure transactions faster and frictionless.

The new face of fraud in the Philippines

The Philippines’ payments ecosystem has rapidly digitalized, with wallets, online banks, and merchants all competing to capture mobile-first consumers. But the same growth that enabled financial inclusion has also given rise to new fraud patterns.

Two forms dominate the current landscape:

  • Mule accounts, which are legitimate accounts used by fraudsters to move illicit funds, often opened with stolen or synthetic identities.

  • Session hijacks, where attackers take over active user sessions to authorize transfers or purchases without needing passwords or OTPs.

These attacks exploit the weakest layer of digital payments — identity verification during and after authentication. Many systems still rely on SMS OTPs or static login tokens that can be intercepted or reused. In a country where mobile penetration is high and social engineering remains widespread, these weaknesses are being exploited at scale.

BSP Circular 1213: raising the bar for authentication

BSP Circular 1213, issued in 2024, requires supervised institutions to implement enhanced anti-fraud measures across digital channels. It mandates real-time fraud monitoring, stronger user verification, and proactive detection of mule account activity.

The circular encourages the use of:

  • Dynamic, multi-factor authentication

  • Risk-based fraud management systems

  • Continuous session monitoring

  • User behavior and device profiling

For banks, fintechs, and payment gateways, this isn’t just a compliance requirement — it’s a competitive shift. Those that can prevent fraud and preserve user experience will define the next phase of growth in the Philippine payments market.

Why mule accounts and session hijacks thrive

Mule networks are difficult to detect because each account appears legitimate on its own. They’re often recruited through social media or online job scams, turning ordinary users into conduits for stolen money. Fraudsters layer transactions across multiple accounts to avoid detection, using instant transfers and wallet hops to obscure the trail.

Session hijacks, meanwhile, target authenticated users. Attackers insert malicious code or hijack tokens during active sessions, often through phishing links or infected apps. Once a session is compromised, the fraudster can approve transactions directly — bypassing login or OTP verification entirely.

In both cases, the problem stems from the same issue: systems that can’t verify which device actually approved the transaction. Without a deterministic link between the account and the device, fraud detection becomes guesswork.

Authentication as the new compliance control

Under BSP’s guidance, stronger authentication is now the front line of fraud prevention. This doesn’t mean more friction; it means smarter validation. Device-bound credentials — where the identity of the device itself becomes part of the verification process — provide that assurance.

Ideem’s ZSM and Passkeys+ deliver this capability by cryptographically linking user accounts to trusted devices. Every transaction or login request is validated against this device identity in real time. If the request comes from an unregistered or altered device, it can be stopped before any funds move.

This deterministic approach aligns directly with BSP’s call for multi-factor, risk-based authentication while reducing the delays and drop-offs that often come with legacy OTP methods.

Why secure authentication also boosts conversion

For many Philippine banks and fintechs, the trade-off between security and conversion has been costly. Extra steps like OTPs and captchas can cause users to abandon payments mid-checkout — especially in mobile environments where connectivity fluctuates.

Device-bound authentication eliminates that tension. Once a device is registered and verified, future transactions can occur seamlessly, often without any visible login prompt. The authentication happens invisibly through cryptographic validation, ensuring compliance without adding friction.

As institutions implement BSP’s enhanced anti-fraud requirements, those who adopt such frictionless models will likely see:

  • Higher approval rates for legitimate users

  • Fewer false declines due to improved risk precision

  • Reduced checkout abandonment across wallet and card payments

  • Lower fraud losses through deterministic verification

A readiness checklist for Philippine financial institutions

  1. Map your fraud exposure
    Identify where mule activity or session hijacking could occur — from onboarding to checkout.

  2. Implement device-bound authentication
    Link accounts to trusted devices and ensure each transaction can be traced back to a verified endpoint.

  3. Adopt real-time session monitoring
    Detect unauthorized session activity instantly rather than after a dispute or loss.

  4. Move beyond OTPs
    Replace SMS-based verification with cryptographic passkeys and biometrics for stronger user assurance.

  5. Deploy Ideem’s ZSM and Passkeys+
    Use these tools to integrate zero-trust verification and dynamic risk evaluation directly into existing payment infrastructure.

Looking ahead

The Philippines is entering a new phase of digital payment maturity. As the BSP raises the bar for fraud prevention, the institutions that adapt fastest will gain both trust and market share. The combination of stronger authentication, risk-based detection, and device-level verification will define that evolution.

Mule accounts and session hijacks are symptoms of systems that trust the wrong signals — usernames, passwords, OTPs. The future of fraud prevention lies in trusting the right ones: verified devices, cryptographic credentials, and zero-trust logic.

Ideem’s Zero-Trust Secure Module and Passkeys+ offer a path forward. They help Philippine banks, wallets, and payment gateways comply with BSP regulations while delivering seamless, secure user experiences. In a payments landscape defined by speed and vulnerability, strong authentication is no longer optional — it’s the only sustainable advantage.

Sources

  1. Bangko Sentral ng Pilipinas – Circular No. 1213: Enhanced Anti-Fraud Management for Digital Channels
    https://www.bsp.gov.ph/Regulations/IssuedCirculars/Circular1213.pdf

  2. The Philippine Star – BSP Enforces Stricter Rules vs Scammers Under Circular 1213
    https://www.philstar.com/business/2024/06/04/2447974/bsp-enforces-stricter-rules-vs-scammers

  3. Inquirer.net – BSP Orders Banks to Strengthen Fraud Controls in Digital Banking
    https://business.inquirer.net/438562/bsp-orders-banks-to-strengthen-fraud-controls-in-digital-banking

  4. Clari5 – Future-Ready Fraud Defense in the Philippines: Aligning with BSP Circular 1213
    https://www.clari5.com/future-ready-fraud-defense-in-philippines-clari5-alignment-with-bsp-circular-1213/

  5. Ideem – Device Binding and Passkeys+ for BSP-Aligned Fraud Prevention
    https://www.useideem.com/passkeys-plus

Weekly newsletter
No spam. Just the latest releases and tips, interesting articles, and exclusive interviews in your inbox every week.
Read about our privacy policy.
Thank you! Your submission has been received!
Oops! Something went wrong while submitting the form.