GridinSoft Threat Intelligence

StartMenuIndexer.exe file report

Under review File reputation report
MD5 bd1ba7a2e927f67f016e49d062368fdd
Latest seen 2024-01-17 23:22:51 (2 years ago)
First seen 2017-08-24 22:03:22 (8 years ago)
Size 1 MB
Publisher Pokki
Product Start Menu Service
Signed by Pokki

Why it matters

Evidence available for this file

Detection

No final classification is available yet.

Timeline

First seen 2017-08-24 22:03:22 (8 years ago); latest analysis 2024-01-17 23:22:51 (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.

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.

File context

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 2024-01-17 23:22:51 (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.

File Details

Product Name: Start Menu Service
Company Name: Pokki
MD5: bd1ba7a2e927f67f016e49d062368fdd
Size: 1 MB
First Published: 2017-08-24 22:03:22 (8 years ago)
Latest Published: 2024-01-17 23:22:51 (2 years ago)
Status: Undefined (on last analysis)
Analysis Date: 2024-01-17 23:22:51 (2 years ago)

Overview

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.

Common Places:

%localappdata%\pokki\engine
%localappdata%\pokki
%windir%\serviceprofiles\networkservice\appdata\local\pokki
%windir%\serviceprofiles\localservice\appdata\local\pokki
%sysdrive%\windows.old\users\default\appdata\local\pokki
%sysdrive%\adwcleaner\quarantine\1xvpfvjcrg

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.

Geographic signal

Observed country distribution

ThreatInfo has seen StartMenuIndexer.exe across 5 countries. Use this signal to compare local evidence with where the sample is most often reported.

Top country United States
Share 69.2%
Low High activity

The strongest geographic signal for this file is United States with 69.2% 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 73.1%
Windows 8.1 26.9%

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

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 0x000e9e64
Image base 0x0000000140000000

PE Sections:

Sections 9
Raw data 1891328

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

.text 1296384 bytes · 68.5% of section data
MD5 f371aff6923887851050b678d1e4a527
.rdata 411136 bytes · 21.7% of section data
MD5 bcffb2d0c9cdad9f1e82fa46ab57696b
.data 23040 bytes · 1.2% of section data
MD5 22ecf975d6dc2b5a78f818c1558d2cf9
.pdata 78848 bytes · 4.2% of section data
MD5 1f413b0eab99d4a0bc9f7db894893753
.tls 512 bytes · 0.0% of section data
MD5 bf619eac0cdf3f68d496ea9344137e8b
text 3072 bytes · 0.2% of section data
MD5 bc4471b02c526e0ac6889ca795f58175
data 10240 bytes · 0.5% of section data
MD5 a6643ae545092962a14d7bee1a5b20fe
.rsrc 60416 bytes · 3.2% of section data
MD5 1f63116d733659458fc5fb6dd2804df9
.reloc 7680 bytes · 0.4% of section data
MD5 910ef2ddab9adee5b0f1cc11c94f3171

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 bd1ba7a2e927f67f016e49d062368fdd.
  • 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.