Malicious ScreenConnect deployments observed

The Anatomy of the Attack
The malicious campaign identified by Sophos involves the unauthorized deployment of ScreenConnect clients to facilitate remote access. According to technical analysis, the intrusion process typically begins with the execution of legitimate system tools to mask malicious intent. In one documented instance, the attackers utilized curl.exe to initiate the download of a file named ScreenConnect.ClientSetup.msi from the malicious IP address 185[.]99[.]255[.]28. The file is saved directly into the C:WindowsTEMP directory as sc.msi, a common staging area for attackers due to its typically permissive access rights.
Once the installer is staged, a ScreenConnect-generated command file is triggered, invoking msiexec.exe to execute the installation silently. By operating in the background, the attackers minimize the risk of user detection, effectively turning a legitimate support tool into a persistent backdoor. Beyond the initial deployment, Sophos researchers observed the deployment of secondary payloads. These involve the staging of batch files via ScreenConnect scripts and the execution of PowerShell commands with an execution-policy bypass flag. This configuration allows the attacker to pull a second-stage script from ns[.]mo7sen[.]dev/EadF.php?p=4, which likely serves as the command-and-control (C2) communication channel or a gateway for further malicious instructions.
Chronology and Instance Analysis
The scope of this campaign is defined by specific ScreenConnect instance IDs that appear to have been compromised. Sophos has identified three primary instances—d905b2b1b165d0a9, 4b8f4089ddaac6a9, and df1f7ef0cfacd0d8—which act as the origin points for the malicious activity. These instances are likely instances where administrative credentials were stolen or hijacked, allowing attackers to leverage the platform’s native management capabilities. From these compromised hubs, the threat actors deployed malicious instances with the IDs 2588ef5c15954b10 and ed630cc2c873b091.
The timeline of this incident correlates with increased vigilance regarding third-party extensions within the ScreenConnect ecosystem. ConnectWise, the vendor behind ScreenConnect, has acknowledged the incident and is currently investigating reports that suggest the exploit may be facilitated by the abuse of third-party extensions. While the investigation remains ongoing, the rapid shift from initial compromise to secondary script execution suggests a sophisticated threat actor capable of orchestrating multi-stage attacks across fragmented network environments.
Context: The Vulnerability of MSP Infrastructure
The exploitation of remote monitoring and management (RMM) software is not a novel tactic, but it remains a persistent threat. RMM tools like ScreenConnect are designed to provide elevated, persistent access to endpoints, making them inherently attractive to cybercriminals, particularly ransomware operators. In recent years, the security of the software supply chain has come under intense scrutiny. When an RMM platform is compromised, the "blast radius" is significant, as a single compromised instance can potentially grant an attacker access to the entire fleet of devices managed by that specific server.
The reliance on legitimate tools—a technique often referred to as "living off the land"—makes detection notoriously difficult. Because msiexec.exe and curl.exe are standard system utilities, security software that relies solely on signature-based detection may fail to flag the activity as malicious. Sophos and other security firms are now shifting their focus toward behavioral analysis, looking for anomalous command-line arguments and unusual file paths that deviate from standard administrative patterns.
Official Responses and Mitigation Strategies
ConnectWise has released a formal security advisory in response to these developments. The company is urging all ScreenConnect administrators to conduct an immediate audit of their instances. The primary recommendation is to identify and disable any third-party extensions that cannot be verified as legitimate or necessary. Furthermore, the advisory emphasizes the importance of patching and maintaining the latest version of the ScreenConnect software, as updates often contain critical security hardening that can prevent unauthorized access.
SophosLabs, the threat intelligence arm of Sophos, has begun a comprehensive review of its customer base to identify signs of compromise. The organization is in the process of evaluating its existing detection heuristics and is actively working on developing custom countermeasures to address the specific tactics, techniques, and procedures (TTPs) associated with this campaign. "Activity is being reviewed across customer environments and will be escalated where identified," a Sophos spokesperson indicated, highlighting the severity of the threat.
Recommended Defensive Posture
For organizations currently utilizing ScreenConnect, the following proactive measures are strongly recommended:
- Review Command History: Administrators should meticulously audit the ScreenConnect command history logs. Any command execution that involves the
curlutility or unauthorizedmsiexecoperations should be treated as an immediate indicator of compromise. - Monitor Temporary Directories: Security operations centers (SOCs) should implement file integrity monitoring on the
C:WindowsTEMPdirectory. Unauthorized.msifiles or batch scripts appearing in this directory are a primary indicator of staging activity. - Audit PowerShell Execution: Configure endpoint detection and response (EDR) tools to log and flag PowerShell activity that utilizes the
execution-policy bypassflag. This is a common indicator of a secondary payload being executed in a non-interactive manner. - Credential Rotation: Given the potential for credential theft in this incident, administrators should force a password reset for all ScreenConnect accounts and ensure that Multi-Factor Authentication (MFA) is strictly enforced for all administrative logins.
- Network Filtering: Block outbound communication to the identified malicious IP and domain indicators, specifically
185[.]99[.]255[.]28andns[.]mo7sen[.]dev, at the network perimeter level.
Broader Implications for the IT Sector
The incident serves as a stark reminder of the security risks inherent in centralized management systems. As the IT landscape moves toward greater automation and cloud-based management, the number of "chokepoints" in the network increases. An attacker who gains control over an RMM platform effectively gains the administrative powers of the IT staff, allowing them to bypass traditional security controls that might otherwise block an external intruder.
Furthermore, this incident highlights the risks associated with the third-party extension ecosystem. Many RMM platforms encourage developers to create extensions to improve functionality. However, these extensions often run with the same privileges as the core application, creating a potential vector for attackers to inject code or execute unauthorized tasks. Moving forward, the industry will likely see a move toward more stringent vetting processes for third-party software integrations and a greater emphasis on "zero-trust" architecture for management platforms.
As investigations continue, the cybersecurity community expects to see further refinements in detection capabilities. The focus will remain on identifying the origin of these compromised instances and determining whether this activity is linked to a specific state-sponsored group or a profit-motivated cybercriminal organization. For now, the priority remains containment and the hardening of existing remote access infrastructure against similar exploitation tactics. The situation remains fluid, and administrators are encouraged to monitor official security feeds from ConnectWise and their respective cybersecurity vendors for real-time updates.





