GridinSoft Threat Intelligence

MalwareScanner.dll file report

Under review File reputation report
MD5 a9dd3a1482da75e1ba55bbc4860e6e28
Latest seen 2021-01-11 12:24:24 (5 years ago)
First seen 2020-01-04 19:36:22 (6 years ago)
Size 292 KB

Why it matters

Evidence available for this file

Detection

No final classification is available yet.

Timeline

First seen 2020-01-04 19:36:22 (6 years ago); latest analysis 2021-01-11 12:24:24 (5 years ago).

Publisher context

Product metadata: MalwareScanner.dll Module.

Digital signature

Signed by Sorentio Systems Ltd. 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.

MalwareScanner.dll is a Windows file recorded in the ThreatInfo database. It is associated with MalwareScanner.dll Module. The current detection status is Undefined, based on the latest analysis from 2021-01-11 12:24:24 (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: MalwareScanner.dll Module
MD5: a9dd3a1482da75e1ba55bbc4860e6e28
Size: 292 KB
First Published: 2020-01-04 19:36:22 (6 years ago)
Latest Published: 2021-01-11 12:24:24 (5 years ago)
Status: Undefined (on last analysis)
Analysis Date: 2021-01-11 12:24:24 (5 years ago)
Signed By: Sorentio Systems Ltd
Status: Valid

The signature on MalwareScanner.dll 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.

%commondir%

ThreatInfo has observed MalwareScanner.dll 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 42.1%
Windows XP 42.1%
Windows 7 15.8%

The most common operating system signal for MalwareScanner.dll is Windows 10 with 42.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.

MalwareScanner.dll 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 0x000262a6
Image base 0x10000000

PE Sections:

Sections 5
Raw data 273408

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

.text 197120 bytes · 72.1% of section data
MD5 d3918029d07fd9c30ebd70b5da57c07e
.rdata 42496 bytes · 15.5% of section data
MD5 ee3e41c818cba45d4dde2e659c34f927
.data 7680 bytes · 2.8% of section data
MD5 55033768a62d19efc3b7e62b470d3d28
.rsrc 10752 bytes · 3.9% of section data
MD5 6d6df91f2f35cfde5f45f92e1c0aaa76
.reloc 15360 bytes · 5.6% of section data
MD5 cd529572c34169f1c5fd794a9ca8cd74

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