GridinSoft Threat Intelligence

SPMUninstaller.exe file report

Under review File reputation report
MD5 2082d954513428ae5ec63ca1e72224a4
Latest seen 2022-03-31 23:09:44 (4 years ago)
First seen 2018-06-05 17:04:56 (7 years ago)
Size 43 KB

Why it matters

Evidence available for this file

Detection

No final classification is available yet.

Category context

Potentially unwanted programs, bundlers, installers, and utilities with intrusive behavior. Related PUP reports help compare this file with nearby detections, publishers, and hashes.

Timeline

First seen 2018-06-05 17:04:56 (7 years ago); latest analysis 2022-03-31 23:09:44 (4 years ago).

Digital signature

Signed by Smart PC Solutions, Inc.. 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.

SPMUninstaller.exe is a Windows file recorded in the ThreatInfo database. The current detection status is Undefined, based on the latest analysis from 2022-03-31 23:09:44 (4 years ago). ThreatInfo groups this verdict with PUP reports for broader family-level investigation.

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.

MD5: 2082d954513428ae5ec63ca1e72224a4
Size: 43 KB
First Published: 2018-06-05 17:04:56 (7 years ago)
Latest Published: 2022-03-31 23:09:44 (4 years ago)
Status: Undefined (on last analysis)
Analysis Date: 2022-03-31 23:09:44 (4 years ago)
Signed By: Smart PC Solutions, Inc.
Status: Valid

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

ThreatInfo has observed SPMUninstaller.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 100.0%

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

SPMUninstaller.exe is identified as pe for 32-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 32-bit
Subsystem Windows GUI
Entry point 0x0001d2d0
Image base 0x00400000

PE Sections:

Sections 3
Raw data 39424

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

UPX0 0 bytes · 0.0% of section data
Packer marker Uncommon name
MD5 00000000000000000000000000000000
UPX1 38400 bytes · 97.4% of section data
Packer marker Uncommon name
MD5 c7ff187bbd9ef2b5f5c2aa5cf1acde26
.rsrc 1024 bytes · 2.6% of section data
MD5 6f061b978503f6ed60f0addb2cdbc653

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 2082d954513428ae5ec63ca1e72224a4.
  • 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. Use the PUP category to compare similar reports.