GridinSoft Threat Intelligence

kofficeaddin.dll file report

Under review File reputation report
MD5 6da1f8fd8b407537f051f6c98c0bdc43
Latest seen 2024-08-10 23:02:28 (2 years ago)
First seen 2024-08-10 23:02:28 (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:28 (2 years ago); latest analysis 2024-08-10 23:02:28 (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.

kofficeaddin.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:28 (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: 6da1f8fd8b407537f051f6c98c0bdc43
Size: 2 MB
First Published: 2024-08-10 23:02:28 (2 years ago)
Latest Published: 2024-08-10 23:02:28 (2 years ago)
Status: Undefined (on last analysis)
Analysis Date: 2024-08-10 23:02:28 (2 years ago)

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

kofficeaddin.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 0x000aa295
Image base 0x10000000

PE Sections:

Sections 5
Raw data 2134016

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

.text 896000 bytes · 42.0% of section data
MD5 870b970ad3c826ae103c56a066b63b74
.rdata 190464 bytes · 8.9% of section data
MD5 05c79c38a60096a2bcf399f59599ae8c
.data 22528 bytes · 1.1% of section data
MD5 0d25da94af437022d55e3a602f4fc46e
.rsrc 976384 bytes · 45.8% of section data
MD5 e0eb756c03c67e57b69802245b70de3f
.reloc 48640 bytes · 2.3% of section data
MD5 c23f12b76e1552b3db9f465d5b02ed00

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 6da1f8fd8b407537f051f6c98c0bdc43.
  • 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.