Bank Rakyat's Defaced Pages Said 'Security Assessment'. The $2,000 Listing Was Already Up.
Bank Rakyat's pages were defaced with a note titled 'Security Assessment'. An hour before, the same handle was selling server access for $2,000.

On the night of Friday 6 November 2026, pages on Bank Rakyat's own domains were replaced with a note. The title was "Security Assessment – Proof of Concept". The body read: "Marlanwg is here. We have successfully accessed the internal infrastructure and retrieved a sample of your data to verify the extent of the breach."
Read only that note, and you could file the whole thing as a test. The rest of the night does not support that reading.
What was actually on the page
The defaced pages sat on Bank Rakyat's legitimate domains, including pages tied to the iRakyat internet-banking login, across more than one domain name. Lowyat.NET captured one at 10.45pm.
The note asked the bank's officials and security teams to make contact on Session, a metadata-minimising encrypted messenger, "to discuss the security assessment findings, remediation steps, or to request the secure deletion of the extracted data". It carried a Session ID for the negotiation.
That is the whole artefact: a claim of internal access, a claim of extracted data, and a private channel to discuss deleting it.
The hour before the defacement
At 13:43 UTC on 6 November — 9.43pm in Kuala Lumpur, roughly an hour before the defacement was captured — a listing appeared on DarkForums offering access to a bankrakyat.com.my production server, with database extraction capability, for USD 2,000. The seller claimed unauthenticated remote code execution and root. The proof was a redacted screenshot, with no data samples and no record counts. Darkwiser and Kalir both logged the listing and both mark it unverified.
Neither artefact proves the other. But a proof of concept that is simultaneously for sale, priced, and awaiting a buyer is not a proof of concept. It is an offer.
What the bank said, and what it did not
Shortly before midnight, Bank Rakyat posted an advisory on its social media channels. It said the corporate website was unavailable and told customers to use iRakyat, BRICK, QR2E and i-bizRAKYAT instead, and apologised for the inconvenience — as carried by Bernama and Utusan Malaysia.
Access to most of the bank's websites was disabled. The bank did not confirm the incident as a cyberattack, and has not said publicly whether customer data was affected. By 3.50am on 7 November, Google was still serving cached results from the defaced pages. By 8am, the corporate portal was still down, with no cause or restoration timeline given.
So the confirmed record is narrow and clear: pages on the bank's own sites were altered, and the bank took its sites offline. Everything about depth of access is still a claim.
What is confirmed, and what is not
| Claim | Status | Basis |
|---|---|---|
| Pages on Bank Rakyat domains were altered | Confirmed | Captured at 22:45 MYT (Lowyat.NET); the bank's own advisory |
| The bank took most of its sites offline | Confirmed | Bank statement carried by Bernama; Lowyat.NET |
| The page carried a note titled "Security Assessment – Proof of Concept" | Confirmed | Captured page, still indexed at the time of writing |
| An access listing at USD 2,000 was up before it | Reported | Darkwiser and Kalir both logged it, both mark it unverified |
| Internal infrastructure was accessed | Claimed | The actor's note only; no forensic report published |
| Customer data was extracted | Claimed | The actor's note only; no sample and no record count published |
| The same handle hit Malaysian Customs and Indonesia's DJP | Reported | Lowyat.NET, VECERT, S2W — handle similarity, not attribution |
| A payment was demanded from the bank | Unknown | No demand has been published |
The gap between the top three rows and the bottom five is the whole story.
What a defaced page does and does not prove
A public-facing page can be altered through a vulnerable CMS plugin, a stolen admin credential, a compromised deployment pipeline or a hijacked DNS record. None of those paths requires root on the server, and none of them touches core banking. These are hypotheses, not findings — the bank has not described the method.
So the honest chain runs like this: defacement confirmed → the web tier was reachable and writable, method unknown → deeper access claimed, unproven. Collapsing the third step into the first is the mistake this incident invites, and it is the same mistake the actor's own wording is designed to encourage.
Why "assessment" is the wrong frame
Three details sit badly with the word assessment:
- There was a price. A security assessment does not come with a USD 2,000 access listing on a criminal forum.
- There was a private channel. Assessments are delivered in reports, to the party that commissioned them. This one arrived with a Session ID and an instruction to negotiate.
- There was a deletion offer. "Request the secure deletion of the extracted data" is a payment term, not a finding.
And the target selection matters. An assessment that replaces the login page of a bank's internet-banking service is not testing a boundary — it is standing in front of customers. What the record shows is extortion-shaped, which is not the same as extortion proven: a priced access listing, a claim of extracted data, and a private channel opened to discuss deletion. What it does not show is a demand — the USD 2,000 was a sale price to forum buyers, and no payment request to the bank has been published. Call it a possible extortion attempt until someone produces the ask.
None of this means the deeper claim is true. Threat-intelligence trackers keep the intrusion claim at alleged and unconfirmed, and the bank has not validated it. Two things can be true at once: the defacement is confirmed, the intrusion is not.
The same handle, three weeks, three targets
This is not a first appearance.
- October 2026 — the same handle offered webshell access to production MySQL databases belonging to the Royal Malaysian Customs Department, advertised as a 0-day on DarkForums.
- 31 October 2026 — the same handle advertised an unauthenticated RCE 0-day against Indonesia's Directorate General of Taxes (DJP) Coretax system, and claimed to have pulled 10,490,677 tax-return submission records tied to roughly 3.4 million taxpayers. The DJP denied a leak and said the circulating data showed irregularities.
- 6 November 2026 — Bank Rakyat.
Threat-intelligence trackers put this actor's first appearance at 8 August 2026, with Colombia, Indonesia and the USA in its target list. The playbook has not changed across the three: pick a public-facing target, claim deep access, publish a fragment, open a private channel, ask for money.
One thing to get right: which Bank Rakyat
This matters more than it looks. Bank Kerjasama Rakyat Malaysia Berhad (Bank Rakyat) is not Bank Rakyat Indonesia (BRI). They are separate institutions in separate countries, and a large share of search results about a "Bank Rakyat breach" are about BRI — including a 2024 ransomware listing against bri.co.id.
There is also no public source that geolocates the Bank Rakyat defacement to an Indonesian IP address. What is documented is that this actor ran its most recent major campaign against an Indonesian government system, and that Indonesia appears in its target list. That is the actor's history, not an attribution of this incident — and the difference is worth keeping, because "the IP is Indonesian" is the kind of detail that gets repeated until it becomes fact without ever having been sourced.
The compliance backdrop
Bank Rakyat is not arriving at this with a clean slate.
On 20 January 2026, Bank Negara Malaysia imposed an RM1,000,000 administrative monetary penalty on the bank for failing to implement robust cybersecurity standards under the RMiT policy document and to safeguard customer information under the MCIPD policy document. BNM's finding was specific: the breaches followed "a cybersecurity incident in which an external threat actor gained unauthorised access to its IT infrastructure", and were attributed to "inadequate cybersecurity controls and incident response". The bank paid on 26 January 2026.
That penalty came on top of an earlier RM2.85 million for repeated service disruptions — roughly RM3.85 million in seven months.
What to do if you bank with them
The practical advice is boring and it works:
- Do not log in from search results or shared links. Defaced pages were still indexed hours after the sites came down. Type the address, or open the app.
- Check the host and the certificate before you type a password. A defaced page can live on a real domain, so a valid certificate only proves the TLS handshake — not that the server behind it is uncompromised. A wrong issuer, though, is a stop sign.
# Confirm you are talking to the real Bank Rakyat portal, not a lookalike.
# 1) what does the name resolve to? 2) who issued the certificate?
dig +short www.bankrakyat.com.my
openssl s_client -connect www.bankrakyat.com.my:443 \
-servername www.bankrakyat.com.my </dev/null 2>/dev/null \
| openssl x509 -noout -subject -issuer -dates
- Treat every message about this incident as phishing until proven otherwise. Breach news is prime cover for "we are securing your account" calls, SMS and emails. No bank will ask you to move money to a "safe account".
- Check your transactions and report anything you do not recognise immediately.
- Escalate properly if something goes wrong. The bank's complaints unit first; if that stalls, BNMLINK; for direct financial loss, the Financial Markets Ombudsman Service.
The uncomfortable part
A defacement is loud and an intrusion is quiet. The visible damage is a replaced page; the question that actually matters is whether anything left the building, and only the bank can answer it.
"Security assessment" is a costume, not a category. The correct default, until Bank Rakyat says otherwise in writing, is to treat this as an intrusion that happened to announce itself — assume compromise while you investigate, but do not report one you cannot evidence. The first is a defensive posture. The second is a finding, and findings need forensics.
Sources
- Lowyat.NET: Bank Rakyat Takes Down Sites After Suspected Cyber Attack
- Pokde.Net: Bank Rakyat Under Suspected Cyberattack By Threat Actor "Marlanwg", Website Briefly Defaced
- RTM / Bernama: Laman web Bank Rakyat, terganggu
- Utusan Malaysia: Laman web korporat Bank Rakyat tidak dapat diakses
- Darkwiser Threat Intel: Bank Rakyat (bankrakyat.com.my) Database Credentials Exposed
- Kalir Brief: Venta de acceso al servidor del banco malasio Bank Rakyat
- Bank Negara Malaysia: Imposition of Administrative Monetary Penalty on Bank Kerjasama Rakyat Malaysia Berhad
- iNews.id: Heboh! Bank di Malaysia Diduga Kena Serangan Siber
- Imago: Hacker sells 0-day exploit and leaks 10 million tax records from Indonesia
- CNBC Indonesia: Ditjen Pajak Bantah Data Coretax Bocor
author
Editor & Operator
MrDodgerX (MrDodgerX) is an enterprise geospatial systems engineer in Malaysia and the editor behind hejes.my. He runs the briefing pipeline, curates and edits every draft, verifies each factual claim against primary sources, and presses the publish button — nothing ships without his review. He writes about AI, security and Malaysia's tech scene from a builder's perspective. Professional profile and code: the links below.
sources
fact-check verified · 07 NOV 2026
Source details and access dates
- Bank Rakyat Takes Down Sites After Suspected Cyber AttackLowyat.NET · accessed 07 NOV 2026
- Bank Rakyat Under Suspected Cyberattack By Threat Actor "Marlanwg", Website Briefly DefacedPokde.Net · accessed 07 NOV 2026
- Laman web Bank Rakyat, tergangguRTM / Bernama · accessed 07 NOV 2026
- Laman web korporat Bank Rakyat tidak dapat diaksesUtusan Malaysia · accessed 07 NOV 2026
- Bank Rakyat (bankrakyat.com.my) Database Credentials ExposedDarkwiser Threat Intel · accessed 07 NOV 2026
- Venta de acceso al servidor del banco malasio Bank RakyatKalir Brief · accessed 07 NOV 2026
- Imposition of Administrative Monetary Penalty on Bank Kerjasama Rakyat Malaysia BerhadBank Negara Malaysia · accessed 07 NOV 2026
- Heboh! Bank di Malaysia Diduga Kena Serangan SiberiNews.id · accessed 07 NOV 2026
- Hacker sells 0-day exploit and leaks 10 million tax records from IndonesiaImago · accessed 07 NOV 2026
- Ditjen Pajak Bantah Data Coretax BocorCNBC Indonesia · accessed 07 NOV 2026
related

CTOS Breach: When the Credit Agency Asks You to Reset Your Password
CTOS confirmed a limited subset of consumer data was accessed; password-reset notices are now reaching account holders. Here is what it means.

Tabung Haji Cyberattack: Depositors' Savings Safe, Services Restored
Tabung Haji suspended all services after a cyberattack, restored them within days and says savings are safe. What depositors should know and check.

Misi Rakyat Now Acknowledges Cyberattack: What Changed After the Data Leak Analysis?
Misi Rakyat says it was hit by a malicious cyberattack. What the Sep 9 statement confirms, what it leaves open, and how it compares to the Sep 8 leak analysis.
join the feed
one fresh insight per week. no spam, ever.
weekly digest. unsubscribe anytime.