Security

EV-Signed Phishing Installers Drop ScreenConnect

3 min read

Summary

Microsoft Defender Experts uncovered phishing campaigns that use fake meeting, invoice, and document lures to deliver malware installers disguised as trusted apps like Teams, Zoom, and Adobe Reader. What makes this notable is that the installers were signed with an EV certificate and used to deploy legitimate remote management tools such as ScreenConnect and Tactical RMM, giving attackers stealthy initial access that can blend into normal enterprise IT activity.

Need help with Security?Talk to an Expert

Introduction: why this matters

Threat actors are increasingly blending in with legitimate IT operations by deploying commercially available Remote Monitoring and Management (RMM) tools. This campaign raises the bar further by using familiar “workplace app” branding and EV code signing to reduce user suspicion and improve execution rates—making it a practical initial access path in enterprises where users routinely install meeting and document software.

What’s new / key findings

Microsoft Defender Experts observed multiple phishing campaigns attributed to an unidentified threat actor. Key characteristics include:

  • Meeting and document lures: Emails masqueraded as meeting invitations (Teams/Zoom/Google Meet), invoices, financial documents, bids, and organizational notifications.
  • Counterfeit PDFs and spoofed download pages: Some messages delivered fake PDFs with an “Open in Adobe” button that redirected users to a lookalike Adobe download site prompting an “update.”
  • Masquerading executables: Payloads were named to resemble trusted installers, including msteams.exe, adobereader.exe, zoomworkspace.clientsetup.exe, invite.exe, and trustconnectagent.exe.
  • Abuse of trust via EV signing: The droppers were digitally signed with an EV certificate issued to TrustConnect Software PTY LTD, helping them appear legitimate.
  • RMM backdoor deployment: Execution led to installation of RMM tools such as ScreenConnect, Tactical RMM, and Mesh Agent, enabling persistent remote access.

How the intrusion establishes persistence (technical highlights)

In the ScreenConnect-focused chain, the “workspace” executable:

  • Copied itself into C:\Program Files to look like a legitimate installed application.
  • Registered itself as a Windows service for startup persistence.
  • Created an additional autorun via Run key:
    • HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Run
    • Value name: TrustConnectAgent
    • Target: C:\Program Files\Adobe Acrobat Reader\AdobeReader.exe
  • Connected outbound to attacker infrastructure (notably trustconnectsoftware[.]com).
  • Used encoded PowerShell to download additional payloads and invoked msiexec.exe to install ScreenConnect from staged MSI files.

Microsoft noted cases where the MSI appeared unsigned, followed by ScreenConnect binaries signed with revoked certificates, a pattern commonly associated with malicious or unauthorized deployment.

Impact on IT administrators and end users

  • Users are targeted through routine workflows: joining meetings, reviewing invoices, and updating “out-of-date” apps.
  • IT and security teams may see attacker activity blend into normal admin tooling because RMM agents can resemble sanctioned remote support.
  • Risk increases post-compromise: persistence via services/autoruns plus RMM tooling can accelerate credential access, remote control, and lateral movement.

Action items / next steps

  • Harden software installation paths: restrict user-driven installs where feasible; enforce allowlisting (e.g., WDAC/App Control) for “installer-like” executables.
  • Audit RMM usage: inventory approved RMM tools and block or alert on unauthorized agents (ScreenConnect/Tactical RMM/Mesh) and suspicious service creation.
  • Review code-signing trust decisions: treat “signed” as a signal—not proof. Add detection logic for new/rare publishers and unusual EV-signed binaries.
  • Hunt for persistence indicators: look for the TrustConnectAgent Run key, unexpected services, and suspicious msiexec.exe plus encoded PowerShell patterns.
  • Strengthen phishing resilience: reinforce user guidance around “update required” prompts from email/PDFs and use Defender protections to detonate/inspect attachments and links.

Need help with Security?

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

Talk to an Expert

Stay updated on Microsoft technologies

Microsoft DefenderphishingRMMScreenConnectcode signing

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.