SOCLYDE logo
Current languageEN
Cybersecurity newsCybersecurityarkea

Arkéa fraud prompts checks on bank transfers

Arkéa confirms fraud through a supplier platform. The bank says customer holdings are unaffected; check delayed transfers and unexpected messages.

Published on

By Soclyde Team

A customer discusses a transaction with an adviser in a bank consultation area

In summary

  • Arkéa issued two statements on November 4 following fraudulent transactions.
  • The bank separates its own account from customer holdings and denies entry through Fortuneo.
  • Check a delayed transfer with the bank before submitting another payment order.

Explore next

Soclyde resources

Article contents

Crédit Mutuel Arkéa confirmed on November 4, 2026 that an attack had enabled fraudulent transactions, prompting a temporary suspension of some operations. A second statement identified a supplier platform as the route of access. The bank says customer holdings are unaffected. Small businesses should check delayed transfers while treating unexpected requests to resolve them with care.

The bank’s own account is distinct

Arkéa separates the funds in its own account from customer accounts. It also denies that the entry point was Fortuneo. This clarification, published after the first statement, matters when reading early coverage. The incident does not establish that all Fortuneo customers suffered fraudulent debits.

The financial impact is still being assessed

Le Monde contributes reporting on banking controls and money movements, although parts of its initial account differ from Arkéa’s subsequent clarification. The bank validates the order of magnitude of the €118 million figure reported in the press without confirming that precise amount. Recovery work continues. The figure should therefore not be treated as a final net loss in a headline or a cash-management decision.

Check the original instruction before repeating it

Selectra examines the difference between a delayed transfer and a payment that must be submitted again. Freelancers awaiting payment should contact their bank and client through established channels and ask for the original transaction’s status and reference. A small business paying a supplier should check the existing order before requesting a new approval. This helps keep processing delays separate from new payment obligations.

Watch for false security calls

Arkéa warns of possible follow-on phishing. Knowing about the bank’s incident does not authenticate a caller. Do not disclose passwords or codes received by text message. If a message asks you to change a beneficiary or make a test transfer, end the exchange and call your adviser using a known number. These precautions do not establish that customer data was leaked in this incident.

Being able to find the correct banking login helps a small team avoid asking for credentials in a rushed conversation. Soclyde keeps credentials in an encrypted vault on the user’s devices. Payment approval and beneficiary checks still take place in the bank, under the business’s own procedures. The vault does not supervise Arkéa’s transactions or the supplier’s access.

Takeaway

Read Arkéa’s two statements together: fraud involving its own account, resumption of operations and vigilance over unexpected messages. To organise business credentials without scattered copies, contact Soclyde.

Frequently asked questions

Were customer accounts used for the fraud?

Arkéa says the attackers used its own account, rather than accounts belonging to customers of its federations or subsidiaries.

Is the reported €118 million loss final?

No. The bank validates the order of magnitude without confirming the precise figure. Some funds were blocked and assessment continues.

Should a delayed transfer be sent again?

Ask the bank to establish the status of the original order first. Delay does not establish failure, and repeating it may create a duplicate payment.

References

Sources and references

Need advice?

Design your password strategy with Soclyde

Schedule a dedicated walkthrough with the team to see how local-first security adapts to your stack.

Talk with us

Keep reading