GridinSoft Threat Intelligence

unicows.dll file report

Clean record File reputation report
MD5 2d2f84761a9fde81898ed505b227e7e3
Latest seen 2021-01-09 16:34:39 (5 years ago)
First seen 2017-09-15 18:07:28 (8 years ago)
Size 239 KB

Why it matters

Evidence available for this file

Detection

Latest status is clean for this hash.

Timeline

First seen 2017-09-15 18:07:28 (8 years ago); latest analysis 2021-01-09 16:34:39 (5 years ago).

Digital signature

Signed by Microsoft Corporation. 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. 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.

unicows.dll is a Windows file recorded in the ThreatInfo database. It is associated with Microsoft (R) Windows (R) 95, Windows (R) 98, and Windows (R) Millennium Operating Systems. The reported company name is Microsoft Corporation. The current detection status is Clean, based on the latest analysis from 2021-01-09 16:34:39 (5 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: Microsoft (R) Windows (R) 95, Windows (R) 98, and Windows (R) Millennium Operating Systems
Company Name: Microsoft Corporation
MD5: 2d2f84761a9fde81898ed505b227e7e3
Size: 239 KB
First Published: 2017-09-15 18:07:28 (8 years ago)
Latest Published: 2021-01-09 16:34:39 (5 years ago)
Status: Clean (on last analysis)
Analysis Date: 2021-01-09 16:34:39 (5 years ago)
Signed By: Microsoft Corporation
Status: Valid

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

%programfiles%\drivertoolkit\download\1d1b7df7d04424705ce2076809d75337\$_outdir\bin
%programfiles%\cat4cad\plugins\jre6\bin
%programfiles%\rational_service5\dwjava\java6u14
%programfiles%\bentley\powercivil v8i (selectseries 3)\powercivil\inroadsgroup\qm\classes\javarun
%programfiles%\juriafrica\jre

ThreatInfo has observed unicows.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 60.0%
Windows 7 40.0%

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

unicows.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 0x0000e122
Image base 0x7f2d0000

PE Sections:

Sections 4
Raw data 237568

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

.text 221184 bytes · 93.1% of section data
MD5 5022c065adbdd419d9cac92aa36a6117
.data 512 bytes · 0.2% of section data
MD5 84ca464d9195c785e75df0ebf9ed4305
.rsrc 1536 bytes · 0.6% of section data
MD5 8dce8884b9853ef812becc96ab0def1d
.reloc 14336 bytes · 6.0% of section data
MD5 40f16d663d498e6e08f50ca571ef900d

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