A PowerPanel Business attack has shown how software intended to protect server availability can become a privileged route into Active Directory. Attackers abused CyberPower’s UPS management platform on a Windows domain controller, executing commands as SYSTEM and copying sensitive credential data.
Symantec publicly disclosed the intrusion on 18 November 2026. Its investigation found hands-on activity involving uploaded command scripts, PowerShell, Active Directory database collection and a later DLL side-loaded implant.
How the PowerPanel Business attack unfolded
CyberPower PowerPanel Business manages uninterruptible power supplies and can safely shut down connected systems during extended power failures. Its legitimate capabilities include running administrator-defined scripts when configured power events occur.
On Windows, the relevant PowerPanel Business service, ppbed.exe, runs under the highly privileged SYSTEM account. Commands launched by that service inherit SYSTEM permissions, which made the software a valuable execution channel after the attackers obtained access to its web console.
The PowerPanel Business attack involved the console on TCP port 3052. HTTP POST requests to the /local/rest/v1/file/upload endpoint placed attacker-supplied files beneath the product’s embedded Tomcat work directory.
The uploaded content subsequently appeared as command scripts in the CyberPower PowerPanel Business temp\profile\extcmd directory. Scripts with names following patterns such as ppskbcx.cmd, ppgxrte.cmd, ppotuff.cmd and ifm*.cmd were then executed from the extcmd directory by ppbed.exe.
Because ppbed.exe operated as SYSTEM, it could spawn cmd.exe and powershell.exe with extensive privileges. The attackers used this process chain to test network connectivity, retrieve tools and establish that they could execute code in memory.
Tool downloads and in-memory execution
Observed commands used certutil and curl to communicate with 84.200.205.145 over high-numbered ports, including 55556 and 55557. Referenced resources included junk50k.bin, while binaries were downloaded under names including dt.bin and wupd.bin.
The attackers also reflectively loaded a small .NET assembly into memory. Although that test program only produced a greeting, it demonstrated that code could be loaded and run through a trusted, SYSTEM-level PowerPanel process without first launching it as a conventional executable.
Active Directory data targeted in the attack
The central objective observed during the PowerPanel Business attack was the acquisition of Active Directory credential material. The operator repeatedly changed scripts, executed them and checked the results, behaviour that indicated an interactive, human-operated intrusion rather than a fully automated exploit.
Initial collection attempts used ntdsutil to create an Install From Media, or IFM, export. When those attempts did not achieve the required result, the operator changed approach.
The attackers created a Volume Shadow Copy using vssadmin. They then used esentutl to copy ntds.dit, the locked database containing Active Directory objects and password hashes, from the shadow copy.
They also collected the Windows SYSTEM registry hive. Possession of both ntds.dit and the SYSTEM hive can provide the material needed to decrypt and extract domain password hashes, potentially allowing offline password cracking, account impersonation or further movement through the domain.
Symantec did not observe the collected files leaving the network. It also found no ransomware deployment during the investigated activity, so the attackers’ ultimate objective remains unknown.
DLL side-loading followed the collection
Later activity associated with the same process tree launched upnpcont.exe from C:\Windows\System32\config\systemprofile\AppData\Local\50679f292a1. Although its name resembled a Microsoft component, its location beneath the SYSTEM profile was unusual.
The executable loaded a malicious atl.dll from the same directory. This technique, known as DLL side-loading, places a malicious library where a legitimate or apparently legitimate executable will load it in preference to the expected file.
The lineage ppbed.exe to cmd.exe to powershell.exe to upnpcont.exe linked this implant activity directly to the earlier PowerPanel execution. It also provides defenders with a useful behavioural trail, particularly because UPS management software would not normally initiate PowerShell, copy Active Directory databases or launch binaries from a SYSTEM profile directory.
Affected PowerPanel Business versions and access
The product abused was CyberPower PowerPanel Business for Windows, installed on a domain controller. Symantec did not disclose the victim’s exact version, so the PowerPanel Business attack should not be attributed to one confirmed vulnerability or release.
CyberPower documentation independently confirms that the web interface uses TCP 3052 and that event scripts can be placed in an extcmd directory. These are legitimate features, but they became powerful control points when accessed by an unauthorised operator.
The initial entry route remains unconfirmed. Possible explanations include stolen administrator credentials or previously documented PowerPanel Business weaknesses involving hard-coded credentials, default or weak credentials and unsafe file handling.
Relevant version history includes:
- PowerPanel Business 4.9.0 and earlier contained documented issues including hard-coded credentials and relative path traversal in file import.
- Version 4.10.1, released on 17 April 2024, addressed the issues covered by CISA advisory ICSA-24-123-01, published on 2 May 2024.
- Version 4.11.0 was affected by CVE-2024-11322, a separate unauthenticated denial-of-service issue involving TCP 2003. This is not the Active Directory collection method used in this intrusion.
- Version 4.12.2 was released on 6 May 2026 with security and third-party component improvements.
- Version 4.12.4, released on 22 September 2026, was the latest listed Windows package when the incident was reported.
No incident-specific CyberPower advisory had been identified by 19 November 2026. The confirmed exploitation status therefore rests on the intrusion observed by Symantec, rather than confirmation that a particular CVE was exploited.
Why this SYSTEM-level abuse matters
The PowerPanel Business attack demonstrates the risk posed by administrative infrastructure software running with broad privileges. On a domain controller, abusing such a service can turn a specialised management console into a route for credential theft and persistent malware execution.
The event does not prove that every deployment is vulnerable to unauthenticated compromise. It does show that console access, whether gained through credentials or an unpatched weakness, can have domain-wide consequences when scripts run as SYSTEM.
Actions for organisations using PowerPanel Business
Organisations should identify every PowerPanel Business installation, establish its version and determine whether it is present on a domain controller. The latest supported vendor release should be applied, and default or shared administrative credentials should be replaced.
- Restrict TCP 3052 to approved administrator workstations and keep the console off the public internet and ordinary user networks.
- Review extcmd and temp\profile\extcmd for unknown scripts, particularly names matching the observed pp*.cmd and ifm*.cmd patterns.
- Investigate ppbed.exe spawning cmd.exe, powershell.exe or programs from SYSTEM profile directories.
- Search for connections to 84.200.205.145 and review access to /local/rest/v1/file/upload.
- If ntds.dit and the SYSTEM hive were copied, treat domain credentials as exposed, plan a controlled krbtgt reset and rotate affected credentials across the domain.
Monitoring should focus on the specific execution chain and file locations observed in this case. These signals can distinguish normal UPS administration from PowerPanel activity being used to access Active Directory or establish a follow-on implant.
Originally reported by cybersecuritynews.com.






