GridinSoft Threat Intelligence

SampleUploader.exe file report

Under review File reputation report
MD5 bd5a32e4a4b331bdfa15553e9c72a24c
Latest seen 2021-03-21 21:29:10 (5 years ago)
First seen 2017-10-17 08:10:09 (8 years ago)
Size 11 KB
Product SampleUploader
Signed by P.C. Pitstop LLC

Why it matters

Evidence available for this file

Detection

No final classification is available yet.

Timeline

First seen 2017-10-17 08:10:09 (8 years ago); latest analysis 2021-03-21 21:29:10 (5 years ago).

Publisher context

Product metadata: SampleUploader.

Digital signature

Signed by P.C. Pitstop LLC. 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.

SampleUploader.exe is a Windows file recorded in the ThreatInfo database. It is associated with SampleUploader. The current detection status is Undefined, based on the latest analysis from 2021-03-21 21:29:10 (5 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: SampleUploader
MD5: bd5a32e4a4b331bdfa15553e9c72a24c
Size: 11 KB
First Published: 2017-10-17 08:10:09 (8 years ago)
Latest Published: 2021-03-21 21:29:10 (5 years ago)
Status: Undefined (on last analysis)
Analysis Date: 2021-03-21 21:29:10 (5 years ago)
Signed By: P.C. Pitstop LLC
Status: Valid

The signature on SampleUploader.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%\pcpitstop\super shield
%programfiles%\pcpitstop

ThreatInfo has observed SampleUploader.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 7 52.4%
Windows 10 47.6%

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

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

Format pe
Architecture 32-bit
Subsystem Windows CUI
Entry point 0x00002c3e
Image base 0x00400000

.NET Info:

MVID: bfdbaaa8-633f-438b-860d-94770c121cd9
Typelib ID: 6687d846-697b-4377-980f-a62fb84ec419

PE Sections:

Sections 3
Raw data 5632

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

.text 3584 bytes · 63.6% of section data
MD5 3572c3272b4a786e1194062ff4d86d86
.rsrc 1536 bytes · 27.3% of section data
MD5 4109b91a3ef48698ab69590824d0be91
.reloc 512 bytes · 9.1% of section data
MD5 ad19108ea943dd04095c026a06a58d40

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