GoogleSTTApp.exe threat report

MD5 ddc44051bed9468500e5cbe6fe1736ce
Latest seen 2024-02-21 23:02:19 (2 years ago)
First seen 2024-02-21 23:02:19 (2 years ago)
Size 13 MB

GridinSoft Anti-Malware detection

Detected by GridinSoft before you download

The current ThreatInfo record shows this exact file hash detected as Ransom.Sabsik. Download GridinSoft Anti-Malware to scan the device, confirm whether this file is present, and remove the detected object if it is found.

Detection name
Ransom.Sabsik
Recommended action
Scan and remove
Last analysis
2024-02-21 23:02:19 (2 years ago)
File hash
ddc44051bed9468500e5cbe6fe1736ce
Download Anti-Malware

Why it matters

Why GridinSoft flags this file

Detection

GridinSoft identifies the sample as Ransom.Sabsik.

Timeline

First seen 2024-02-21 23:02:19 (2 years ago); latest analysis 2024-02-21 23:02:19 (2 years ago).

Digital signature

Signed by Shenzhen iMyFone Technology Co., Ltd. The signature is reported as valid, but signed files can still be bundled or abused.

Observed locations

ThreatInfo has seen this file in user or system paths listed below. Unexpected locations increase the need for local verification.

Recommended action

What to do next

  1. Compare the MD5 above with the file found on the device.
  2. Check whether the file appears in the observed locations or under one of the alternate names.
  3. Run GridinSoft Anti-Malware to confirm the detection and remove the file if it is present.

GoogleSTTApp.exe is a Windows file recorded in the ThreatInfo database. The current detection status is Ransom.Sabsik, based on the latest analysis from 2024-02-21 23:02:19 (2 years ago).

If GoogleSTTApp.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.

MD5: ddc44051bed9468500e5cbe6fe1736ce
Size: 13 MB
First Published: 2024-02-21 23:02:19 (2 years ago)
Latest Published: 2024-02-21 23:02:19 (2 years ago)
Status: Ransom.Sabsik (on last analysis)
Analysis Date: 2024-02-21 23:02:19 (2 years ago)
GoogleSTTApp.exe detection screenshot

The screenshot is a visual record of a GridinSoft Anti-Malware detection for this sample. Use the hash and metadata above as the primary identifiers when comparing the file on your system.

Signed By: Shenzhen iMyFone Technology Co., Ltd
Status: Valid

The signature on GoogleSTTApp.exe is reported as valid. A valid signature helps confirm publisher identity, but it does not automatically make the file safe if the installer was bundled, abused, or downloaded from an untrusted source.

%programfiles%\imyfone

ThreatInfo has observed GoogleSTTApp.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.

100.0%

The strongest geographic signal for this file is Egypt with 100.0% of observed hits. Geographic distribution can help identify targeted campaigns, regional software bundles, or where a file is most commonly reported.

Windows 10 100.0%

The most common operating system signal for GoogleSTTApp.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.

GoogleSTTApp.exe is identified as pe for 64 systems. The subsystem is Windows CUI. PE header values are useful for triage, especially when they do not match the expected publisher, product, or release timeline.

Subsystem: Windows CUI
PE Type: pe
OS Bitness: 64
Image Base: 0x0000000140000000
Entry Address: 0x00009b24

PE Sections:

Name Size of data MD5
.text 144384 dcd00cd1af6a00dacfbe21d1c168cf6b
.rdata 70656 2de7f93b07553ccf57db41ea6c7e25d1
.data 3584 93ff6beab5249602fdb56e41214c93a1
.pdata 7680 5fd73e6b132f697d173a19e8ab0209eb
_RDATA 512 0506636a835bf6907171a92f4541d21e
.rsrc 108544 b82d789a7714e35ae981e79438f8a52a
.reloc 2048 7918cd7fe09e2d60657c15aade4ba826

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: