How to remove SigmaKey.exe
SigmaKey.exe
The module SigmaKey.exe has been detected as Trojan.Heur!
SigmaKey.exe is a Windows file recorded in the ThreatInfo database. It is associated with Phone Servicing Solution. The current detection status is Trojan.Heur!, based on the latest analysis from 2023-03-23 23:48:55 (3 years ago).
If SigmaKey.exe appears on your computer unexpectedly, treat it as suspicious. Check its location, digital signature, and recent system changes before allowing it to run. A full anti-malware scan is recommended when this file is detected as Trojan.Heur!.
File Details
| Product Name: | Phone Servicing Solution |
| MD5: | a82eb96ee092789314bcbe03771cb5ce |
| Size: | 12 MB |
| First Published: | 2023-03-23 23:48:55 (3 years ago) |
| Latest Published: | 2023-03-23 23:48:55 (3 years ago) |
| Status: | Trojan.Heur! (on last analysis) | |
| Analysis Date: | 2023-03-23 23:48:55 (3 years ago) |
Common Places:
| %programfiles%\gsmserver |
ThreatInfo has observed SigmaKey.exe in the locations listed above. Files found in temporary folders, user profile folders, startup locations, or unusual application directories should be reviewed more carefully than files installed under a known program directory.
OS Version:
| Windows 10 | 100.0% |
The most common operating system signal for SigmaKey.exe is Windows 10 with 100.0% of observed hits. If your system differs from the common profile, check whether the file was introduced by a specific installer, archive, or removable device.
Analysis
SigmaKey.exe is identified as pe for 32 systems. The subsystem is Windows GUI. PE header values are useful for triage, especially when they do not match the expected publisher, product, or release timeline.
| Subsystem: | Windows GUI |
| PE Type: | pe |
| OS Bitness: | 32 |
| Image Base: | 0x00400000 |
| Entry Address: | 0x00208c43 |
PE Sections:
| Name | Size of data | MD5 |
| .text | 421376 | 695ee5135f51dd885645e8c7f4065469 |
| .text | 2636800 | 1a927c9b531ab19480bee99ebfed8d99 |
| .text | 3504128 | 450b1b27b6a3fd5d2b4004a28cb3e46b |
| .rdata | 6868992 | 8e77eb053e029cd2555d7214caf4004c |
| .rdata | 2560 | caf974a6934bd481df3accb6e2bcd300 |
| .rdata | 3072 | 0119f8fe82fe12c10b9d1eab791bd765 |
| .data | 128000 | 2040686000e8d82a7a502d074a26da9a |
| .rdata | 3584 | c755dc36a0701d5720322461c9a1db9d |
| .rdata | 17408 | b86c5060099d879d62fe66afaf6dd982 |
| .data | 7168 | 494c0ce66df9a8877a09e4f95d7f7c00 |
| .rsrc | 24064 | 4759ed277529fc2d779c120045f73fdf |
| .discard | 6656 | c3d949dc136c07ce79aac459459f7c8f |
| .ps4 | 0 | d41d8cd98f00b204e9800998ecf8427e |
PE section names and hashes can reveal packing, injected resources, or unusual build artifacts. Sections with uncommon names, very large raw data, or hashes that differ from a trusted copy deserve additional review.
More information:
