Security

Phishing Abuses RMM Tools for Persistent Access

3 min read

Summary

Microsoft security researchers observed phishing campaigns in July 2026 that used a legitimate MSP360 RMM installer disguised as meeting invites, PDF updates, and other lures to gain remote access. Attackers then deployed ConnectWise ScreenConnect for redundant persistence, highlighting the need for tighter controls on remote management tools and better detection of unapproved RMM activity.

Need help with Security?Talk to an Expert

Phishing abuses RMM tools for persistent access

Introduction

Microsoft has detailed a phishing campaign that shows how legitimate remote monitoring and management (RMM) tools can be turned into a stealthy persistence mechanism. For IT and security teams, this matters because the software involved is trusted, signed, and commonly used in enterprise environments—making abuse harder to spot than traditional malware.

What’s new

In July 2026, Microsoft Defender Experts observed phishing campaigns targeting multiple industries. The attackers delivered a legitimate MSP360 RMM installer under deceptive filenames and themes such as:

  • Meeting invitations
  • Zoom or Google Meet install prompts
  • Adobe/PDF reader updates
  • Document review or signature requests
  • RSVP and e-card lures
  • Package delivery notifications

After a user executed the file and approved UAC elevation, the installer:

  • Installed MSP360 RMM for persistent remote access
  • Registered Windows services for long-term foothold
  • Added autorun entries for user sign-in persistence
  • Created a Windows Firewall allow rule for the RMM agent
  • Used PowerShell to download and silently install ConnectWise ScreenConnect

Microsoft noted that attackers did not exploit a vulnerability in ScreenConnect. Instead, they abused legitimately obtained remote administration software to create a second remote-access channel.

Why this matters for administrators

This campaign reinforces a growing problem: threat actors are blending into normal IT activity by using approved or familiar admin tools instead of custom malware.

For defenders, that creates several challenges:

  • Signed installers can appear trustworthy to users and security controls
  • RMM traffic may resemble legitimate remote support activity
  • Multiple remote-access tools on one endpoint can provide redundant persistence
  • Post-compromise actions such as credential access and data collection may happen through tools already allowed in the environment

Organizations that do not tightly govern which RMM products are approved may struggle to distinguish sanctioned use from attacker activity.

Security and endpoint teams should review Microsoft’s guidance and hunting queries from the original research. Practical actions include:

  • Audit and inventory approved RMM tools across the environment
  • Block or restrict unapproved RMM software through application control
  • Monitor for uncommon or newly installed remote administration tools
  • Investigate endpoints running both MSP360 and ScreenConnect unexpectedly
  • Review phishing protections for software update and meeting-invite lures
  • Use Microsoft Defender for Endpoint detections for suspicious RMM behavior

Bottom line

This campaign is a reminder that legitimate admin tools can become an attacker’s persistence layer when introduced through phishing. IT teams should treat unexpected RMM installations as high-risk activity and enforce stricter controls around remote management software.

Need help with Security?

Our experts can help you implement and optimize your Microsoft solutions.

Talk to an Expert

Stay updated on Microsoft technologies

SecurityphishingRMMMSP360ScreenConnect

Related Posts

Security

Microsoft Sentinel Named a 2026 SIEM Leader

Microsoft has been named a Leader in the 2026 Gartner Magic Quadrant for SIEM, highlighting the continued momentum behind Microsoft Sentinel. The announcement also underscores Microsoft's push toward integrated, AI-powered security operations through deep Sentinel integration with the new Integrated Security Operations Center in Microsoft Defender.

Security

Microsoft Perception GA: Agentic Security at Ignite

Microsoft has made Microsoft Perception generally available, introducing an agentic security platform that coordinates red, blue, and green team agents through automated playbooks. Announced at Ignite 2026, the update also expands Defender and Sentinel capabilities to help security teams detect, investigate, and remediate AI-speed threats while keeping administrators in control.

Security

Device Code Phishing Risks for AI Coding Agents

Microsoft warns that device code phishing can be used against AI coding agents such as GitHub Copilot CLI, not just user mailboxes or cloud apps. In a controlled lab, a single approved device code sign-in could enable remote session steering, memory poisoning, synced session exposure, and private repository access depending on account permissions and enabled features.

Security

Microsoft 365 Outage Phishing Campaign Targets Users

Microsoft Threat Intelligence reported a high-volume phishing campaign that impersonates Microsoft 365 service-health notifications to trick users into clicking malicious links. The campaign matters because it uses outage-themed urgency and recipient-specific tracking to target multiple industries, increasing the risk of credential theft and follow-on account compromise.

Security

SCKit ScreenConnect Attack: MSPs Must Hunt Now

Microsoft Threat Intelligence confirmed a campaign abusing ConnectWise ScreenConnect to deploy unauthorized remote-access clients and the SCKit worm on MSP-managed endpoints. The activity can also target technician sessions, making this a high-priority incident for defenders because removing a rogue client alone does not eliminate persistence or invalidate exposed sessions.

Security

AI Agent Supply Chain Attacks Target Coding Tools

Microsoft Security researchers detailed two post-training supply chain attack paths that can backdoor coding and terminal agents: dataset poisoning and model poisoning. The findings matter because compromised agents can misuse tools, execute commands, and access sensitive environments even when prompts appear benign, reinforcing the need for stronger controls around training data, model provenance, and tool permissions.