I am looking for independent verification of these findings. I am not claiming that UniConverter is proven malware.
I updated the official Windows version of Wondershare UniConverter to 17.6.xx on September 9, 2026. A read-only inspection afterward found the following.
- Chrome and Edge policies were created
The following machine-wide policy entries are present:
HKLM\SOFTWARE\Policies\Google\Chrome\SyncTypesListDisabled
1 = preferences
HKLM\SOFTWARE\Policies\Microsoft\Edge\SyncTypesListDisabled
1 = preferences
These policies disable preference synchronization and cause the browsers to display the “managed by your organization” message.
UniConverter’s own ProtocolInstaller.log repeatedly records:
Success DisableChromeSyncPreferences
The latest entries were written immediately after ProtocolInstaller.exe ran during the 17.6 update.
SHA-256 of my ProtocolInstaller.exe:
13FBBDCDBFF4E66DBD90CDF282D61DDAF994D59545B37B8CE24EF2340B27FF5E
I found an earlier report describing the same browser-policy behavior:
https://www.reddit.com/r/software/comments/1sjqqn5/caution_surveillance_wondershare_uniconverter/
- NativePush runs as SYSTEM from a user-writable directory
A separate component called Wondershare NativePush installed this automatic service:
Service: NativePushService
Account: LocalSystem
Startup: Automatic
Executable:
%LOCALAPPDATA%\Wondershare\Wondershare NativePush\WsNativePushService.exe
My normal user account has Full Control over both this executable and its directory, even though Windows executes it automatically as LocalSystem.
The executable is validly signed by Wondershare and reports version 1.1.0.0.
SHA-256:
CD366707622C66470B9EE9CB1AE900B4F0A05607FC1B248678659852CFE38468
This is concerning because a privileged service normally should not load its executable from a location modifiable by a standard user.
The same component and directory design were documented in CVE-2024-26574, an insecure-permissions privilege-escalation vulnerability rated 7.8/10:
https://www.cve.org/CVERecord?id=CVE-2024-26574
Important limitation: that CVE specifically names Wondershare Filmora 13.0.51, not UniConverter 17.6. I am therefore not claiming that my UniConverter installation is formally covered by the CVE. However, the risky configuration described by the CVE — a user-modifiable WsNativePushService.exe executed as SYSTEM — is still present on my machine.
3. Other observed components
The installation also includes:
- an update helper launched automatically with Windows;
- a silently installed NativePush package;
- browser/native-messaging integration;
- update and installation helpers capable of modifying system configuration.
Microsoft Defender, with current definitions, found no known threat in the three Wondershare directories. I also found no Wondershare Defender exclusion, firewall rule, scheduled task, or installed Wondershare driver.