GridinSoft Threat Intelligence

OsDiag.dll file report

Clean record File reputation report
MD5 3db61fc8363edcccad6420cb7af7d226
Latest seen 2022-01-25 21:25:33 (4 years ago)
First seen 2022-01-07 21:10:03 (4 years ago)
Size 53 KB
Product OsDiag

Why it matters

Evidence available for this file

Detection

Latest status is clean for this hash.

Timeline

First seen 2022-01-07 21:10:03 (4 years ago); latest analysis 2022-01-25 21:25:33 (4 years ago).

Publisher context

Product metadata: OsDiag.

Digital signature

Signed by Lenovo (Beijing) Limited. 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.

OsDiag.dll is a Windows file recorded in the ThreatInfo database. It is associated with OsDiag. The current detection status is Clean, based on the latest analysis from 2022-01-25 21:25:33 (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: OsDiag
MD5: 3db61fc8363edcccad6420cb7af7d226
Size: 53 KB
First Published: 2022-01-07 21:10:03 (4 years ago)
Latest Published: 2022-01-25 21:25:33 (4 years ago)
Status: Clean (on last analysis)
Analysis Date: 2022-01-25 21:25:33 (4 years ago)
Signed By: Lenovo (Beijing) Limited
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%\programs\lenovo

ThreatInfo has observed OsDiag.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 OsDiag.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.

OsDiag.dll 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 0x0001200a
Image base 0x10000000

.NET Info:

MVID: 31fba038-406b-4050-a2d7-08066bef6e75
Typelib ID: c2e10f5d-f160-4470-87c4-954395943d36

PE Sections:

Sections 5
Raw data 46592

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

Afqa2n\ 22528 bytes · 48.4% of section data
Uncommon name
MD5 a0adbfcd188933eaf889c1f0a03a21d1
.text 22016 bytes · 47.3% of section data
MD5 756961cfe514fbd941fa09ca4f53c425
.rsrc 1024 bytes · 2.2% of section data
MD5 93c1b9f60e5c0e48bac02728cdfb23fe
.reloc 512 bytes · 1.1% of section data
MD5 a907a191d8b52617c22703e19088fd22
512 bytes · 1.1% of section data
Uncommon name
MD5 e167b2d39908a16751676467ae79bed1

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 3db61fc8363edcccad6420cb7af7d226.
  • 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.