Dev.to Security πŸ” Cybersecurity πŸ‘ 0 πŸ“– 12 min read

When Attackers Gain Control of the Tools That Manage Your Infrastructure

Recent attacks on remote-management, virtualization and backup systems reveal a security problem that goes beyond individual vulnerabilities: the authority these platforms hold over other systems. One administr

Recent attacks on remote-management, virtualization and backup systems reveal a security problem that goes beyond individual vulnerabilities: the authority these platforms hold over other systems.

One administrative tool. Hundreds of systems.

Imagine an IT team managing 200 servers and employee devices.

Instead of connecting to every machine individually, administrators use a central platform to install updates, run maintenance tasks, monitor health and troubleshoot problems. It saves time and helps keep systems configured consistently.

But what if an attacker gains control of that platform?

Depending on its permissions, the attacker may be able to deploy software, execute commands or change configurations across multiple systems without compromising each one separately.

This is why management platforms deserve particular security attention. Their purpose is to control other systems, and that same authority can become dangerous when it falls into the wrong hands.

Security investigations from October and November 2026 show how attackers exploited different parts of this administrative trust.

Where does a management platform get its power?

Modern infrastructure depends on several types of management software.

Remote monitoring and management (RMM) platforms allow technicians to administer endpoints and servers. Virtualization managers control hosts and virtual machines. Backup consoles coordinate data protection and recovery. Cloud administration and security systems manage resources, identities and network access.

These tools need privileged capabilities to do their jobs.

An RMM platform may communicate with installed agents that run commands using elevated operating-system permissions. A virtualization manager can instruct a host to create, stop or modify virtual machines. A backup system may possess credentials that allow it to access protected workloads and storage.

The important distinction is between accessing a system and having authority to administer other systems.

An ordinary application might be able to read or change its own data. A management platform can potentially change the environment in which many applications operate.

The extent of that authority depends on its configuration, credentials, permissions and connected systems. It is not necessarily unlimited.

Three mechanisms from recent investigations illustrate why those boundaries matter.

The table sets the incidents side by side and separates what each source confirms from what it only reports.

Incident What attackers did or could do Confirmed by the source Reported, not established Fix or response
ScreenConnect and RMM+ (Huntress, November 11 and 13) Ran commands from management panels to install remote-access software on managed devices At least 288 endpoints in 48 organizations in about 90 minutes, then 205 hosts in 41 organizations Activity appeared related to RMM+ versions 1.0.31 and 1.0.32, which accepted a blank access key. ConnectWise had not identified an initial access vector. Spread through technician sessions was not observed succeeding ConnectWise disabled RMM+ and related extensions on its hosted environments
Xen Orchestra (Vates advisory VSA-2026-062, November 10) Bypassed authentication with an empty-object token and gained administrator access A threat actor was actively exploiting it. Successful unauthenticated access leaves no application log Code execution on managed pools and root takeover of XCP-ng hosts is a possible outcome, not a described result Fixed in versions 6.9.2 and 6.10.1
Check Point gateway to ESXi (Check Point Research, one intrusion) Exploited gateway flaws, escalated to root, persisted, then moved to an ESXi host over SSH and ran a wiper The move to ESXi and the wiper in that one investigated intrusion How the attackers obtained the ESXi service account credentials. The true nature of the operation is not assessed with high confidence A security fix was available about a week before the first activity (advisory SK1000362)
AhsayCBS backup servers (Huntress, October 8 to 11) Chained an authentication bypass and a remote code execution flaw on exposed servers, then planted webshells, a cryptocurrency miner and remote-access tools Tooling recovered from three servers in one environment, including a webshell that hid encrypted payloads in PNG image data On a related Veeam server, a command consistent with a credential-theft module. How many credentials were retrieved is unknown Hotfixes 10.3.4.45 for version 10 and 9.15.2.70 for versions 7 to 9. Patching does not remove what was already planted
N-able N-central (N-able, November 10 to 13) Reported weaknesses in authentication, permissions, legacy API access and agent impersonation Hotfix 2 on November 10 addressed seven documented CVEs. N-able treats the central application separately from its agents, probes and appliances Authenticated data leakage issues remain open and are described as lower risk Hotfix 2 released, Hotfix 3 planned

Status as of November 16, 2026, from the reports listed under Go deeper. The rows record different kinds of evidence, so they are not a ranking of severity.

1. When legitimate administration becomes the attack mechanism

On November 11, 2026, Huntress observed attackers using ScreenConnect management panels to run commands that deployed unauthorized remote-access software onto managed devices.

The initial wave affected at least 288 endpoints across 48 organizations in approximately 90 minutes. Huntress reported additional activity on November 13 involving 205 hosts across 41 organizations.

ScreenConnect’s remote-command capability is a legitimate administrative feature. In this incident, attackers used access to management panels to execute malicious commands through that feature.

Huntress said the activity appeared related to an authentication weakness in a third-party extension called RMM+, where versions 1.0.31 and 1.0.32 accepted a blank access key. ConnectWise said it had not identified an initial access vector, and it disabled RMM+ and related extensions on its hosted environments. The weakness Huntress described sits in the extension, not in a proven flaw in ScreenConnect’s core product. Although the SCKit malware included functionality intended to spread through technicians’ remote sessions, researchers did not observe that additional method succeeding.

Huntress’s SCKit investigation provides the observed command activity, malware analysis and evidence limitations.

The operational problem is not limited to ScreenConnect.

Any management tool capable of executing commands across many systems needs a way to distinguish authorized administration from misuse of that authority.

A technician installing approved software on 20 machines and an attacker deploying unauthorized software through a stolen management session may both use the same underlying functionality.

That creates a detection challenge. Security teams need to consider not just which software executed a command, but who initiated it, which devices were targeted, whether the action was expected and whether its scope was unusual.

2. When compromising one component opens a path to more privileged systems

The second mechanism concerns management infrastructure that sits above ordinary workloads.

In November 2026, Vates disclosed an authentication bypass in Xen Orchestra, a platform used to manage XCP-ng virtualization infrastructure.

The flaw involved how an empty-object authentication token was interpreted. Under the affected conditions, an attacker could bypass authentication and gain administrative access. Vates warned that Xen Orchestra compromise could lead to code execution on managed pools and potentially full takeover of XCP-ng hosts as root.

A virtual machine may have strong operating-system security, but its virtualization host operates beneath it. Administrative control at that level can undermine protections applied only inside the guest operating system.

Vates also documented an important detection limitation: successful unauthenticated exploitation does not generate a corresponding application log. Its published indicators cover known attacker activity, not every possible use of the vulnerability.

See Vates Security Advisory VSA-2026-062.

A separate investigation by Check Point Research demonstrates a related, though technically different, problem.

Attackers exploited vulnerabilities in Check Point Security Gateways, escalated privileges and established persistence. In one investigated intrusion, they then moved from the gateway to a VMware ESXi host over SSH and executed destructive malware.

The gateway compromise did not automatically grant control of ESXi. The attacker still needed a path into that environment and usable authentication. The significance is that a compromised infrastructure component became a foothold for reaching another sensitive system.

Check Point Research’s PHP2Shell investigation documents the sequence and its attribution limitations.

Both cases raise a practical architecture question:

Can a compromised administrative component reach systems or privileges beyond those required for its intended job?

Network segmentation, restricted management interfaces and narrowly scoped service credentials can help limit that reach. They cannot guarantee that a trusted platform will never be compromised, but they can affect what an attacker is able to do afterward.

3. When the systems needed for recovery are compromised

The third mechanism becomes especially serious during incident response.

In October 2026, Huntress investigated compromised AhsayCBS backup-management servers. Researchers recovered webshells, cryptocurrency-mining software, persistence mechanisms and remote-access tools.

One webshell concealed encrypted payloads in PNG image data. On a related Veeam server in the same environment, investigators also found a command consistent with a credential-theft module for Veeam, although they could not say whether any credentials were retrieved.

The Huntress AhsayCBS investigation describes the tooling recovered from three servers in one affected environment.

Backup administration is sensitive because it sits close to the systems organizations rely upon when something goes wrong. If attackers compromise that environment, responders may need to establish whether backup credentials, administrative settings or recovery resources have also been affected.

This creates a dependency problem.

An organization might have reliable backups, but restoring them could still be difficult if access to the recovery infrastructure depends on a management system that cannot be trusted.

The same issue can arise with other administrative services. If the usual management console is compromised or unavailable, the organization needs an independently protected way to investigate and restore critical systems.

Security updates are necessary, but the deployment matters

Not every management-platform security incident involves a successful compromise.

N-able’s November 2026 N-central response illustrates the separate challenge of remediating vulnerabilities in a management system made up of several connected components.

On November 10, N-able released Hotfix 2 addressing seven documented CVEs. Its November 13 update described additional reported weaknesses involving authentication, permissions, legacy API access and agent impersonation, with further remediation planned.

N-able’s response distinguished the central application from its Agents, Probes and appliances, which perform management functions and communicate with the central server.

See N-able’s November 13 remediation update.

This distinction matters during patching. Administrators need to understand which components are affected, what fixes are available, whether updates must follow a particular order and whether temporary restrictions are necessary.

It also matters when a compromise has already occurred.

A patch can close a vulnerable entry point without necessarily removing malicious software installed earlier, revoking stolen credentials or reversing unauthorized configuration changes.

That is why vulnerability remediation and incident recovery require different decisions.

What should organizations change?

These investigations do not mean centralized administration is a bad design choice.

Without central management, organizations can struggle with inconsistent configurations, delayed updates and limited operational visibility. The objective is to keep those advantages while reducing the consequences of unauthorized access.

The most useful starting point is to understand the authority each management platform holds.

Limit administrative reach

Identify the management interfaces, service accounts, APIs, installed agents and integrations that can act on other systems.

Restrict access to people and services that need it. Where appropriate, separate management networks from ordinary user and application traffic, and protect administrative access with strong authentication.

An automation service that checks system health should not receive configuration-changing permissions unless its job requires them.

Control actions that affect many systems

Mass scripting, software deployment and bulk configuration changes have a wider potential impact than ordinary single-device administration.

Where supported, these operations can be protected through role restrictions, additional authorization or alerts for unusual activity.

The aim is not to make administrators approve every routine task manually. It is to provide stronger controls for actions capable of affecting large parts of the environment.

Preserve independent evidence

Critical administrative actions should be observable through monitoring that does not depend entirely on the system being investigated.

This can include separately protected audit logs, endpoint telemetry and network monitoring.

For example, if a management server is compromised, independently collected endpoint events may help determine which machines received commands and what happened afterward.

Prepare to recover without the compromised console

An organization should know how to regain control of important systems if its normal administration platform becomes untrustworthy.

That may require independently protected recovery accounts, trusted installation sources, separate backup credentials and tested alternative access paths.

These measures should be proportional to the environment. A small organization using a hosted support tool does not require the same design as an enterprise operating multiple virtualization clusters.

The common requirement is that recovery must not depend entirely on the component being recovered.

A useful exercise for your next security review

Choose the management platform with the broadest authority in your environment.

Rather than beginning with a product checklist, trace one administrative action through the system.

Suppose an administrator deploys an update to 100 endpoints.

Where does the administrator authenticate? Which service receives the instruction? What credentials or privileges does it use? Which agents execute the command? Where is the activity recorded?

Interactive figure: view it in the original article

Accessible text alternative for this figure

The figure traces one administrative action, such as deploying an update to 100 endpoints, in five numbered stages. Each stage matches one question of the exercise.

Stage 1: the administrator signs in. The question is where the administrator authenticates.

Stage 2: the management platform receives the instruction. The question is which service receives it. An amber flag marks this stage: if the platform is compromised, the attacker holds the authority it has over the systems it manages.

Stage 3: the platform acts with its own credentials and privileges. The question is which credentials or privileges it uses.

Stage 4: agents on the endpoints run the command. The question is which agents execute it. The command reaches all 100 endpoints, shown as a grid of 100 small squares.

Stage 5: an independent record of the action, kept outside the platform and apart from the platform’s own log. The question is where the activity is recorded, and whether the team could investigate and regain control without depending on the compromised platform.

Figure 1. One administrative action traced from sign-in to 100 endpoints. The numbers match the five questions above. A compromise of the platform changes the outcome at step 2, so the independent record at step 5 must not depend on it.

Now consider what happens if the administrative session or central platform is compromised.

Could the attacker reach all 100 endpoints? Would anyone detect an unexpected deployment? Could the team investigate the activity and regain control without depending on the compromised platform?

This exercise turns a general security concern into a specific architectural assessment.

It also helps identify where additional access restrictions, monitoring or recovery arrangements would have the greatest value.

Protect the authority, not just the application

Management platforms are longstanding targets because they hold valuable administrative capabilities. The incidents from October and November 2026 reinforce that risk rather than establish a new category of attack.

Their technical details differ, but they demonstrate how management authority can be misused, how compromise can extend into other infrastructure and why recovery may become more difficult when trusted administrative systems are affected.

For infrastructure teams, the question is not whether centralized management should exist.

It is whether the authority it holds is appropriately limited, observable and recoverable.

The security of a management platform must be measured partly by what happens when its authority is compromised.

Go deeper

Huntress: SCKit Worm Investigation: Original investigation into malicious commands delivered through ScreenConnect, including observed activity and unconfirmed propagation paths.

Vates: Xen Orchestra Security Advisory: Authentication-bypass mechanism, affected versions, detection limitations and remediation guidance.

Check Point Research: PHP2Shell Exploitation: Analysis of gateway compromise, privilege escalation, persistence and movement into virtualization infrastructure.

Huntress: Inside an AhsayCBS Intrusion: Technical analysis of attacker persistence and tooling found on compromised backup-management servers.

N-able: Vulnerability Remediation Update: November 13, 2026 vendor guidance explaining confirmed fixes and further work on authentication and agent communications.

CISA and Partners: Guide to Securing Remote Access Software: Joint guidance from CISA and partner agencies (June 2023) on restricting administrative access, managing remote-access tools and monitoring high-impact operations.

Related TechiesJournal reading

When a Trusted Cloud Application Becomes an Attack Path: How trusted application identities can extend unauthorized access across customer environments.

Cloud Control Plane Outages: Why Running Servers Do Not Mean a Working Service: Why infrastructure availability and recovery depend on systems outside the running workloads.

Technical sources reviewed November 16, 2026.

Originally published on TechiesJournal.

πŸ“° Read the original article on Dev.to Security

Originally published by Dev.to Security. Aggregated on AIWithGhost for educational purposes β€” full credit and traffic to the original publisher.