The Daily Byte
Breaking
Welcome to The Daily Byte — real stories from across Pakistan.
Saturday, 21 November 2026 · Pakistan

The Daily Byte

Stories from Pakistan that deserve to be heard

CyberPower PowerPanel Abuse Hits Domain Controller

By The Daily Byte ·21 Nov 2026 ·4 min read
Rows of server racks with blinking lights inside a modern data centre

Attackers have turned a piece of power-management software into a back door on a Windows domain controller, using its own documented features to run commands with the highest privileges on the system. Security researchers at Symantec disclosed the intrusion on 18 November, warning that no software bug or new exploit was needed for the attack to work.

The software at the centre of the case is CyberPower's PowerPanel Business, which manages uninterruptible power supply units and shuts servers down safely when the power fails. Because that job matters most on critical machines, the software is often installed on hypervisors, database servers, file servers and, in this case, a domain controller, the server that controls logins across a Windows network.

How the UPS software became a back door

PowerPanel Business has three properties that made it attractive to the intruders. It can run a script automatically when it detects a power problem, and administrators configure that by placing a command file in a folder called extcmd. It has a network-facing web console, served by an embedded Tomcat server on TCP port 3052, with a file-upload endpoint. And its service, ppbed.exe, runs as SYSTEM, the most powerful account in Windows, so any command it launches inherits those privileges.

Symantec found that the attacker uploaded scripts through the web console's file-upload endpoint and placed them in the extcmd folder, where the PowerPanel service executed them. The scripts were named to blend in with the product's own files, following patterns such as ppskbcx.cmd and ppgxrte.cmd. In process telemetry, the activity looked like a power-management product launching the Windows command prompt, something defenders might dismiss as routine.

From scripts to the keys of the kingdom

Once the channel was open, the attacker used it as a general remote shell. Scripts downloaded tools with certutil, loaded a small .NET program into memory through PowerShell, and tested the connection back to an attacker-controlled server. One downloaded tool was an antivirus killer, while another was a harmless test program whose only job was to print a greeting, proof that code could be loaded and run through the trusted service.

The main objective was the Active Directory database. The operator repeatedly rewrote the collection scripts, ran them, checked the results and tried again, behaviour Symantec read as a human working live at the keyboard rather than an automated attack. The scripts used ntdsutil to export ntds.dit, the database holding credentials for every account on the network, and later switched to copying it from a Volume Shadow Copy with esentutl, along with the Windows SYSTEM registry hive needed to decrypt it.

The same channel was then used to launch a persistent implant, a file called upnpcont.exe that loaded a malicious atl.dll through DLL side-loading, in which a legitimate program is tricked into loading a hostile library. The implant's process tree led back to ppbed.exe, tying it to the earlier activity.

Symantec has not identified the victim or linked the intrusion to any known group, and has not established how the attacker first reached the PowerPanel console. Possible routes include stolen administrator credentials and previously disclosed weaknesses in the product, including a default administrator password, hard-coded credentials and a file-upload flaw. No exfiltration or final payload such as ransomware was observed.

What defenders should do now

Symantec recommends finding every PowerPanel Business installation and restricting access to TCP port 3052 to named administrator workstations only, never exposing it to the internet or to general user networks. The default administrator password should be changed, patches kept up to date, and the extcmd folders audited against the product's defaults, with any unknown script treated as hostile.

Organisations that find the attacker's indicators should assume Active Directory credentials are exposed and plan a reset of the krbtgt account, which secures Kerberos tickets, along with wider credential rotation. The wider lesson, Symantec said, is that power-management and other infrastructure software should be treated like any other dual-use remote-management product: network-restricted, uniquely credentialed, patched and monitored at the process level.