Kluang's LED Hack Is a Signage Network Problem
Eight council LED screens in Kluang showed obscene clips on 29 October. The intrusion is the easy part; the shared control plane and default logins are not.

Eight LED screens belonging to the Kluang Municipal Council (MPK) showed obscene images and video on the night of 29 October. By the next afternoon the council had cut power to every screen under its jurisdiction, lodged a police report, and promised a joint investigation with the vendor that supplies the displays.
That is the news. The narrower question for anyone running public signage in Malaysia: how does one intrusion reach eight screens at three locations, and what would have stopped it at one?
What the record actually says
The Star reported that Kluang OCPD Asst Comm Bahrin Mohd Noh confirmed eight council screens were allegedly hacked. The complainant was a 42-year-old local man who lodged a report on Friday, 30 October; his staff had told him about the incident the day before. He then received WhatsApp messages containing screenshots and video, contacted the supplier to verify what he was seeing, and cut the power to the affected displays. The locations named in reporting are Dataran Tasik Kluang, Taman Intan in Kluang town, and the road towards Kahang.
MPK's statement is short and worth reading for what it does not say. It confirms a police report and adds: "A comprehensive investigation is being undertaken in collaboration with the screen's vendor to identify the main cause of the incident. This is in addition to implementing remedial measures and strengthening the system's security."
Johor housing and local government committee chairman Datuk Mohd Jafni Md Shukor told Malay Mail that "the council has taken proactive measures by shutting down all LED screens under its jurisdiction". Police are investigating under section 4(1) of the Computer Crimes Act 1997 and section 292 of the Penal Code, and asked for no speculation.
Lowyat.NET noted there is no indication that AI was involved, and nothing in the public record points to a novel technique. This looks like the oldest problem in networked signage.
Eight screens is a topology clue
An LED wall is not a television. It is a sending card and a chain of receiving cards, fed by a media player, configured from a control PC or a cloud content-management system. Someone has to publish to it, and that someone needs an account, an address, and a path in.
When eight screens across three locations change together, the cheapest explanation is that they share a management plane: one content system, one player fleet, one credential, one reachable endpoint. That is a hypothesis, not a finding: the same effect could come from eight logins sharing a reused password. Police have not published a cause.
The hypothesis is the one worth designing against, because it scales: a single vendor account with publish rights is a single point of failure for every screen it can address.
There is a second clue in the police account: the complainant "contacted the supplier for verification". In this market the council frequently does not own the stack it operates; the vendor does — the same split that decides who runs the 5G inside Bukit Chagar. That is the supply-chain story in miniature, and it is why MPK's statement puts the vendor inside the investigation rather than beside it.
The failure mode is documented and boring
This class of system fails in documented ways. In June, CISA published an advisory on Daktronics VFC-DMP-5000, DMP-5000 and DMP-8000 controllers — hardware behind a large share of the world's LED billboards and highway signs. Three issues: an unauthenticated path traversal that enumerates filesystem paths, an authenticated arbitrary file upload, and default administrator credentials.
CISA's summary was blunt: "Successful exploitation of these vulnerabilities could provide an unauthenticated user with complete root-level access and control of the system."
The researcher who found them, Thomas Jou, told SecurityWeek what made the default credential issue worse than it sounds. "The devices also shipped with default administrator credentials that weren't required to be changed, and field testing showed a majority of internet-exposed units were still using them."
Not "some". A majority of the units he could reach from the internet were still on the vendor's shipped login. The patch existed — reported in January 2026, firmware ready around March — and the population that mattered had not applied it, the same gap that left MikroTik routers exposed after their fix shipped.
Daktronics told SecurityWeek that it had notified impacted customers and that "no active exploits of the vulnerabilities have been reported to Daktronics". That is a vendor speaking about its own install base, not about any specific council in Johor.
The charge tells you the theory, not the cause
Section 4(1) of the Computer Crimes Act 1997 is not the simple unauthorised-access offence. That is section 3, which carries up to RM50,000 or five years, or both. Section 4(1) requires the access to be committed with intent to commit, or facilitate, an offence involving fraud or dishonesty, or one causing injury as defined in the Penal Code. On conviction it carries up to RM150,000 or ten years, or both.
Pairing it with section 292 of the Penal Code — displaying obscene material, maximum three years and a fine — tells you the prosecution theory: access plus intent to facilitate the obscenity offence. It is a sensible pairing, and a reminder that the charge is a legal construct. It says nothing about whether the entry point was a reused password, an exposed remote-desktop port, a vendor account, or a content-system API.
A third offence may matter more: section 5, unauthorised modification of a computer's contents, carries up to RM100,000 or seven years. Changing what a public screen displays is, plainly, modifying a computer's contents, and section 5 is where such cases often land when intent is hard to prove. Either way, the charge sheet is not a root-cause report: the legal theory and the technical cause are separate workstreams, and only one produces a fix.
The watermark is a claim, not evidence
Malay Mail reported that the video carried "a watermark that credited the Leakers.Gov cyber hacking group". That is worth stating precisely: a watermark is an assertion by whoever posted the clip. It is not authentication, it is not attribution, and group branding is often borrowed.
The Facebook reel has since been taken down, and police asked the public not to speculate. Treat the name as unverified until someone with access to the systems substantiates it.
Six gates that would have narrowed the blast radius
You cannot audit a council you do not work for. You can audit your own inventory, and the checks are not exotic. The script below scores each screen against six gates that map to the failures above: management plane reachability, shipped credentials, firmware support, upload restrictions, network separation, and raw port-forwarding.
#!/usr/bin/env python3
"""Score digital-signage endpoints against six exposure gates.
Read-only: takes an inventory of screens and prints a verdict per screen.
"""
from dataclasses import dataclass
@dataclass
class Screen:
name: str
mgmt_exposed: bool = False
default_creds: bool = False
firmware_eol: bool = False
unrestricted_upload: bool = False
shared_vlan: bool = False
port_forwarded: bool = False
def gates(self) -> dict[str, bool]:
return {
"mgmt not internet-facing": not self.mgmt_exposed,
"vendor creds rotated": not self.default_creds,
"firmware supported": not self.firmware_eol,
"content upload restricted": not self.unrestricted_upload,
"signage on its own VLAN": not self.shared_vlan,
"no raw port-forward": not self.port_forwarded,
}
def failures(self) -> list[str]:
return [name for name, ok in self.gates().items() if not ok]
def audit(screens: list[Screen]) -> None:
width = max(len(s.name) for s in screens) + 2
print(f"{'screen'.ljust(width)}{'score':>7} failures")
print("-" * (width + 9))
for s in screens:
failed = s.failures()
print(f"{s.name.ljust(width)}{f'{6 - len(failed)}/6':>7} {', '.join(failed) or 'none'}")
blocked = sum(1 for s in screens if s.failures())
print(f"\n{blocked}/{len(screens)} screen(s) need work before the next campaign.")
if __name__ == "__main__":
audit([
Screen("site-a-main-road", mgmt_exposed=True, default_creds=True,
firmware_eol=True, unrestricted_upload=True, shared_vlan=True),
Screen("site-b-town-hall", default_creds=True, unrestricted_upload=True,
shared_vlan=True),
Screen("site-c-junction", port_forwarded=True, shared_vlan=True),
Screen("site-d-library"),
])
Run against four illustrative records, with the names invented:
screen score failures
---------------------------
site-a-main-road 1/6 mgmt not internet-facing, vendor creds rotated, firmware supported, content upload restricted, signage on its own VLAN
site-b-town-hall 3/6 vendor creds rotated, content upload restricted, signage on its own VLAN
site-c-junction 4/6 signage on its own VLAN, no raw port-forward
site-d-library 6/6 none
3/4 screen(s) need work before the next campaign.
Most real inventories score 3/6 and feel fine, because the two gates that actually stop a remote attacker — internet reachability and shipped credentials — are the ones nobody looks at.
What to do this week
- Inventory the screens, then the accounts. Every screen, player, content system and login that can publish. The number you want is how many accounts can put an image on a public wall.
- Remove the management plane from the internet. VPN or an allowlisted jump host, not a port-forward. Vendor remote access needs its own account, its own log, and an expiry date.
- Rotate every shipped credential, per site. Shared vendor passwords turn one compromised account into a fleet. Where the platform supports it, add MFA and short sessions.
- Separate the signage VLAN. No flat path to council servers, no path to the finance network, and an egress allowlist so a compromised player cannot call out wherever it likes.
- Restrict what can be published. Allowlisted file types, signed or hashed content, a publish window, and a second pair of eyes for anything outside the scheduled playlist.
- Test the kill switch. MPK cut power: a physical response to a network problem. Know the one action that stops playback across the fleet, and rehearse it.
- Put it in the contract. The vendor should owe you notification, log retention, and cooperation in an investigation. A clause makes that cooperation an obligation.
What to watch
Whether police or the vendor name a technical cause: a credential, an exposed service, or a content-system flaw. Whether other councils run the same audit before their next campaign. Whether a section 5 charge follows. And whether the watermark's group name is ever substantiated by something other than the watermark.
The screens are the part everyone saw. The management plane is the part that decided how many of them changed at once.
Sources
- The Star: Police probing obscene content on Kluang LED screens
- Malay Mail: Kluang council shuts down LED screens after obscene video appears in suspected hack
- Lowyat.NET: Kluang LED billboards hacked to display adult content, authorities investigating
- SecurityWeek: New Controller Flaws Expose Highway Signs and Billboards to Remote Hacking
- CISA: Daktronics Digital Media Player
- Attorney General's Chambers: Computer Crimes Act 1997 (Act 563)
- MITRE ATT&CK: T1021.005 Remote Services: VNC
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 · 31 OCT 2026
Source details and access dates
- Police probing obscene content on Kluang LED screensThe Star · accessed 31 OCT 2026
- Kluang council shuts down LED screens after obscene video appears in suspected hackMalay Mail · accessed 31 OCT 2026
- Kluang LED billboards hacked to display adult content, authorities investigatingLowyat.NET · accessed 31 OCT 2026
- New Controller Flaws Expose Highway Signs and Billboards to Remote HackingSecurityWeek · accessed 31 OCT 2026
- Daktronics Digital Media PlayerCISA · accessed 31 OCT 2026
- Computer Crimes Act 1997 (Act 563)Attorney General's Chambers · accessed 31 OCT 2026
- T1021.005 Remote Services: VNCMITRE ATT&CK · accessed 31 OCT 2026
related

Google's TV box takedown leaves 1.3M backdoors in place
Google severed a 1.3 million-device TV box botnet, but the x.cpe backdoor stays on the hardware and owners cannot remove it.

The 5G at Bukit Chagar Belongs to MRT Corp
U Mobile and MRT Corp signed an MoU to put 4G and 5G inside the Bukit Chagar border hall. MRT Corp owns the indoor system, and that changes the deal.

Inside YTL and JLand's Gigawatt Data Center Plan
YTL Power and JLand Group are building a gigawatt-scale data center campus in Sedenak, Johor. Here is what the deal actually covers and why it matters.
join the feed
one fresh insight per week. no spam, ever.
weekly digest. unsubscribe anytime.