GridinSoft Threat Intelligence

pdf.dll file report

Clean record File reputation report
MD5 fc59131e7db17aee3c326e63502d3e16
Latest seen 2024-03-22 23:01:10 (2 years ago)
First seen 2017-09-04 17:06:37 (8 years ago)
Size 3 MB
Product Chrome PDF Viewer
Signed by Google Inc

Why it matters

Evidence available for this file

Detection

Latest status is clean for this hash.

Timeline

First seen 2017-09-04 17:06:37 (8 years ago); latest analysis 2024-03-22 23:01:10 (2 years ago).

Publisher context

Product metadata: Chrome PDF Viewer.

Digital signature

Signed by Google Inc. The signature is reported as valid, but signed files can still be bundled or abused.

Aliases

This hash has appeared under multiple file names, which can happen with repackaging, bundling, or deliberate renaming.

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.

File context

pdf.dll is a Windows file recorded in the ThreatInfo database. It is associated with Chrome PDF Viewer. The current detection status is Clean, based on the latest analysis from 2024-03-22 23:01:10 (2 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.

File Details

Product Name: Chrome PDF Viewer
MD5: fc59131e7db17aee3c326e63502d3e16
Size: 3 MB
First Published: 2017-09-04 17:06:37 (8 years ago)
Latest Published: 2024-03-22 23:01:10 (2 years ago)
Status: Clean (on last analysis)
Analysis Date: 2024-03-22 23:01:10 (2 years ago)

Overview

Signed By: Google Inc
Status: Valid

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

Common Places:

%localappdata%\idlecrawler\chrome-bin\31.0.1650.63
%localappdata%\sogouexplorer\5.0.10.13455

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

File Names:

2 observed names
pdf(42).dll pdf.dll

This hash has been seen with multiple file names. Alternate names can appear when software is updated, copied between folders, packed by an installer, or deliberately renamed to avoid recognition. Compare the exact MD5 above before assuming two names refer to the same file.

Geographic signal

Observed country distribution

ThreatInfo has seen pdf.dll across 2 countries. Use this signal to compare local evidence with where the sample is most often reported.

Top country United States
Share 66.7%
Low High activity

The strongest geographic signal for this file is United States with 66.7% of observed hits. Geographic distribution can help identify targeted campaigns, regional software bundles, or where a file is most commonly reported.

OS Version:

Windows 7 33.3%
Windows 10 33.3%
Windows 8.1 33.3%

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

pdf.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 0x002164c5
Image base 0x10000000

PE Sections:

Sections 6
Raw data 4048384

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

.text 2371072 bytes · 58.6% of section data
MD5 2c4eb001e89ef5af61d791ba8d8cbf27
.rdata 1524224 bytes · 37.7% of section data
MD5 6e704424cea99972332c444eb3781334
.data 43008 bytes · 1.1% of section data
MD5 b3608d770e2bcca07ef66e15345f2488
.tls 512 bytes · 0.0% of section data
MD5 bf619eac0cdf3f68d496ea9344137e8b
.rsrc 1536 bytes · 0.0% of section data
MD5 a862c97c0a44273d5dc90a315669c047
.reloc 108032 bytes · 2.7% of section data
MD5 18932e774692ca2842cfda2c581a1861

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