GridinSoft Threat Intelligence

Xceed.Wpf.AvalonDock.resources.dll file report

Under review File reputation report
MD5 04d1bf1e07f8e67f28b118b4f7ab9236
Latest seen 2024-01-02 23:37:58 (2 years ago)
First seen 2019-08-13 16:39:39 (6 years ago)
Size 6 KB

Why it matters

Evidence available for this file

Detection

No final classification is available yet.

Timeline

First seen 2019-08-13 16:39:39 (6 years ago); latest analysis 2024-01-02 23:37:58 (2 years ago).

Publisher context

Company metadata: Xceed Software Inc.. Product metadata: Xceed Toolkit for WPF - AvalonDock.

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.

Xceed.Wpf.AvalonDock.resources.dll is a Windows file recorded in the ThreatInfo database. It is associated with Xceed Toolkit for WPF - AvalonDock. The reported company name is Xceed Software Inc.. The current detection status is Undefined, based on the latest analysis from 2024-01-02 23:37:58 (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: Xceed Toolkit for WPF - AvalonDock
Company Name: Xceed Software Inc.
MD5: 04d1bf1e07f8e67f28b118b4f7ab9236
Size: 6 KB
First Published: 2019-08-13 16:39:39 (6 years ago)
Latest Published: 2024-01-02 23:37:58 (2 years ago)
Status: Undefined (on last analysis)
Analysis Date: 2024-01-02 23:37:58 (2 years ago)
%programfiles%\free youtube downloader

ThreatInfo has observed Xceed.Wpf.AvalonDock.resources.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.

14.3%
14.3%
7.1%
7.1%
7.1%
7.1%
7.1%
7.1%
7.1%
7.1%
7.1%
7.1%

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

Windows 10 78.6%
Windows 7 21.4%

The most common operating system signal for Xceed.Wpf.AvalonDock.resources.dll is Windows 10 with 78.6% 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.

Xceed.Wpf.AvalonDock.resources.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 0x00002dce
Image base 0x10000000

.NET Info:

MVID: f6e75e0c-84d5-4a7a-9764-27d3979f08e6

PE Sections:

Sections 3
Raw data 5632

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

.text 3584 bytes · 63.6% of section data
MD5 87e010702bc394b731f37cebe7f5d538
.rsrc 1536 bytes · 27.3% of section data
MD5 dcf19fe3204082ccd27ad9a0cbd1d9f0
.reloc 512 bytes · 9.1% of section data
MD5 e40891c61e5ea9fd695831faae64401f

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 04d1bf1e07f8e67f28b118b4f7ab9236.
  • 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.