How to remove services64.exe
services64.exe
The module services64.exe has been detected as Ransom.Sabsik
services64.exe is a Windows file recorded in the ThreatInfo database. It is associated with Google3 Chrome. The reported company name is Google3 Inc.. The current detection status is Ransom.Sabsik, based on the latest analysis from 2023-06-17 23:52:12 (2 years ago).
If services64.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 Ransom.Sabsik.
File Details
| Product Name: | Google3 Chrome |
| Company Name: | Google3 Inc. |
| MD5: | 285480919abfb64c7dba64798d6c8f30 |
| Size: | 2 MB |
| First Published: | 2021-11-18 21:20:04 (4 years ago) |
| Latest Published: | 2023-06-17 23:52:12 (2 years ago) |
| Status: | Ransom.Sabsik (on last analysis) | |
| Analysis Date: | 2023-06-17 23:52:12 (2 years ago) |
Common Places:
| %appdata% |
| %temp% |
| %appdata% |
| %appdata% |
| %temp% |
| %temp% |
| %appdata% |
ThreatInfo has observed services64.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.
Geography:
| 33.3% | ||
| 33.3% | ||
| 16.7% | ||
| 16.7% |
The strongest geographic signal for this file is Brazil with 33.3% of observed hits. Geographic distribution can help identify targeted campaigns, regional software bundles, or where a file is most commonly reported.
OS Version:
| Windows 10 | 71.4% | |
| Windows 8.1 | 28.6% |
The most common operating system signal for services64.exe is Windows 10 with 71.4% 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
services64.exe is identified as pe for 64 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: | 64 |
| Image Base: | 0x0000000000400000 |
| Entry Address: | 0x000022fa |
PE Sections:
| Name | Size of data | MD5 |
| .text | 5632 | 4baea60a4405856c666765cf2cd8f090 |
| .rdata | 2228736 | 276dc12f45dfe80b9c6baf3d3550b57a |
| .bss | 0 | d41d8cd98f00b204e9800998ecf8427e |
| .pdata | 512 | 833d670d56c423f97067d7571a397b78 |
| .rsrc | 1024 | 67877d9cf681794eb35ea86fa426174b |
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:
