Hi,

Could you please check this in your tenant and verify whether this original 7z.exe (v24.09) SHA1 is incorrectly displayed as code-signed by "OneWorkplace Operations"?

SHA1: db96d4b476005a684f4a10480c722b3d89dde8a5  
SHA256: e2ca3ec168ae9c0b4115cd4fe220145ea9b2dc4b6fc79d765e91f415b34d00de

As you can clearly see in the file properties dialog, the binary is **not signed**.  
Also Virustotal shows it as Unsigned Publisher:  
[VirusTotal - File - e2ca3ec168ae9c0b4115cd4fe220145ea9b2dc4b6fc79d765e91f415b34d00de](https://www.virustotal.com/gui/file/e2ca3ec168ae9c0b4115cd4fe220145ea9b2dc4b6fc79d765e91f415b34d00de/details)

And also signtool.exe cannot find any signature:  
`signtool verify c:\temp\7z.exe`  
`File: c:\temp\7z.exe`  
`Index  Algorithm  Timestamp`  
`========================================`  
`SignTool Error: No signature found.`



There is also no SHA1 matching entry in the `DeviceFileCertificateInfo` table:

    DeviceFileCertificateInfo
    | where SHA1 has "db96d4b476005a684f4a10480c722b3d89dde8a5"

We have several similar samples showing the same behavior with other CodeSigners.

It seems, this is just another backend error in the Defender Security Portal.

Hello MS, could you please fix this or must I open a support case for this?  
"Do the needful".  


Defender Backend Error with incorrectly CodeSigners