GridinSoft Threat Intelligence

font_recognize.dll file report

Under review File reputation report
MD5 b20e2a02fcf8e20157a25cbaa09e00ba
Latest seen 2024-08-10 23:02:26 (2 years ago)
First seen 2024-08-10 23:02:26 (2 years ago)
Size 102 KB
Product PDF阅读器

Why it matters

Evidence available for this file

Detection

No final classification is available yet.

Timeline

First seen 2024-08-10 23:02:26 (2 years ago); latest analysis 2024-08-10 23:02:26 (2 years ago).

Publisher context

Company metadata: 茉柏枘(上海)软件科技有限公司. Product metadata: PDF阅读器.

Digital signature

Signed by 茉柏枘(上海)软件科技有限公司. 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. 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.

font_recognize.dll is a Windows file recorded in the ThreatInfo database. It is associated with PDF阅读器. The reported company name is 茉柏枘(上海)软件科技有限公司. The current detection status is Undefined, based on the latest analysis from 2024-08-10 23:02:26 (2 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: PDF阅读器
Company Name: 茉柏枘(上海)软件科技有限公司
MD5: b20e2a02fcf8e20157a25cbaa09e00ba
Size: 102 KB
First Published: 2024-08-10 23:02:26 (2 years ago)
Latest Published: 2024-08-10 23:02:26 (2 years ago)
Status: Undefined (on last analysis)
Analysis Date: 2024-08-10 23:02:26 (2 years ago)

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

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

font_recognize.dll is identified as pe for 32-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 32-bit
Subsystem Windows GUI
Entry point 0x00002754
Image base 0x10000000

PE Sections:

Sections 5
Raw data 84992

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

.text 51712 bytes · 60.8% of section data
MD5 a8ec67ff59d92b4e341afe8b8e09128f
.rdata 25600 bytes · 30.1% of section data
MD5 b73e93cc01ae79cdeaf53c77aee18879
.data 2560 bytes · 3.0% of section data
MD5 a5abb5d91c6c7e4edf1d045f77fe81ac
.rsrc 1024 bytes · 1.2% of section data
MD5 4020e8aa18d78ff8267a7985e8faff57
.reloc 4096 bytes · 4.8% of section data
MD5 3074d3395de8200941b937937a76f020

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