IPS Signature Oct 01, 2026

GajIPS - IPS Signature Update — GS TROJAN: Dual-RMM phishing campaign (MSP360 + ScreenConnect) attacker C2 domain detection

Attackers are using trusted remote-management software to maintain two separate access paths into compromised Windows systems. GajIPS detects the linked C2 infrastructure.

Severity: HIGH · Priority: P2 — dual-RMM persistent access via phishing, investigate on hit

These rules detect connections to domains used as relay or C2 hosts for ScreenConnect sessions established by a phishing campaign. The campaign, observed in July 2026, distributes a digitally signed MSP360 Remote Monitoring and Management installer version 2.5.0.67 under deceptive lure names — meeting invitations, PDF-themed files, software update prompts, and tax-document lures. When the victim executes the installer and approves a User Account Control elevation prompt, MSP360 establishes itself as a persistent Windows service and gives the attacker remote management access. The attacker then uses MSP360 to silently download and install ConnectWise ScreenConnect, creating a second independent remote-access channel — a dual-RMM setup that provides redundancy if either tool is removed or blocked. With both tools in place, the attackers collect credentials, gather system information, modify firewall settings and autorun entries, and stage additional executables, while blending their activity into the appearance of legitimate IT remote management.

A hit on these rules indicates a device on your network is establishing outbound ScreenConnect sessions to infrastructure linked to this campaign. Because both MSP360 and ScreenConnect are legitimate software that appears in many corporate environments, a hit should be correlated with evidence of unauthorised installation: check whether MSP360 RMM v2.5.0.67 was installed without a sanctioned IT request, look for the services RMM.Agent.exe and RMM.Agent.Launcher.exe, and verify whether ScreenConnect on the same device was deployed through your organisation's own ScreenConnect instance or an external one. Treat an unexplained installation of either tool combined with a hit on these rules as a probable intrusion: isolate the device, revoke any credentials stored on or reachable from it, and investigate what the attacker may have accessed through the remote sessions. Remove both unauthorised RMM tools, check firewall settings and autorun entries for modifications, and hunt for any additional executables staged by the attacker.

The most effective long-term control against this class of attack is an approved-RMM inventory policy: know which remote management tools are authorised in your environment and on which devices, and treat any other RMM installation as a security event. Endpoint detection rules for MSP360 and ScreenConnect installation events from unexpected parent processes or without a prior IT change ticket provide earlier detection than network indicators, which only fire after the tools are already connecting to the attacker's infrastructure.

See the latest threat intelligence