
Fake Zoom Meeting Invite Installs ScreenConnect
(ConnectWise Control) Remote Access Agent
Applies To: Windows 10 and Windows 11 workstations
Severity: High (unauthorized remote access / persistence)
Overview
Users may receive a phishing email or chat message containing a fake Zoom meeting invitation. Clicking the link results in the silent or prompted installation of ScreenConnect (ConnectWise Control), a legitimate remote access tool that is frequently abused by attackers.
Once installed, the agent runs as a Windows service, registers a credential provider, and can load an authentication package into lsass.exe. This provides persistent remote access and can survive normal user-level uninstall attempts.
Symptoms / Indicators of Compromise
- Unexpected services named
ScreenConnect Client (<unique-id>) - Folders present under:
C:\Program Files (x86)\ScreenConnect Client (<unique-id>)C:\Program Files\ScreenConnect Client (<unique-id>)C:\ProgramData\ScreenConnect Client (<unique-id>)
- File
ScreenConnect.WindowsAuthenticationPackage.dllpresent in the client folder - Credential Providers registered under:
HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Authentication\Credential Providers
with names containing “ScreenConnect Client” - The DLL loaded inside
lsass.exe(visible via Process Explorer or PowerShell module enumeration) - Recent phishing email with Zoom-related subject and a non-official meeting link
Detection Commands
Run the following in an elevated PowerShell window:
# Services
Get-Service *screenconnect*
# Processes
Get-Process *screenconnect* -ErrorAction SilentlyContinue
# Folders
Get-ChildItem -Path "C:\Program Files","C:\Program Files (x86)","C:\ProgramData" -Filter "*ScreenConnect*" -Recurse -ErrorAction SilentlyContinue
# Credential Providers
Get-ChildItem "HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\Authentication\Credential Providers" |
ForEach-Object { Get-ItemProperty $_.PSPath } |
Where-Object { $_.'(default)' -like "*ScreenConnect*" }
Resolution / Remediation
Important: Disconnect the affected machine from the network if active remote access is suspected. Perform all steps with administrative privileges.
- Stop and delete the ScreenConnect services:
Get-Service *screenconnect* | Stop-Service -Force -ErrorAction SilentlyContinue Get-Service *screenconnect* | ForEach-Object { sc.exe delete $_.Name } - Remove the Credential Provider registry keys (replace the GUIDs with the ones found on the system):
Remove-Item -Path "HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\Authentication\Credential Providers\{GUID}" -Recurse -Force Remove-Item -Path "HKLM:\SOFTWARE\Classes\CLSID\{GUID}" -Recurse -Force -ErrorAction SilentlyContinue Remove-Item -Path "HKLM:\SOFTWARE\WOW6432Node\Classes\CLSID\{GUID}" -Recurse -Force -ErrorAction SilentlyContinue - Reboot the computer. This is required so
lsass.exereleases the authentication package DLL. - After reboot, delete the leftover folders:
Remove-Item -Path "C:\Program Files (x86)\ScreenConnect Client*" -Recurse -Force -ErrorAction SilentlyContinue Remove-Item -Path "C:\Program Files\ScreenConnect Client*" -Recurse -Force -ErrorAction SilentlyContinue Remove-Item -Path "C:\ProgramData\ScreenConnect Client*" -Recurse -Force -ErrorAction SilentlyContinueIf access is denied, take ownership first:
takeown /F "C:\Program Files (x86)\ScreenConnect Client (<id>)" /R /D Y icacls "C:\Program Files (x86)\ScreenConnect Client (<id>)" /grant Administrators:F /T Remove-Item -Path "C:\Program Files (x86)\ScreenConnect Client (<id>)" -Recurse -Force - Re-run the detection commands above. All results should be empty.
- Perform additional cleanup:
- Clear related Windows Error Reporting folders under
C:\ProgramData\Microsoft\Windows\WER\ReportArchive - Run a full Microsoft Defender or enterprise EDR scan
- Check scheduled tasks, startup entries, and Run keys for ScreenConnect references
- Delete the original phishing email
- Reset passwords for any accounts used on the machine while the agent was installed
- Open a security incident ticket if unauthorized access is confirmed
- Clear related Windows Error Reporting folders under
Notes
- The
ScreenConnect.WindowsAuthenticationPackage.dllis intentionally loaded bylsass.exewhen registered as a credential provider. Removing the registry keys and rebooting is required before the file can be deleted. - Do not delete the DLL while it is still registered; this can cause boot or logon failures.
- Multiple ScreenConnect clients (different unique IDs) can be present on the same machine.
Additional Recommendations
- Block or tightly control ScreenConnect / ConnectWise Control installations via application allow-listing (AppLocker, WDAC, or EDR).
- Educate users never to install software from unsolicited Zoom or Teams meeting invites.
- Enable Microsoft Defender for Office 365 Safe Links and Safe Attachments.
- Monitor for new services and credential providers matching the patterns above.
- Require administrative approval for third-party remote access tools.
Official References
- ConnectWise Control (ScreenConnect) product documentation
- Microsoft guidance on LSA authentication packages and credential providers
- Common phishing campaign reporting on fake Zoom meeting invites delivering remote access tools
This article is based on observed incident response activity as of November 17, 2026. Always verify current indicators and test remediation steps in a non-production environment when possible.
![]()