Power Management Software Turned Into a Backdoor on a Domain Controller
An attacker has abused CyberPower's PowerPanel Business (PPB) software to run malicious scripts on a domain controller, the server that controls logins across a Windows network. Symantec detailed the intrusion in research published on 18 November.
PPB manages uninterruptible power supply (UPS) battery backups, so it often runs on important systems such as hypervisors, database servers and file servers. Administrators can set it to launch a script when it detects a power problem, and the service runs that script with SYSTEM privileges, the highest level in Windows. Symantec said this let the attacker run code without exploiting a software bug and without creating a service or scheduled task.
According to Symantec, the attacker uploaded scripts through the web console and used them to stage an antivirus killer and copy the Active Directory database, which holds credentials for every account on the network. A persistent implant followed, loaded through DLL sideloading, where a legitimate program is tricked into loading a malicious library. Most of the tooling shipped with Windows, and the data collection scripts were rewritten several times, which Symantec read as a human operator working live.
Symantec did not say how the attacker reached the network or the PPB console. Possible routes included stolen administrator credentials and previously disclosed weaknesses, such as a default administrator password, hard-coded credentials and a file upload flaw. The victim was not named, the activity was not linked to a known group, and with no data theft or ransomware seen, the motive remains unclear. Symantec urged organizations to treat power-management software with the same suspicion as remote administration tools.
Why it matters
Because the script feature runs as SYSTEM by design, the usual assumption that an attacker needs a vulnerability or a new persistence mechanism does not hold, so alerts keyed to those behaviours may stay silent. Any business running PPB on hypervisors, file servers or domain controllers is exposed, and a weak console login effectively becomes a path to full domain credentials. It forces defenders to inventory management software that sits outside normal IT tooling and apply the same access controls they give remote administration products.
What to do
- Restrict PPB console access to specific administrator machines and keep it off the internet.
- Replace the default administrator password and apply the latest PPB patches.
- Check the folders PPB runs scripts from and treat any unfamiliar script as malicious.
- Reset Active Directory credentials if indicators of compromise are found.