GridinSoft Threat Intelligence

em002_32.dll.raw file report

Clean record File reputation report
MD5 2f3bb2fd5de76fa4bdedcf4fcdc4e619
Latest seen 2024-09-20 23:09:21 (2 years ago)
First seen 2024-09-20 23:09:21 (2 years ago)
Size 120 MB
Publisher ESET
Product ESET Security
Signed by ESET, spol. s r.o.

Why it matters

Evidence available for this file

Detection

Latest status is clean for this hash.

Timeline

First seen 2024-09-20 23:09:21 (2 years ago); latest analysis 2024-09-20 23:09:21 (2 years ago).

Publisher context

Company metadata: ESET. Product metadata: ESET Security.

Digital signature

Signed by ESET, spol. s r.o.. ThreatInfo marks this publisher as trusted for this record.

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. Confirm the hash and publisher match the expected software.
  2. Review the observed locations and signature information below.
  3. Rescan if the file was downloaded from an unknown source or appears in an unusual path.

em002_32.dll.raw is a Windows file recorded in the ThreatInfo database. It is associated with ESET Security. The reported company name is ESET. The current detection status is Clean, based on the latest analysis from 2024-09-20 23:09:21 (2 years ago).

This record is currently marked as clean, but file reputation can depend on the exact path, hash, and source. Compare the MD5 and publisher data below with the file on your system.

Product Name: ESET Security
Company Name: ESET
MD5: 2f3bb2fd5de76fa4bdedcf4fcdc4e619
Size: 120 MB
First Published: 2024-09-20 23:09:21 (2 years ago)
Latest Published: 2024-09-20 23:09:21 (2 years ago)
Status: Clean (on last analysis)
Analysis Date: 2024-09-20 23:09:21 (2 years ago)
Signed By: ESET, spol. s r.o.
Status: Trusted Publisher

ThreatInfo marks this publisher as trusted for this record, but the file hash and source should still match the expected software distribution.

%localappdata%\eset\esetonlinescanner\modules\em002_32

ThreatInfo has observed em002_32.dll.raw 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 em002_32.dll.raw 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.

em002_32.dll.raw 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 0x001d5080
Image base 0x10000000

PE Sections:

Sections 5
Raw data 125901312

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

.text 1937408 bytes · 1.5% of section data
MD5 4ca6b83a3194260f9193ce36e120008f
.rdata 284160 bytes · 0.2% of section data
MD5 9524c8360a6d199d4da616c1c4ef3ed5
.data 512 bytes · 0.0% of section data
MD5 33dc062869f6f109b6f14be0fb416273
.rsrc 123624960 bytes · 98.2% of section data
Large raw data
MD5 7c8a214a6f8204b80bd8b355c48ff6b3
.reloc 54272 bytes · 0.0% of section data
MD5 d8aab6241762aff4e8ca69ecfccaa5a9

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 hash is currently recorded as clean

Use the MD5, publisher, signature, and observed paths in this report to verify that the file on your device is the same copy described here.

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 2f3bb2fd5de76fa4bdedcf4fcdc4e619.
  • 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.