GridinSoft Threat Intelligence
FD4123B1-314F-4854-BCEA-A213C91C66E5.2.9.0.10.dll file report
Why it matters
Evidence available for this file
No final classification is available yet.
First seen 2023-05-09 23:41:48 (3 years ago); latest analysis 2023-05-09 23:41:48 (3 years ago).
Company metadata: Corel Corporation. Product metadata: FD4123B1-314F-4854-BCEA-A213C91C66E5.
Signed by Corel Corporation. The signature is reported as valid, but signed files can still be bundled or abused.
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
- Use the hash and metadata below to verify the exact file identity.
- Review publisher, signature, paths, and PE details for inconsistencies.
- Run a local scan if the file appears unexpectedly or starts with Windows.
File context
FD4123B1-314F-4854-BCEA-A213C91C66E5.2.9.0.10.dll is a Windows file recorded in the ThreatInfo database. It is associated with FD4123B1-314F-4854-BCEA-A213C91C66E5. The reported company name is Corel Corporation. The current detection status is Undefined, based on the latest analysis from 2023-05-09 23:41:48 (3 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.
File Details
| Product Name: | FD4123B1-314F-4854-BCEA-A213C91C66E5 |
| Company Name: | Corel Corporation |
| MD5: | b4893ff1ac0bcfa60d03c297568d3f46 |
| Size: | 234 KB |
| First Published: | 2023-05-09 23:41:48 (3 years ago) |
| Latest Published: | 2023-05-09 23:41:48 (3 years ago) |
| Status: | Undefined (on last analysis) | |
| Analysis Date: | 2023-05-09 23:41:48 (3 years ago) |
Overview
| Signed By: | Corel Corporation |
| Status: | Valid |
The signature on FD4123B1-314F-4854-BCEA-A213C91C66E5.2.9.0.10.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:
| %programfiles%\winzip smart monitor\plugins |
ThreatInfo has observed FD4123B1-314F-4854-BCEA-A213C91C66E5.2.9.0.10.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.
Geographic signal
Observed country distribution
ThreatInfo has seen FD4123B1-314F-4854-BCEA-A213C91C66E5.2.9.0.10.dll across 1 countries. Use this signal to compare local evidence with where the sample is most often reported.
The strongest geographic signal for this file is Switzerland with 100.0% of observed hits. Geographic distribution can help identify targeted campaigns, regional software bundles, or where a file is most commonly reported.
OS Version:
The most common operating system signal for FD4123B1-314F-4854-BCEA-A213C91C66E5.2.9.0.10.dll is Windows 7 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.
Analysis
FD4123B1-314F-4854-BCEA-A213C91C66E5.2.9.0.10.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.
PE Sections:
Section layout highlights raw-size concentration, repeated names, packer markers, and hashes that can be compared across related samples.
7cb82a28ead9e02941cd66f549c5f00d
d897333dfdcec39aca28c7fbd8abd102
9c51b81cc2427ce4fc6f6907f73a0a5d
452039c9ac1e2aee8fab14ca95913b08
bf3487f2ed69fc0c48dd97db85989aff
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.