GridinSoft Threat Intelligence

WXFCNVP.dll file report

Under review File reputation report
MD5 3598be56726ccc94cd1b27bc34eb1473
Latest seen 2021-01-13 18:33:19 (5 years ago)
First seen 2021-01-13 18:33:19 (5 years ago)
Size 35 KB
Publisher WinZip Computing
Product WXFCNVP
Signed by Corel Corporation

Why it matters

Evidence available for this file

Detection

No final classification is available yet.

Timeline

First seen 2021-01-13 18:33:19 (5 years ago); latest analysis 2021-01-13 18:33:19 (5 years ago).

Publisher context

Company metadata: WinZip Computing. Product metadata: WXFCNVP.

Digital signature

Signed by Corel Corporation. 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.

WXFCNVP.dll is a Windows file recorded in the ThreatInfo database. It is associated with WXFCNVP. The reported company name is WinZip Computing. The current detection status is Undefined, based on the latest analysis from 2021-01-13 18:33:19 (5 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: WXFCNVP
Company Name: WinZip Computing
MD5: 3598be56726ccc94cd1b27bc34eb1473
Size: 35 KB
First Published: 2021-01-13 18:33:19 (5 years ago)
Latest Published: 2021-01-13 18:33:19 (5 years ago)
Status: Undefined (on last analysis)
Analysis Date: 2021-01-13 18:33:19 (5 years ago)
Signed By: Corel Corporation
Status: Valid

The signature on WXFCNVP.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%\windowsapps

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

WXFCNVP.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 0x00006d4a
Image base 0x10000000

.NET Info:

MVID: 65a1daea-c1e9-4520-8024-7df7993908d7
Typelib ID: 020cadab-9056-426e-b2a9-601c51f62ed3

PE Sections:

Sections 3
Raw data 22528

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

.text 19968 bytes · 88.6% of section data
MD5 3342cb1293f0010724064e8ad638a45e
.rsrc 2048 bytes · 9.1% of section data
MD5 74fc255fde26e3ccad226161491fc18f
.reloc 512 bytes · 2.3% of section data
MD5 962915cfee1d0c4f4c745b6168e745a4

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 3598be56726ccc94cd1b27bc34eb1473.
  • 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.