Apparently, the issue that led to the certificate revocation is ScreenConnect storing configuration data in an available area of the installer that is not signed.
Attackers are changing the configuration data to suit their needs, without affecting the signature.
It's been happening for months, it seems.