--- title: "CyberPower PowerPanel Abused on a Domain Controller: Act" url: https://playciso.com/blog/cyberpower-powerpanel-domain-controller-attack updated: 2026-11-19 section: Blog publisher: PlayCISO --- # CyberPower PowerPanel Abused on a Domain Controller: Act > Symantec: an attacker used CyberPower PowerPanel Business to run SYSTEM commands on a domain controller and copy AD data. No CVE named. What to check. Source: https://playciso.com/blog/cyberpower-powerpanel-domain-controller-attack · Published: 2026-11-19 · Publisher: PlayCISO (https://playciso.com) Primary source: https://www.security.com/threat-intelligence/power-management-software-attack-vector --- **An attacker turned UPS management software into a way to run commands as SYSTEM on a Windows domain controller.** In a report published on 18 November 2026, [Symantec's threat intelligence team](https://www.security.com/threat-intelligence/power-management-software-attack-vector) says the attacker abused **CyberPower PowerPanel Business**, which manages uninterruptible power supplies, to run scripts on the domain controller, copy the **Active Directory database** and start a long-running implant. Symantec names **no CVE** and does not know how the attacker first got in. Nobody has been named as responsible. **Who this is for:** CISOs, Active Directory and infrastructure owners, and SOC and threat-hunting leads. The software here is about power, but the lesson covers every agent and console that can run commands on a domain controller. *Based on Symantec's report, read in full on 19 November 2026, with CISA's 2024 advisory on older PowerPanel Business flaws for background. PlayCISO is not affiliated with Symantec or CyberPower. We publish no indicators or attack commands.* Confirmed vs not yet known **Symantec reports (18 Nov 2026):** scripts were uploaded through the PowerPanel Business web service and run by its event-action feature; the PowerPanel service ran them as SYSTEM on a Windows domain controller; the attacker copied the Active Directory database (ntds.dit) and started an implant whose process lineage leads back to the PowerPanel service. **No CVE named:** Symantec describes abuse of a legitimate feature, not an exploit. It says public advisories about hard-coded credentials, a default administrator password and a file-upload path traversal, or stolen administrator credentials, "could give an attacker the necessary console access". **Not established:** how the attacker got access, whether any data left the network, what the final goal was (no ransomware or other final payload was seen), who the attacker is, and the victim's sector or country. Symantec gives no dates for the intrusion and does not say which PowerPanel version or edition was installed. **CyberPower:** Symantec does not mention a CyberPower response, and we found no CyberPower statement about this intrusion on 19 November 2026. ## What the attacker did, at a defender's level Everything in this section is [Symantec's account](https://www.security.com/threat-intelligence/power-management-software-attack-vector). We leave out commands, file hashes and network indicators; Symantec's report lists them for defenders. - Used a feature, not a bug. PowerPanel Business can run a stored command script when a power event, such as an outage, happens. The attacker uploaded scripts through the web service's file-upload function and had the PowerPanel service run them. Because every process traced back to that trusted service, the activity could pass for normal power-management behaviour. Symantec notes that no new service or scheduled task was needed. - Lived off the land. Once running commands, the attacker used built-in Windows tools such as certutil and PowerShell, and tested a reflective .NET loader with a harmless program first. - Went for the Active Directory database. Scripts using built-in database and shadow-copy tools were refined over several attempts until they copied the Active Directory database. Symantec reads the trial and error as a human operator at work. - Left an implant. The attacker then started a long-running program that side-loaded an unknown DLL from a user-profile folder, again with a process lineage that led back to the PowerPanel service. A copy of the Active Directory database contains the password hashes for every account in the domain, including the krbtgt account that signs Kerberos tickets. Whether or not anything was seen leaving the network, that is why Symantec's advice for anyone who finds these signs is to assume the domain's credentials are exposed. ## Why management software on a domain controller is tier-0 Domain controllers are the most sensitive servers most organisations run: control of one is control of the identity system everything else trusts. Many security programmes call this tier 0. Anything that can run code on a domain controller belongs in the same tier, and that includes software nobody thinks of as security-relevant: UPS and power agents, backup agents, hardware monitoring, remote-management and patching tools. If that software has a web console that can tell it what to run, **the console and everyone who can log in to it are tier-0 too**, and so is the network path to it. Power-management agents end up on domain controllers for a sensible reason (shutting down cleanly when the battery runs low), and then nobody reviews them, patches them or watches what they launch. This report shows that blind spot being used. The same pattern runs through other recent incidents with management tools, such as the [ScreenConnect rogue-client attacks](/blog/cve-2026-84869-screenconnect-rogue-clients) and the Puppet Server flaw in our [Puppet CVE-2026-115731 post](/blog/puppet-cve-2026-115731-kev). ## What security leaders should do this week - Find every PowerPanel Business install. Search for the software on domain controllers first, then every other server: software inventory, EDR process data and listening ports. Record the version and edition of each, and which host runs the management console. Symantec says to locate all PowerPanel Business console instances. - Close the console. Restrict TCP port 3052 to named administrator hosts; Symantec says not to expose it to the internet, other servers or user networks. Change the default administrator password, use unique credentials per console and keep the software patched (CISA's 2024 advisory on earlier flaws says to run 4.10.1 or later; check CyberPower's site for the current release). - Audit what it is set to run. Compare the contents of the extcmd folder in the installation directory, and of temp\profile\extcmd, against the product defaults on every PowerPanel host, and review which commands are assigned to which power events. Symantec says to treat unknown scripts as hostile. - Check the service account and what it can reach. Confirm which account the PowerPanel service runs as and whether it needs SYSTEM on a domain controller at all. Where shutdown can be handled another way, move the agent off the domain controller. - Watch the process tree. Alert when the PowerPanel service (or any power, backup or monitoring agent) starts a command shell, PowerShell, certutil, database or shadow-copy tools, or anything that touches the Active Directory database. Symantec's point is that these process trees look trusted, so make that parent-child pair a detection, not an allow-list entry. - If you find signs of this activity, treat it as a domain compromise: bring in incident response, preserve evidence, and, as Symantec advises, plan a krbtgt reset and wider credential rotation (the krbtgt password is normally reset twice, with replication in between, alongside privileged and service accounts). The [Kerberos attack lab](/tools/kerberos-attack-lab) shows why a stolen krbtgt hash matters. - Extend the review to every agent on your domain controllers. List every non-Microsoft service on them, who administers its console, and whether it can run commands. Use the [attack path mapping lab](/tools/attack-path-mapping-lab) to trace the routes, put the gaps in your [risk register](/tools/risk-register), and run a hunt for unusual children of those services (the [hunt plan review](/tools/hunt-plan-review) helps scope it). ## Timeline | Date | Event | Source | | --- | --- | --- | | 31 Mar 2023 | ZUSO publishes advisory ZA-2023-02 on a file-upload flaw in PowerPanel Business 4.8.6 and earlier (one of the public advisories Symantec links) | ZUSO | | 2 May 2024 | CISA advisory ICSA-24-123-01: hard-coded passwords and credentials, path traversal and other flaws in PowerPanel Business 4.9.0 and earlier; fix in 4.10.1 or later; no known public exploitation reported to CISA | CISA | | Not stated | The intrusion: PowerPanel Business abused on a Windows domain controller (Symantec gives no dates) | Symantec | | 18 Nov 2026 | Symantec publishes "Behind the Power Outage: Unmasking a New Intrusion Vector in Enterprise Infrastructure Tools" | Symantec | | 19 Nov 2026 | No CyberPower statement on the intrusion found; no CyberPower product in the CISA KEV catalog | CyberPower, CISA KEV | ## Frequently asked questions ### What happened with CyberPower PowerPanel Business? Symantec's threat intelligence team reported on 18 November 2026 that an attacker abused PowerPanel Business, CyberPower's software for managing uninterruptible power supplies (UPS), on a Windows domain controller. The attacker uploaded scripts through the software's web console and had its event-action feature run them; the PowerPanel service ran them as SYSTEM. The attacker used this to copy the Active Directory database and start a long-running implant. ### Was a CVE exploited in the PowerPanel attack? Symantec does not name one and does not say a vulnerability was exploited. It says the attacker abused a legitimate feature that runs a command script when a power event occurs, and that no memory-corruption exploit, new service or scheduled task is needed for that. It notes that public advisories about hard-coded credentials, a default administrator password and a file-upload path traversal in PowerPanel Business, or stolen administrator credentials, could give an attacker the console access the technique needs. ### How did the attacker get in? Not established. Symantec does not describe the initial access. It also did not observe data exfiltration or a final payload such as ransomware, and it has not attributed the activity to a known group. ### Why is software on a domain controller such a risk? A domain controller holds the Active Directory database, including the password hashes for every account in the domain. Any software that runs there with SYSTEM rights, and can be told what to run from a web console, is a path to the whole domain. That makes the software, its console and its administrators part of the most sensitive tier of your environment (often called tier 0), whatever the software is for. ### What should I check if we run PowerPanel Business? Find every PowerPanel Business console and agent, especially on domain controllers and other critical servers. Restrict TCP port 3052 to named administrator hosts, change the default administrator password, keep the software patched, and compare the contents of its extcmd folders with the product defaults. Review which commands are assigned to power events. Symantec says to treat unknown scripts as hostile. ### What if we find signs of this activity? Symantec says to assume Active Directory credentials are exposed and to plan a krbtgt reset and wider credential rotation. In practice that means treating it as a domain compromise: involve your incident response team, preserve evidence, and plan the krbtgt reset (done twice, with replication in between) alongside resets of privileged and service accounts. ### Has CyberPower responded? Symantec's report does not mention a CyberPower response, and we found no CyberPower statement about this intrusion on 19 November 2026. CISA's 2024 advisory on older PowerPanel Business flaws says to update to version 4.10.1 or later. ## Sources - [Symantec Threat Intelligence: Behind the Power Outage: Unmasking a New Intrusion Vector in Enterprise Infrastructure Tools (18 November 2026)](https://www.security.com/threat-intelligence/power-management-software-attack-vector) - [CISA ICS advisory ICSA-24-123-01: CyberPower PowerPanel Business (2 May 2024, revised 12 August 2025)](https://www.cisa.gov/news-events/ics-advisories/icsa-24-123-01) - [ZUSO advisory ZA-2023-02: CyberPower PowerPanel Business (31 March 2023)](https://zuso.ai/advisory/za-2023-02) - [CyberPower: PowerPanel Business product page](https://www.cyberpowersystems.com/products/software/power-panel-business-software/power-panel-business/)