Rogue ScreenConnect Hit an MSP Client Twice in 12 Days After Compromised Machines Returned Too Soon
In early September, a 2am alert in the Huntress Security Operations Center (SOC) flagged suspicious remote monitoring and management (RMM) activity in the client network of managed service provider TruePath IT. Close to 1,000 endpoints were at risk. The attackers had compromised an account with wide-reaching admin rights and used it to push out rogue ScreenConnect instances, giving them remote control of machines that could run scripts and push updates.
The SOC isolated the affected endpoints and sent a critical incident report straight away. TruePath's Vice President of Operations, Tom Warren, took over just before 5am and asked for a call with the SOC anyway, because the client would treat his next words as final. An analyst joined in under 10 minutes, then supported a call with the client's IT director, who could then pass confirmed facts up to executives. By the time the first wave settled, the client had been down for about two days.
Under pressure from leadership to restore operations, the client put some endpoints that were still compromised back into use before they were fully cleaned. Twelve days later, a second rogue ScreenConnect instance appeared in the same environment, this time delivering what looked like a ransomware executable. The attacker had kept a foothold on those machines. The two incidents cost the client an estimated $3 million in downtime.
TruePath locked the environment down again and finished the cleanup. This time, nothing returned to production until the client's IT team verified remediation on each endpoint and an executive gave verbal approval. Recovery was slower, but the client never received a ransom note. Huntress also advises deciding in advance who can isolate systems, who talks to leadership, and which remote access tools are allowed, blocking all others by default.
Why it matters
The attacker did not need malware to start: one over-privileged admin account turned a trusted remote support tool into a way into almost 1,000 machines. The second incident shows that business pressure to restore service can quietly undo containment, so recovery sign-off needs to be a defined control rather than a judgement call under stress. Any business using RMM tools, or relying on an MSP that does, is exposed to this pattern.
What to do
- Block remote access tools by default and allow only the ones your business has approved.
- Review what normally runs in your environment and remove leftover software from past IT providers, projects or trials.
- Check which ports and services are exposed to the internet and tighten them with a hardened firewall policy.
- Require per-endpoint verification of remediation and executive approval before any machine returns to production.