Threat Intel
Huntress Reports Phishing Campaigns Using Rogue ScreenConnect Installations for Persistent Access
Huntress says its SOC has seen phishing attacks that convince employees to install rogue remote management tools, including ScreenConnect, giving attackers persistent access. Defenders should inventory authorized RMM agents, block or alert on unauthorized remote access software, and hunt for unexpected installers, services, and outbound management connections.
What happened
Huntress reported that its SOC observed phishing attacks in which employees were persuaded to install unauthorized remote management software. The briefing specifically names ScreenConnect as an example of a rogue RMM tool used to establish persistent access.
The attacks rely on user action rather than a disclosed software flaw: once an employee runs the installer, the remote access agent can remain on the endpoint and provide a channel for later intrusion.
Who is affected
Any organization whose users can install software and whose endpoints are reachable from the internet or from attacker-controlled RMM portals is exposed. Risk is higher where remote support tools are common, where installation controls are weak, or where employees receive support-related phishing messages.
What to do
- Inventory all RMM and remote access agents, then define an approved list by vendor, product, version, and installation path.
- Block or alert on unauthorized installers, services, scheduled tasks, and processes associated with remote management software, including ScreenConnect if it is not approved.
- Review email and endpoint telemetry for phishing lures that request remote support, IT help, or software installation.
- Enforce application allowlisting, least privilege, and user approval for new software where feasible.
- Search for unexpected outbound connections to RMM portals, new local admin accounts, and persistent access mechanisms on endpoints that recently received user-initiated installs.
Detection focus
Defenders should treat unexpected RMM installation as a high-fidelity indicator of compromise, not just a support ticket. Look for install events, service creation, new listening ports, and user-agent or portal activity that does not match the organization's approved remote access stack.
Practical rule: if a remote management agent appears on a host without an authorized change record, investigate it as malicious until proven otherwise.