Files signed by ByELDI Certificate

ByELDI Certificate

ByELDI Certificate is a digital signature publisher name observed in ThreatInfo records. This page groups 21 signed files and shows whether those files are currently classified as clean, undefined, or detected.

A digital signature can help identify a publisher, but it does not always prove that a file is safe. Certificates may be abused, stolen, expired, or attached to modified installers, so the file hash and detection status should be checked together.

Detection signal

Detected files use this signature name

At least one file signed as ByELDI Certificate is detected by GridinSoft. Review the hashes below and scan the device if one of these files is present.

Download GridinSoft scanner
gService_KMS.exe 3c19c8cbc7917fee066cb7a116d3f326 Risk.Gen
KMSpico 9.1.3.exe 1fadee024cbe8396538cfa2c8d412629 Hack.KMS
AutoPico.exe ca189cb28ed318b44a2a89f0b35b1831 Hack.KMS
KMSELDI.exe 132e4fd0484610a64d6d9580c331e647 Hack.KMS
autopico.exe 0aefaf065282f95d3a15049613b600f5 Hack.KMS
kmseldi.exe f9920eb356157477c001e83641c9a97d Hack.KMS
KMSpico_setup.exe 5e29516ec4e11d7cbd45b5429457debb Hack.KMS
Service_KMS.exe 4cdec52d0f42fc15e50788ead2b8d0d5 Risk.Gen
Service_KMS.exe b591fb11177173525140169eb92b89fa Risk.Gen
AutoPico.exe 3ae2d4c765540fa4e3d8a3054e0491a7 Hack.KMS
KMSELDI.exe d751b0e7260af2843c79d9e228696cc3 Hack.KMS
Service_KMS.exe 23081884235a212fd56bf28a71e0adfc Risk.Gen
KMSELDI.exe d686d8d8d52d64b6d4439ff5118ba0d3 Hack.KMS
AutoPico.exe ae25c9da26b27a09ac901f3c400f9da1 Hack.KMS
KMSELDI.exe c41072b170b818b1a3163fa1c404b4f0 Hack.KMS
Service_KMS.exe 14551b13a5d7c16c92e41e69dac0ee03 Risk.Gen
KMSELDI.exe 07bf238b1f9e1c1cbbb5a9a8ba9a2099 Hack.KMS
Service_KMS.exe 7277f36c937c23b86cb9c030096afe2b Risk.Gen
AutoPico.exe 2e0d9743d64ff13d8d945979310172cf Hack.KMS
Service_KMS.exe ec51d5db19cdc8601c85cb756b785839 Risk.Gen
AutoPico.exe 748ee6dfd9476abafb32598879be2e72 Hack.KMS

Certificate review summary

Do not trust this signature name by itself

ThreatInfo found detected files associated with ByELDI Certificate. A matching signature name should be checked together with the file hash, detection verdict, and source path.

Recommended checks

  • Open any matching file report and compare the MD5 hash.
  • Confirm the file path and download source before trusting the binary.
  • Run a GridinSoft scan if a detected file from this list is present.