GridinSoft Threat Intelligence
libiomp5md.dll file report
Why it matters
Evidence available for this file
Latest status is clean for this hash.
First seen 2025-12-14 23:00:50 (5 months ago); latest analysis 2025-12-14 23:00:52 (5 months ago).
Company metadata: Intel Corporation. Product metadata: Intel(R) OpenMP* Runtime Library.
Signed by Intel(R) Software Development Products. ThreatInfo marks this publisher as trusted for this record.
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
- Confirm the hash and publisher match the expected software.
- Review the observed locations and signature information below.
- Rescan if the file was downloaded from an unknown source or appears in an unusual path.
File context
libiomp5md.dll is a Windows file recorded in the ThreatInfo database. It is associated with Intel(R) OpenMP* Runtime Library. The reported company name is Intel Corporation. The current detection status is Clean, based on the latest analysis from 2025-12-14 23:00:52 (5 months 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.
File Details
| Product Name: | Intel(R) OpenMP* Runtime Library |
| Company Name: | Intel Corporation |
| MD5: | 0eabcf99049b7e48d364d40e60f49cb9 |
| Size: | 1 MB |
| First Published: | 2025-12-14 23:00:50 (5 months ago) |
| Latest Published: | 2025-12-14 23:00:52 (5 months ago) |
| Status: | Clean (on last analysis) | |
| Analysis Date: | 2025-12-14 23:00:52 (5 months ago) |
Overview
| Signed By: | Intel(R) Software Development Products |
| 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.
Common Places:
| %sysdrive%\visual studio 2017\projects\control\ramanview_new\packages\mathnet.numerics.mkl.win.2.3.0\build |
| %sysdrive%\visual studio 2017\projects\control\raman_view\packages\mathnet.numerics.mkl.win.2.3.0\build |
| %sysdrive%\visual studio 2017\projects\control\ramanview_new_main\bin\debug |
| %sysdrive%\visual studio 2017\projects\control\raman_view64\bin\debug |
| %sysdrive%\visual studio 2017\projects\control\ramanview_new\bin\debug |
| %sysdrive%\visual studio 2017\projects\control\raman_view\bin\debug |
ThreatInfo has observed libiomp5md.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.
Geographic signal
Observed country distribution
ThreatInfo has seen libiomp5md.dll across 1 countries. Use this signal to compare local evidence with where the sample is most often reported.
The strongest geographic signal for this file is Italy with 100.0% of observed hits. Geographic distribution can help identify targeted campaigns, regional software bundles, or where a file is most commonly reported.
OS Version:
The most common operating system signal for libiomp5md.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.
Analysis
libiomp5md.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.
PE Sections:
Section layout highlights raw-size concentration, repeated names, packer markers, and hashes that can be compared across related samples.
066067072e5b45233e3ceba63e89099c
8b042058df93cf0df13dd794ef9088d2
cd0dd182572acd170886b805d8f7d4b0
b62f92440cb3cef698081d425776b999
0f4202f555f1a32b884b64298525afa5
2903e3c5c7075284f5fc12533e2a5c38
302de3df282cb6efe276b2081745dd70
298cc87d53000774197572f8de75e20d
729bf49b50650d9e3b9186d1960d6267
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.