Business

Indonesian Banks on 24-Hour Cyber Alert: What Non-Bank Companies Should Do This Week

November 13, 2026 · 5 min read · Etzal Group Team

On 9 November 2026 Indonesia's Financial Services Authority (Otoritas Jasa Keuangan, or OJK) said it had written to bank boards asking them to be on alert for cyberattacks and to monitor their systems 24 hours a day. OJK and Bank Indonesia, the central bank, also activated a Cyber Incident Response Team (Tim Tanggap Insiden Siber, or TTIS) for the banking sector, as reported by Katadata and Republika the same day.

The letter went to banks, not to your company. But any business that pays suppliers, salaries and taxes through online banking or a host-to-host connection sits at the other end of the same systems. This article summarises what was reported, then offers a checklist for this week.

What was reported

  • Katadata, 9 November 2026: Dian Ediana Rae, OJK's Chief Executive of Banking Supervision, said OJK had written to bank boards several times, most recently the week before. OJK's IT supervisors are coordinating with the IT teams of all banks, and conditions were described as "so far aman", meaning safe so far.
  • Republika, 9 November 2026: banks were asked to monitor systems around the clock, watch for anomalies, and where necessary pause transactions for verification.
  • Katadata: Coordinating Minister for Political and Security Affairs Dudung Abdurachman told a press conference on 9 November 2026 that a meeting with the National Cyber and Crypto Agency (BSSN) and banks had discussed how far the hackers' impact reached, and that banks were not the only targets.
  • Katadata, 10 November 2026: Oleh Soleh, a member of parliament's Commission I, said the commission would summon BSSN to explain the state of cyber threats and the readiness of critical infrastructure protection.

No Indonesian bank is reported as breached in the sources we read, and no perpetrator is named.

The triggers abroad, and two versions of one story

The Indonesia bank cyberattack alert was prompted in part by two events overseas.

The first is the breach at French bank Credit Mutuel Arkea. Here two sources differ:

KatadataRepublika, citing Reuters
Amount100 million euros, about Rp2 trillionAbout 100 million euros
Whose moneyRefers to lost savingsFunds from the bank's own accounts, not customer accounts
Other detailOccurred on Wednesday 4 NovemberHackers used the bank's accounts for fraudulent transactions to other banks; some transactions were paused, delaying a number of transfers

We note both and do not choose between them. For a corporate reader the relevant detail is the last one: when a bank holds transactions to contain an incident, innocent customers' transfers are delayed as well.

The second: Katadata, citing Yonhap, reported that 437,000 customer records leaked from South Korean financial institutions including Shinhan Bank, KB Kookmin Bank, Hana Bank and Woori Bank.

What it means for non-bank companies

There are two practical consequences.

First, legitimate transactions may be held. Banks told to watch for anomalies will more often stop payments that look unusual: a new beneficiary, a large amount, an odd hour. That is protection, but for a finance team it means a payment scheduled close to a deadline can arrive late.

Second, fraudsters use the mood. When attack news is everywhere, a message claiming to come from the bank and asking you to re-verify an account sounds plausible. This is our assessment, not something the sources report, but the pattern is familiar enough to guard against.

A checklist for this week

Everything below is our practical advice.

Online banking access

  • Export the list of active users from each bank portal. Remove accounts of staff who have moved or left.
  • Make sure each user has their own token or authentication device. Shared tokens erase the trail of who did what.
  • Review limits per user and per day. Limits set years ago are often far above what is needed.

Dual approval

  • Payments above a set threshold should be created by one person and approved by another. Check that the bank's system enforces this, not only the written procedure.
  • Treat new beneficiaries and changes to supplier bank details as strictly as payments. Confirm a change of account through a phone number you already hold, not the one in the email requesting it.

Host-to-host and API connections

  • Record where credentials and certificates are stored, who can read them, and when they were last rotated.
  • Confirm that the IP addresses the bank allows still match your current servers.
  • Check that request and response logs are kept long enough to reconstruct a day of transactions.

Emergency contacts and held transactions

  • Keep each bank's relationship manager and emergency line, verified now, somewhere you can reach when email is down.
  • Agree who in the company is authorised to answer a bank's verification questions, and who covers when that person is away.
  • For important payments this week and towards month end, move one business day earlier. Have supporting documents such as invoices and purchase orders ready so verification takes one call.
  • If the bank calls you, hang up and call back on the number you have verified. A real bank will not object.

The trade-offs

Every layer of control slows payments down. Dual approval on every transaction will overwhelm the finance team and, in the end, lead to approvals nobody reads. Tiered thresholds are more useful: routine payments to established beneficiaries move quickly, while new beneficiaries and large amounts get the full check.

The same applies to banking with more than one bank. Keeping two banks active adds administrative cost, but gives you a way out when one bank holds transactions or pauses a service.

If your payment system connects to banks directly from an ERP and you want to review how credentials and approvals are handled inside it, Etzal Group's enterprise software team can help.

The situation is still developing. Check the latest official announcements from OJK, Bank Indonesia and your own bank before changing payment procedures.

Sources

Frequently asked questions

Has any Indonesian bank been breached?

The sources we read report no breach of an Indonesian bank. A senior regulator said on 9 November 2026 that conditions were "so far" safe.

Why might a company payment be held?

According to Republika, banks were asked to watch for anomalies and, where needed, pause transactions for verification. Keep bank contacts and supporting documents ready.

What should a non-bank company check first?

The list of online banking users, dual approval of payments, host-to-host credentials, and verified emergency contact numbers at each bank.

Author

Etzal Group Team

Etzal Group Team, helping businesses grow with technology. Contact us.

Related service

Free consultation

Not sure where to start? We will map the right system for your business, free.