Fences 6.5.8.1 DeElevate64.exe Flagged by Enterprise Security Due to Revoked Legacy Signing Certificate

Windows Version Number: Windows 11 26H2 (26300.9974)
App Version: 6.58

 

I got flagged for a security issue affecting Stardock Fences 6.5.8.1 in a corporate environment.

I've been a licensed Fences user since version 3, and recently installed Fences 6.5.8.1 on a company workstation using the installer downloaded directly from Stardock's official website.

Shortly after installation, our Security Operations Center (SOC) flagged DeElevate64.exe, a legitimate component included with Fences, due to its association with a documented DLL side-loading malware campaign and a revoked code-signing certificate.

Our SOC is currently reviewing the alert and forced an uninstall, but I wanted to bring the certificate issue directly to y'alls's attention.

Background

The alert appears to originate from the following Huntress investigation: https://www.huntress.com/blog/chatgpt-custom-gpts-clickfix-rat

The investigation documents a social-engineering campaign in which attackers distributed a malicious installer containing Stardock's legitimate DeElevate64.exe alongside a modified DeElevator64.dll to execute malicious code.

The campaign does not appear to involve a compromise of Stardock's official Fences distribution.

 

I reviewed the installed files, SHA-256 hashes, and digital signatures.

Fences 6.5.8.1 Installer - Fences6_setup.exe

SHA-256:
4A1B0306750A2280814700EBB8D184CE19B34691D01246FD1C869837161B4E0B

  • Publisher: Stardock Systems, Inc.

  • Signing authority: DigiCert

  • Certificate validity: April 21, 2025 – April 21, 2028

  • Local Authenticode status: Valid

DeElevate64.exe

SHA-256:
22869E3326FE1DE011CD500E666769027126C5C440B76837BAF55139F30094E4

  • Publisher: Stardock Corporation

  • Certificate issuer: UTN-USERFirst-Object (The USERTRUST Network)

  • Certificate validity: October 12, 2008 – October 13, 2011

  • Certificate thumbprint: F7C37113D0C0184F38C51417255C381637504D69

  • Local Authenticode status: Valid

  • VirusTotal signature verification: Signed file, valid signature, revoked

The executable's SHA-256 matches the legitimate Stardock binary identified in the Huntress investigation.

DeElevator64.dll

SHA-256:
C2826461686E08BAD7E2832EEF739601E265C57DEEDF172816A1B356DE2B0968

  • Digital signature: NotSigned

  • Does not match the specific malicious DLL hash published by Huntress.

Legacy Certificate Issue

Further investigation using Windows' certificate-chain verification revealed that the installed DeElevate64.exe is still signed using Stardock's original 2008–2011 certificate.

The certificate chains to the UTN-USERFirst-Object root, which Windows currently identifies as expired, revoked, and explicitly distrusted.

While the executable's local Authenticode signature verifies, the certificate-chain verification reports a revocation error. The detailed results identify the root as revoked and explicitly distrusted, although I haven't established whether Stardock's individual signing certificate was separately revoked.

This appears to create an enterprise security issue. An otherwise legitimate Fences installation can generate security alerts due to the executable's known association with the Huntress campaign and its legacy certificate chain.

Questions

  1. Is the current Fences 6.5.8.1 installer expected to include a DeElevate64.exe executable signed using the 2008–2011 Stardock certificate?

  2. Is Stardock aware that the legacy certificate chain is currently reported as revoked or distrusted by modern certificate-validation systems?

  3. Are there plans to re-sign or replace this executable using Stardock's current code-signing certificate? This would potentially resolve one of the issues triggering enterprise security alerts.

  4. Can Stardock confirm whether the DeElevator64.dll hash provided above is an expected, unmodified component of Fences 6.5.8.1?

  5. Is Stardock aware of any additional security concerns involving the legitimate Fences distribution related to the Huntress findings?

I recognize that the malware campaign itself is not necessarily a vulnerability in Fences. However, the continued distribution of an executable signed with a legacy, distrusted certificate makes it more difficult for corporate security teams to distinguish legitimate installations from malicious packages abusing the same executable.

I'd appreciate any clarification Stardock can provide, particularly regarding the certificate issue and whether an updated executable is available or planned.

I'd like to continue using Fences in our corporate environment, and having an official response from Stardock would be valuable in resolving the current security review.

Thanks

 

11 views 0 replies