Crédit Mutuel Arkéa hit by cyberattack enabling fraudulent transactions of up to $133 million
French cooperative bank Crédit Mutuel Arkéa was targeted in a cyberattack that allowed fraudulent transactions of up to $133 million. The bank responded by suspending certain systems.

Key points
- Crédit Mutuel Arkéa, a French cooperative bank, was the target of the attack.
- The attack enabled fraudulent transactions of up to $133 million.
- The bank suspended certain systems in response.
- The headline attributes the heist to access via a service provider.
What was reported
Crédit Mutuel Arkéa, a French cooperative bank, was targeted in a cyberattack that made it possible to carry out fraudulent transactions of up to $133 million. According to the report, the bank reacted by suspending certain systems.
The report's headline links the incident to a service provider. The excerpt available to us does not give further detail, so we do not describe the attack method, the provider involved, the timeline or the recovery of funds.
Why it matters for Saudi institutions
The case is a reminder that a bank's exposure extends to the third parties that connect to its payment and operational processes. Even where the institution's own perimeter holds, access granted to a provider can become the route to fraudulent transactions. Suspending systems is also a recognised containment step, and it works best when it has been planned and rehearsed beforehand.
Suggested next steps
We suggest that risk and security teams use this report as a prompt to review third-party access and transaction controls, without waiting for further details to emerge. The actions below are practical starting points.
What to do now
- Inventory service providers that have access to payment, core banking or transaction-approval systems, and confirm the access each one holds.
- Review provider access for least privilege, strong authentication and monitoring of sessions.
- Check that fraud-detection and transaction-limit controls would flag unusual high-value transfers, including those initiated through provider channels.
- Rehearse the decision to suspend systems, including who authorises it and how business continuity is maintained.
- Confirm contractual incident-notification duties with providers and test the escalation path, including to SAMA where applicable.
How useful was this story?
0.0 out of 5 · 0 ratings
Our consultants can assess your exposure and map the change to your controls and evidence.