GridinSoft Threat Intelligence

networkcore.dll file report

Under review File reputation report
MD5 fc8ff7381d0396315b56ddb69d7b6881
Latest seen 2024-08-10 23:02:26 (2 years ago)
First seen 2024-08-10 23:02:26 (2 years ago)
Size 2 MB
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.

networkcore.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: fc8ff7381d0396315b56ddb69d7b6881
Size: 2 MB
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 networkcore.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%\fastpdf\update\cm

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

networkcore.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 0x001e0054
Image base 0x10000000

PE Sections:

Sections 5
Raw data 2953216

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

.text 2179072 bytes · 73.8% of section data
MD5 282c13691f7accd3c917589f924009b6
.rdata 607232 bytes · 20.6% of section data
MD5 a3d88abe50cc18816a849f737b125301
.data 67072 bytes · 2.3% of section data
MD5 8bdbe5771996491f201666cf216527c2
.rsrc 1024 bytes · 0.0% of section data
MD5 717437f545839e235085b90b3a2cfe7e
.reloc 98816 bytes · 3.3% of section data
MD5 f942e06ba34171546db7b6efe3c225eb

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