On 16 November 2026, a ransomware group calling itself Panzer listed a bank in Indonesia on its leak site. The claim: roughly 296 GB of data taken, including fund transfer records, credit reports, confidential documents, and internal reports. The news spread after the X account @DailyDarkWeb posted it, and CNBC Indonesia reported it on 18 November 2026.
When that reporting came out, the data had not been published or verified, and the bank had not responded. That is why we are not treating this as a confirmed breach. That question belongs to the investigation, and it has no answer yet.

Why the case is still worth studying
One part of this story does not depend on whether the claim is true: how Panzer runs its business. According to the profile CNBC Indonesia published, Panzer first appeared on 5 August 2026 and, within that same month, had built a ransomware-as-a-service operation. Prospective members apply through the Tox app and are vetted first. Proceeds are split 80% to the affiliate and 20% to the operator. The profile also cites claims of 16 to 19 victims across 11 countries in under a month.

A model like this changes how the threat should be read. The attacker is not one gang with one rare skill. An operator supplies the tooling, and affiliates go looking for a way in. Our view is that affiliates paid from the proceeds will try the easiest door first, not the cleverest one. That is our opinion, not a finding from the sources above. But the direction of the analyst's suspicions in the same reporting points the same way.
The three doors suspected
An analyst at Security Arsenal, cited by CNBC Indonesia, listed several possible routes in: exploitation of VPN devices and gateways, brute-force attacks on RDP, phishing through macro-laden documents, and misuse of Remote Monitoring and Management (RMM) tools. Confidence is medium to low, and no verified malware sample or file hash yet pins the activity on Panzer. Treat this as a hypothesis, not a conclusion.
Three of those four routes share one trait: they are all remote access, and a small office has them too.

- VPN and gateways. The device itself can carry a flaw. The question for the owner: who is responsible for updating its firmware, and when was that last done?
- RDP. Passwords guessed over and over. The question: is RDP exposed directly to the internet, and is two-step verification on?
- Remote tools (RMM). Software installed by a vendor or the IT team to support remote work can be misused by outsiders. The question: which tools are actually approved, and who holds the access?
The honest answer may well be this: the access was set up by a vendor or an IT employee who is no longer around, and nobody wrote it down. If the answer is "we don't know", that is the door.
Signs worth watching
The same profile lists indicators to watch for: deleted Windows backup copies, unauthorised use of RMM tools, unusually large archive files, and VPN logins from unusual locations. None of the four needs expensive tooling to check. They need a person who has been assigned to look.
In our view, remote access is the easiest door to forget. It is usually installed once for an urgent reason, such as a vendor needing to get in to fix something, and never reviewed again. As long as it does not disturb daily work, nobody feels it is their job.
The consequence only shows up when something happens. The first question after ransomware gets in is not "who did it" but "since when has this door been open, and through whose account?" Without an access list and login records, you have no answer for customers, partners, or your own team.
What can be done this week
No step guarantees safety from ransomware. But this sequence closes the doors most often left open:
- Make one list of every VPN, RDP, and remote-tool account, with the owner's name.
- Remove accounts of people who have left and tools nobody uses.
- Close any RDP exposed to the internet unless there is a strong reason.
- Turn on two-step verification for VPN and RDP.
- Set alerts for logins from unusual locations or hours.

If a vendor handles this work, ask three questions: who holds the list of remote access for our office, when was that list last checked, and do VPN and RDP logins already use two-step verification? A vendor that answers with names, dates, and proof of the settings is doing the job properly. A vendor that says "it's safe, don't worry" has not answered anything.
Whether the bank's data really leaked, the investigation will tell us. Whether your office's remote access is still open to people who should not have it, you can find out this week. If you would like help mapping it, reach us through xetup.id or bisnis@xetup.id.
