GridinSoft Threat Intelligence

StartMenuIndexer.exe file report

Under review File reputation report
MD5 777a01b60930a4fd6e1e1ed9bc65eab0
Latest seen 2025-01-09 23:00:50 (a year ago)
First seen 2017-06-06 15:09:53 (8 years ago)
Size 1 MB
Publisher Pokki
Signed by Pokki

Why it matters

Evidence available for this file

Detection

No final classification is available yet.

Timeline

First seen 2017-06-06 15:09:53 (8 years ago); latest analysis 2025-01-09 23:00:50 (a year ago).

Publisher context

Company metadata: Pokki. Product metadata: Start Menu Service.

Digital signature

Signed by Pokki. 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. Use the hash and metadata below to verify the exact file identity.
  2. Review publisher, signature, paths, and PE details for inconsistencies.
  3. Run a local scan if the file appears unexpectedly or starts with Windows.

StartMenuIndexer.exe is a Windows file recorded in the ThreatInfo database. It is associated with Start Menu Service. The reported company name is Pokki. The current detection status is Undefined, based on the latest analysis from 2025-01-09 23:00:50 (a year ago).

ThreatInfo does not have a final classification for this file yet. Use the technical details below to compare the hash, size, signature, and observed locations with the copy found on your device.

Product Name: Start Menu Service
Company Name: Pokki
MD5: 777a01b60930a4fd6e1e1ed9bc65eab0
Size: 1 MB
First Published: 2017-06-06 15:09:53 (8 years ago)
Latest Published: 2025-01-09 23:00:50 (a year ago)
Status: Undefined (on last analysis)
Analysis Date: 2025-01-09 23:00:50 (a year ago)
Signed By: Pokki
Status: Valid

The signature on StartMenuIndexer.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.

%localappdata%\pokki\engine
%sysdrive%\adwcleaner\quarantine\files\ibwfzvegtyjocfyzdqaurxlewpwmcqpx\engine
%sysdrive%\adwcleaner\quarantine\files\msmnmrhjuwlbrpvukasrqbrojecosqho\engine
%sysdrive%\adwcleaner\quarantine\files\cvdzzvesszzfgrwfigxefhgnaeeejbmt\engine
%sysdrive%\adwcleaner\quarantine\files\hdmngrfcbwrwynlmsnxvlapnyjedtpar\engine
%sysdrive%\adwcleaner\quarantine\files\kmefikgnedtawieqatqeoqdpuueykvrl\engine
%sysdrive%\adwcleaner\quarantine\files\bbrydfxwqezjmqgnsvuxlzihlmyplrbm\engine
%sysdrive%\adwcleaner\quarantine\rywtiizs2t\engine
%sysdrive%\adwcleaner\quarantine\files\hmwqpwobmictnfxiahkbqtzznjdzadvs\engine
%sysdrive%\adwcleaner\quarantine\files\qlmlvfcyhqvabgdrhyrezvlokdrcoxeq\engine

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

Windows 10 56.5%
Windows 8.1 43.5%

The most common operating system signal for StartMenuIndexer.exe is Windows 10 with 56.5% 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.

StartMenuIndexer.exe is identified as pe for 64-bit 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.

Format pe
Architecture 64-bit
Subsystem Windows GUI
Entry point 0x000eabc4
Image base 0x0000000140000000

PE Sections:

Sections 9
Raw data 1896448

Section layout highlights raw-size concentration, repeated names, packer markers, and hashes that can be compared across related samples.

.text 1300480 bytes · 68.6% of section data
MD5 9de395c73094e5ee0a738467a8bcef0d
.rdata 411648 bytes · 21.7% of section data
MD5 adbe0244957268f11d04a20d6622fd18
.data 23040 bytes · 1.2% of section data
MD5 d43db7fe02ff8e7c0da63f6392ec8428
.pdata 79360 bytes · 4.2% of section data
MD5 4422f3d2f620bf2baf70fd8e62be760e
.tls 512 bytes · 0.0% of section data
MD5 bf619eac0cdf3f68d496ea9344137e8b
text 3072 bytes · 0.2% of section data
MD5 1ba7cabe8c9995da4fd2f087816b388a
data 10240 bytes · 0.5% of section data
MD5 a6643ae545092962a14d7bee1a5b20fe
.rsrc 60416 bytes · 3.2% of section data
MD5 c92cd59bf233f1e1163ca7313d4a8e7a
.reloc 7680 bytes · 0.4% of section data
MD5 2884484c6b5462b92ffce35000ca3207

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.

Report conclusion

This file is still under review

ThreatInfo has not assigned a final verdict yet. Compare the file hash, location, signature, and publisher before trusting the file on a production system.

Scan with GridinSoft Anti-Malware Use a local scan if the file origin or behavior is unclear. Check this hash on VirusTotal

Recommended next steps

  • Compare the local file MD5 with 777a01b60930a4fd6e1e1ed9bc65eab0.
  • Check the file path, publisher, and signature against the details in this report.
  • Run a GridinSoft scan if the source, path, or behavior looks unusual.