GridinSoft Threat Intelligence

StartMenuIndexer (1).exe file report

Under review File reputation report
MD5 9127e95ccf5dc5e828f59e84c4a13969
Latest seen 2024-05-30 23:02:22 (2 years ago)
First seen 2017-05-30 18:11:27 (8 years ago)
Size 2 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-05-30 18:11:27 (8 years ago); latest analysis 2024-05-30 23:02:22 (2 years 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.

Aliases

This hash has appeared under multiple file names, which can happen with repackaging, bundling, or deliberate renaming.

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 (1).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 2024-05-30 23:02:22 (2 years 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: 9127e95ccf5dc5e828f59e84c4a13969
Size: 2 MB
First Published: 2017-05-30 18:11:27 (8 years ago)
Latest Published: 2024-05-30 23:02:22 (2 years ago)
Status: Undefined (on last analysis)
Analysis Date: 2024-05-30 23:02:22 (2 years ago)
Signed By: Pokki
Status: Valid

The signature on StartMenuIndexer (1).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\puvstpljnwbfttpsjuszpbmjmnoznrfu\engine
%localappdata%\pokki
%sysdrive%\adwcleaner\quarantine\files\zknpyqkmpsengrusmfymtfgwnngsqpef
%sysdrive%\adwcleaner\quarantine\files\tddukjustictdxuowepakvauzwkeiaxh
%sysdrive%\adwcleaner\quarantine\files\lbmfqkhvsnoiigcrloksdufmmotwhlce
%sysdrive%\adwcleaner\quarantine\files\amxovpebclsbglpiomtgvsnfahdljnha
%sysdrive%\adwcleaner\quarantine\files\gnhrjbfuyhrrpsrljwrihmamvmsovhzl
%sysdrive%\adwcleaner\quarantine\files\lvgliexicbmaxhbepfzoszkmqlnbrwqv
%sysdrive%\adwcleaner\quarantine\files\gwrcrmjthyjzzlmcyhdknhsfspagucwh

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

StartMenuIndexer.exe $RKGAFT7.exe $RV5HAVK.exe $RS6BTB0.exe StartMenuIndexer (1).exe

This hash has been seen with multiple file names. Alternate names can appear when software is updated, copied between folders, packed by an installer, or deliberately renamed to avoid recognition. Compare the exact MD5 above before assuming two names refer to the same file.

Windows 8.1 51.6%
Windows 10 48.4%

The most common operating system signal for StartMenuIndexer (1).exe is Windows 8.1 with 51.6% 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 (1).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 0x001c17a0
Image base 0x0000000140000000

PE Sections:

Sections 9
Raw data 3107840

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

.text 2230272 bytes · 71.8% of section data
MD5 31197d3929a7cab531a03b480389ae3c
.rdata 626688 bytes · 20.2% of section data
MD5 12d8516d8c2e74a04be8bcbd567124c2
.data 31232 bytes · 1.0% of section data
MD5 5d69ea061287b7fe53118d2b32a6a144
.pdata 134656 bytes · 4.3% of section data
MD5 57189ba5cc5786dcdbef42f24784709e
.tls 512 bytes · 0.0% of section data
MD5 bf619eac0cdf3f68d496ea9344137e8b
text 3072 bytes · 0.1% of section data
MD5 4fc1095174c30957e811cc343247cc9d
data 10240 bytes · 0.3% of section data
MD5 a6643ae545092962a14d7bee1a5b20fe
.rsrc 58368 bytes · 1.9% of section data
MD5 28bdafb7e658db23fc6394c912fb670c
.reloc 12800 bytes · 0.4% of section data
MD5 a3f97cea3b2dbb39aa8ae7469e2e1111

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 9127e95ccf5dc5e828f59e84c4a13969.
  • 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.