GridinSoft Threat Intelligence

MaxSpywaredetectorx64.exe_4_0.tmp file report

Under review File reputation report
MD5 6b2938e3eef35b4294092119afe1d08b
Latest seen 2021-03-05 04:56:22 (5 years ago)
First seen 2021-03-05 04:56:22 (5 years ago)
Size 43 MB

Why it matters

Evidence available for this file

Detection

No final classification is available yet.

Timeline

First seen 2021-03-05 04:56:22 (5 years ago); latest analysis 2021-03-05 04:56:22 (5 years ago).

Publisher context

Company metadata: Max Secure Software . Product metadata: Max Spywäre Detëctor .

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.

MaxSpywaredetectorx64.exe_4_0.tmp is a Windows file recorded in the ThreatInfo database. It is associated with Max Spywäre Detëctor . The reported company name is Max Secure Software . The current detection status is Undefined, based on the latest analysis from 2021-03-05 04:56:22 (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: Max Spywäre Detëctor
Company Name: Max Secure Software
MD5: 6b2938e3eef35b4294092119afe1d08b
Size: 43 MB
First Published: 2021-03-05 04:56:22 (5 years ago)
Latest Published: 2021-03-05 04:56:22 (5 years ago)
Status: Undefined (on last analysis)
Analysis Date: 2021-03-05 04:56:22 (5 years ago)
%localappdata%\max secure software

ThreatInfo has observed MaxSpywaredetectorx64.exe_4_0.tmp 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 Server 2012 R2 100.0%

The most common operating system signal for MaxSpywaredetectorx64.exe_4_0.tmp is Windows Server 2012 R2 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.

MaxSpywaredetectorx64.exe_4_0.tmp 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 0x0000aad0
Image base 0x00400000

PE Sections:

Sections 8
Raw data 155648

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

CODE 41984 bytes · 27.0% of section data
MD5 49513e676dadfb3919c4b137dd7c6d66
DATA 1024 bytes · 0.7% of section data
MD5 0a7b48e75f6b6ef4a087528fee0d185c
BSS 0 bytes · 0.0% of section data
MD5 d41d8cd98f00b204e9800998ecf8427e
.idata 2560 bytes · 1.6% of section data
MD5 df5f31e62e05c787fd29eed7071bf556
.tls 0 bytes · 0.0% of section data
MD5 d41d8cd98f00b204e9800998ecf8427e
.rdata 512 bytes · 0.3% of section data
MD5 14dfa4128117e7f94fe2f8d7dea374a0
.reloc 0 bytes · 0.0% of section data
MD5 d41d8cd98f00b204e9800998ecf8427e
.rsrc 109568 bytes · 70.4% of section data
MD5 8f119e4b4a7462a157f77eea7f7fdce7

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 6b2938e3eef35b4294092119afe1d08b.
  • 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.