Skip to content

Response, New York. Noah Park: Check Point Patches Actively Exploited Management Server Path Traversal. Detection, Dallas. Ava Okello: Report Finds Nearly Half of Deployed Detections Need Attention Before SOCs Can Trust Them.

SOCtember

Always First. Fast SOC News.

Symantec diagram of the PowerPanel Business attack chain: initial access to the console web service on TCP port 3052, scripts staged into the extcmd folder, ppbed.exe running them through cmd.exe as SYSTEM, and four malicious actions: network reconnaissance, reflective .NET loading, an Active Directory dump and a persistent implant.
Image: Symantec (fair use). PowerPanel Business abuse attack chain, from the Symantec Threat Hunter Team report "Behind the Power Outage," published Nov. 18, 2026.

Detection

Symantec Says Intruders Turned a UPS Power Management Console Into a SYSTEM-Level Shell on a Domain Controller, Then Used It to Dump Active Directory

The attackers uploaded scripts to CyberPower PowerPanel Business, the software that shuts servers down cleanly when the power fails, and let its own service run them. Every command, from certutil downloads to an ntds.dit copy and a side-loaded implant, traces back to ppbed.exe.

Ava Okello, DetectionLondon6 min read

LONDON - An intruder who reached the management console of a widely sold uninterruptible power supply product used it to run commands as SYSTEM on a Windows domain controller, copy the Active Directory database and start a long-running implant, all without exploiting a memory bug or creating a new service, according to research published Wednesday by Symantec's Threat Hunter Team, part of Broadcom.

The product is CyberPower PowerPanel Business, which manages the company's UPS units for small and medium-sized businesses and triggers a graceful shutdown of critical machines when the power fails. Symantec said the software is typically installed on exactly the systems an attacker most wants: hypervisor hosts, database and file servers and, in this case, a domain controller.

The researchers, Yuvaraj Megavarnadu, SwapanKumar Ghosh and Karthikeyan Kasiviswanathan, wrote that abusing the product requires "no complicated memory-corruption exploit, and no new service or scheduled task." In process telemetry, they said, the activity looks like a power-management product launching cmd.exe, something defenders may dismiss as routine recovery behavior.

A documented feature, used as a remote shell

PowerPanel Business lets an administrator attach a command file to a power event, such as a voltage sag or an outage. The file is saved with a .cmd extension in an extcmd folder under the installation directory, and the product's service, ppbed.exe, runs it when the event fires. That service starts under services.exe and runs as SYSTEM. The web console is served by an embedded Tomcat server on TCP port 3052 and exposes a REST API.

In the intrusion Symantec investigated, the domain controller's console received requests to its file-upload endpoint, /local/rest/v1/file/upload, on port 3052. A Tomcat temporary file named upload_ followed by random characters appeared in the product's web-server\work\tomcat\localhost\local directory, and each attacker script showed up first under temp\profile\extcmd before being executed from extcmd. The scripts were named pp followed by five random lowercase letters, so they blended in with the product's own files.

The attacker never waited for a power event. Symantec said the channel was used simply to run arbitrary commands, each one executed by the PowerPanel service through cmd.exe.

Symantec diagram of the process tree: wininit.exe, services.exe, ppbed.exe running as SYSTEM, then cmd.exe launching each uploaded pp?????.cmd script from the extcmd folder, with child processes including ntdsutil.exe, certutil.exe, powershell.exe, reg.exe and curl.exe.
Image: Symantec (fair use).The process lineage defenders should look for, from the Symantec report.

Testing, then taking the directory

The first commands were plumbing. The attacker used certutil to decode a tool from a Base64 file in C:\Windows\Temp, used curl to pull a test file from a server at 84.200.205[.]145 on port 55557, and downloaded three more binaries from the same address on port 55556. One of them, wupd.exe, is detected as a .NET antivirus killer. Another, hello.exe, is a 4,096-byte .NET program whose only function is to print a greeting; the attacker loaded an identical copy into memory through PowerShell, which Symantec read as a check that the reflective-loading path worked.

The collection phase showed a person at the keyboard. Symantec documented a series of scripts that exported ntds.dit with ntdsutil, then reran the export in the background with a log file, then added a "done" marker, then a timestamp and an exit code. When that approach stalled, the attacker saved the SYSTEM registry hive and copied ntds.dit out of a Volume Shadow Copy with esentutl, a switch that gets around the file being locked by the running directory service.

Screenshot of the Symantec report section titled Stage 4, listing the scripts staged through extcmd and their purpose, including ntdsutil exports, a background export with a log file, a done marker, and a SYSTEM hive save followed by an esentutl copy of ntds.dit from a shadow copy.
Image: Symantec (fair use).The attacker's iterative collection scripts, as listed in the report.

Once the database was collected, PowerShell started upnpcont.exe from a randomly named folder under the SYSTEM profile's AppData\Local directory. The file name belongs to a Microsoft UPnP component but does not belong in that location, and it loaded an atl.dll of unknown reputation from the same folder, the classic shape of DLL side-loading. Later vssadmin and robocopy activity ran under the implant, so the full chain still led back through cmd.exe and ppbed.exe to services.exe.

Symantec did not attribute the activity to a known group and said it saw no exfiltration or final payload such as ransomware, leaving the motive unclear. How the attacker reached the console is also not established; the company noted that public advisories for the product document hard-coded credentials, a default administrator password and a file-upload path-traversal flaw, and that any of those, or stolen administrator credentials, would provide the access the attack required.

What to hunt for

The practical lesson in the report is that the parent process is the indicator. Almost everything the intruder ran was a built-in Windows tool, including certutil, ntdsutil, esentutl, reg, vssadmin, robocopy and wmic. Detection teams can alert on ppbed.exe spawning cmd.exe, PowerShell or any of those utilities, on new .cmd files in the extcmd and temp\profile\extcmd folders, and on inbound connections to TCP port 3052 from anything other than known administrator workstations.

Screenshot of the Recommendations section of the Symantec report, advising teams to restrict TCP port 3052, change the default administrator password, audit extcmd paths, plan a krbtgt reset if indicators are found and treat power-management hosts as high-value assets.
Image: Symantec (fair use).Recommendations from the report.

Symantec's own recommendations follow the same line: locate every PowerPanel Business console and limit port 3052 to named administrator hosts, change the default password and patch, compare extcmd contents and event-to-command assignments with product defaults, and treat any unknown script as hostile. If the indicators turn up, the company said, defenders should assume Active Directory credentials are exposed and plan a krbtgt reset and wider credential rotation. The report publishes SHA-256 hashes for the attacker scripts, the Tomcat upload file, the downloaded tools, upnpcont.exe and atl.dll.

The broader point, Symantec wrote, is that UPS, power-management and other infrastructure software should be treated like any other potentially dual-use remote management product, with network restrictions, unique credentials, patching and process-level monitoring.

About the Author

Ava Okello

Ava Okello covers detection engineering, EDR telemetry, and SOC hunting for SOCtember from London.

Related stories

Detection desk