GridinSoft Threat Intelligence

Microsoft.Ink.dll file report

Under review File reputation report
MD5 a02ee61542caae25f8a44c9428d30247
Latest seen 2023-02-23 23:54:52 (3 years ago)
First seen 2017-07-25 10:15:49 (8 years ago)
Size 504 KB

Why it matters

Evidence available for this file

Detection

No final classification is available yet.

Timeline

First seen 2017-07-25 10:15:49 (8 years ago); latest analysis 2023-02-23 23:54:52 (3 years ago).

Publisher context

Company metadata: Microsoft Corporation. Product metadata: Microsoft (R) Windows (R) Operating System.

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. Use the hash and metadata below to verify the exact file identity.
  2. Review publisher, signature, paths, and PE details for inconsistencies.
  3. Run a local scan if the file appears unexpectedly or starts with Windows.

Microsoft.Ink.dll is a Windows file recorded in the ThreatInfo database. It is associated with Microsoft (R) Windows (R) Operating System. The reported company name is Microsoft Corporation. The current detection status is Undefined, based on the latest analysis from 2023-02-23 23:54:52 (3 years ago).

ThreatInfo does not have a final classification for this file yet. Use the technical details below to compare the hash, size, signature, and observed locations with the copy found on your device.

Product Name: Microsoft (R) Windows (R) Operating System
Company Name: Microsoft Corporation
MD5: a02ee61542caae25f8a44c9428d30247
Size: 504 KB
First Published: 2017-07-25 10:15:49 (8 years ago)
Latest Published: 2023-02-23 23:54:52 (3 years ago)
Status: Undefined (on last analysis)
Analysis Date: 2023-02-23 23:54:52 (3 years ago)
%programfiles%\fileviewpro
%sysdrive%\\program files (x86)\common files\microsoft shared\ink\1.7
%programfiles%
%programfiles%\software\note5\note5_5.1.4.36469

ThreatInfo has observed Microsoft.Ink.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 7 51.2%
Windows 10 40.5%
Windows 8.1 6.0%
Windows XP 2.4%

The most common operating system signal for Microsoft.Ink.dll is Windows 7 with 51.2% 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.

Microsoft.Ink.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 0x0007ccde
Image base 0x01000000

.NET Info:

MVID: 93565283-4ffa-40d5-8e7c-3ce2e721e336

PE Sections:

Sections 3
Raw data 512000

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

.text 503808 bytes · 98.4% of section data
MD5 cf611e6652b311abb4f978ce885d6f5f
.rsrc 4096 bytes · 0.8% of section data
MD5 f8bb873a2b93c93349f71d87b7a3e5b9
.reloc 4096 bytes · 0.8% of section data
MD5 45670b941618bc9c51919907c0e5ffab

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 file is still under review

ThreatInfo has not assigned a final verdict yet. Compare the file hash, location, signature, and publisher before trusting the file on a production system.

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 a02ee61542caae25f8a44c9428d30247.
  • 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.