Skip to main content
Indotek Digital Nusantara

Enterprise IT

Are Indonesian Banks Under Cyber Attack? What the Viral Figures Show

Screenshots of a FortiGuard Labs dashboard showing about 350,600 attack activities aimed at Indonesia, mostly at banking, spread on social media on 7 and 8 November 2026. The reports describe detections, not breaches, and no authority had confirmed damage. What is known, how to read the numbers and what to do.

A row of server racks with blinking lights inside a data centre server room
Server room at the data centre of BalticServers, photographed on 17 March 2013. The picture is illustrative; no institution in this article is shown. Photo: BalticServers.com, CC BY-SA 3.0 (opens in a new tab)

Are Indonesian banks under cyber attack? Over the weekend of 7 and 8 November 2026, screenshots of a FortiGuard Labs threat dashboard spread on social media, showing about 350,600 attack activities aimed at Indonesia, with banking, finance and insurance the largest target. By Sunday, another post put the figure at 844,000 in 24 hours. What the reports we read actually confirm is narrower: the numbers are detections of attempted attacks, not confirmed intrusions, and as of 8 November no Indonesian authority or bank had reported damage to banking systems, customer data or funds linked to the wave. For banks, their suppliers and any company running online services, the episode shows how quickly an unverified number becomes a public question.

What the viral figures say

Industry.co.id reported on 7 November that the FortiGuard Labs dashboard, as of that day, showed about 350,600 attack activities targeting Indonesia. Its table gave about 214,000 for banking, finance and insurance, about 79,000 for government and critical infrastructure, and about 57,600 for other sectors, a remainder the outlet calculated itself. FortiGuard Labs is the threat intelligence unit of the security company Fortinet.

  • The figures moved. Industry.co.id also saw screenshots showing about 206,000 for banking and 73,000 for government, which it put down to the dashboard updating continuously.
  • AFU.id, on 8 November, found the same 350,600 total shared by accounts on X, alongside a post claiming 212,000 attacks on banking and finance in 24 hours and another claiming 723,000 attacks on Indonesia.
  • Bacakoran, also on 8 November, reported 844,000 attacks in 24 hours, including 255,000 against banking, 184,000 against healthcare and 112,000 against government, based on a post on X with a video of the FortiGuard map.

None of the reports we read cites a statement from Fortinet. Industry.co.id wrote that, at the time of writing, neither the national cyber agency BSSN nor Fortinet had issued an official statement confirming the figure.

What has been confirmed, and what has not

The reports agree that the numbers describe detected threat activity, not successful break-ins. AFU.id and Batavia Pos both wrote that BSSN, the Financial Services Authority (OJK) and Bank Indonesia had not announced any disruption to banking systems or leak of customer data linked to the figures, and AFU.id found no Indonesian bank service disruption tied to the wave. Batavia Pos reported that, as of Sunday 8 November, there was still no official BSSN statement on it.

Coverage of the authorities' response is uneven. Bacakoran wrote that BSSN and bank IT teams were monitoring the situation, but quoted no official. Some other outlets went further and attributed statements to BSSN and OJK without naming a spokesperson or a document. We could not confirm those claims and have left them out.

The regional backdrop

The Indonesian posts circulated alongside news from other countries, which helps explain the alarm. None of the reports we read shows that these events were part of one co-ordinated campaign.

  • Malaysia: according to AFU.id, the website of Bank Rakyat was defaced on the night of 6 November, and a group calling itself MARLANWG claimed responsibility. Malaysia's communications minister, Fahmi Fadzil, said there had been no data theft or disruption to online banking, and that the site targeted was managed by a third party.
  • France: AFU.id reported that Crédit Mutuel Arkéa suffered a cyber attack in early November in which corporate funds were moved. Media estimates of the loss varied; in a statement quoted by Reuters, the bank said customer assets were not affected and that it was too early to give an exact figure.
  • Japan: AFU.id reported that 128 Shinkin banks in western Japan had service disruptions on 6 November, which Shinkin Central Bank attributed to a communications equipment failure, not a cyber attack.
  • Mobile banking: AFU.id also noted that on 15 October an Android malware strain called Hirudo was reported to target eight mobile banking apps from seven Indonesian banks.

How to read a threat-map number

This section is our analysis.

  • A detection is not a breach. Security sensors count attempts they see and block. A high count can simply mean defences are working; on its own it says nothing about whether any system was entered.
  • A live map is a snapshot. The same dashboard was reported at 350,600 on one day and, according to a social media post, 844,000 the next. Totals depend on when a screenshot was taken and what period it covers.
  • One vendor sees part of the picture. A dashboard reflects what that vendor's own sensors observe. BSSN has acknowledged the limits of any single view: Disway reported in August that Edit Prima, a BSSN director, said the agency's monitoring covered less than 10 per cent of digital activity.
  • Sector rankings need context. Banking tops such lists because it is a valuable target, and that was true before this weekend too.

What banks and other organisations can do now

This section is our analysis, not legal or regulatory advice.

  • Know your own numbers. A security team that can say, from its own logs, what it detected, blocked and investigated this weekend can answer the board and customers without relying on a screenshot.
  • Prepare the public line before it is needed. Viral figures travel faster than official statements, so decide in advance who speaks, what can be said and how quickly.
  • Check internet-facing services first. Public websites, login pages and remote access are where defacement and intrusion attempts land, as the Malaysian case showed.
  • Watch the mobile channel. Reports of malware aimed at Indonesian banking apps make app hardening and fraud monitoring as relevant as perimeter defences.
  • Treat suppliers as part of the attack surface. The Bank Rakyat site that was affected was, according to the Malaysian minister, managed by a third party.

What to watch next

Watch whether BSSN, OJK or Bank Indonesia make a formal statement on the weekend's figures, and whether any Indonesian bank reports an incident linked to them. Watch whether Fortinet explains what its dashboard was counting. And watch for further findings in the French and Malaysian cases, which will show whether the regional activity was connected or simply coincided.

Sources

  1. 350.600 Aktivitas Serangan Siber ke Indonesia, Perbankan Sasaran Utama · Industry.co.id(opens in a new tab)
  2. Fortiguard Labs Deteksi Ratusan Ribu Upaya Serangan Siber ke Perbankan Indonesia, Belum ada Bukti Sistem Ditembus seperti di Prancis · AFU.id(opens in a new tab)
  3. 350.600 Ancaman Siber Sasar Indonesia, Staf IT Bank Kerja Keras · Batavia Pos(opens in a new tab)
  4. 844 Ribu Serangan Siber Target Indonesia dalam 24 Jam, Perbankan Jadi Sasaran Utama · Bacakoran.co(opens in a new tab)
  5. 3,64 Miliar Serangan Siber Mengintai, BSSN Akui 90 Persen Aktivitas Digital Belum Terpantau · Disway.id(opens in a new tab)

This briefing was prepared by the Indotek editorial desk with AI assistance, from the public sources listed above. It is general information, not legal or professional advice.

Cloud & Data

How Indotek can help

The weekend's real question was whether a bank could show, from its own systems, what reached it and what was stopped. Building platforms where that evidence and those defences are designed in is the work Indotek does in cloud and data.

  • Secure by default: we design landing zones, network and identity so that public websites, login pages and remote access start from secure defaults rather than being locked down later.
  • Observability built in: our platform engineering puts infrastructure as code and observability in place, giving a security team its own record of what its platforms saw.
  • Security and residency by design: access, encryption and data-location requirements shape the architecture from the start, particularly for regulated banking workloads.

Let's build what comes next

Whether you are modernising a legacy environment, building an AI-powered product or exploring a new digital business, let's create technology that delivers lasting value.