GridinSoft Threat Intelligence

OEMUninstall.dll file report

Clean record File reputation report
MD5 899d382f43b5a20ab92c4b8fb52c6247
Latest seen 2021-12-26 21:17:57 (4 years ago)
First seen 2021-08-05 20:22:45 (4 years ago)
Size 442 KB
Signed by Bitdefender SRL

Why it matters

Evidence available for this file

Detection

Latest status is clean for this hash.

Timeline

First seen 2021-08-05 20:22:45 (4 years ago); latest analysis 2021-12-26 21:17:57 (4 years ago).

Publisher context

Company metadata: BitdefenderlDFileDesc. Product metadata: Bitdefender SecurityDVarFileInfo$.

Digital signature

Signed by Bitdefender SRL. 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.

OEMUninstall.dll is a Windows file recorded in the ThreatInfo database. It is associated with Bitdefender SecurityDVarFileInfo$. The reported company name is BitdefenderlDFileDesc. The current detection status is Clean, based on the latest analysis from 2021-12-26 21:17:57 (4 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: Bitdefender SecurityDVarFileInfo$
Company Name: BitdefenderlDFileDesc
MD5: 899d382f43b5a20ab92c4b8fb52c6247
Size: 442 KB
First Published: 2021-08-05 20:22:45 (4 years ago)
Latest Published: 2021-12-26 21:17:57 (4 years ago)
Status: Clean (on last analysis)
Analysis Date: 2021-12-26 21:17:57 (4 years ago)
Signed By: Bitdefender SRL
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.

%commonappdata%\bromium\bem

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

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

OEMUninstall.dll is identified as pe for 64-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 64-bit
Subsystem Windows GUI
Entry point 0x0001b084
Image base 0x0000000180000000

PE Sections:

Sections 6
Raw data 429056

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

.text 280064 bytes · 65.3% of section data
MD5 25cdd8cffc3dbaecfdc855f1ae82d2bb
.rdata 123904 bytes · 28.9% of section data
MD5 b3964c8c77373968fdcbdac369597efb
.data 5120 bytes · 1.2% of section data
MD5 826e6d9dac65268411d09cda2ab078a4
.pdata 14848 bytes · 3.5% of section data
MD5 184574b36c5b5f7abda8360ebeb6fee7
.rsrc 1536 bytes · 0.4% of section data
MD5 782bd42be5152ba9187dfe4ed1cabd26
.reloc 3584 bytes · 0.8% of section data
MD5 4eb0ffbbff3debfa3bdb03dc57162188

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 899d382f43b5a20ab92c4b8fb52c6247.
  • 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.