GridinSoft Threat Intelligence

Prism.DryIoc.Wpf.dll file report

Under review File reputation report
MD5 94f98a3d52419a5e363ea4b73b1a3221
Latest seen 2025-01-13 23:01:22 (a year ago)
First seen 2024-06-25 23:02:36 (2 years ago)
Size 26 KB

Why it matters

Evidence available for this file

Detection

No final classification is available yet.

Timeline

First seen 2024-06-25 23:02:36 (2 years ago); latest analysis 2025-01-13 23:01:22 (a year ago).

Publisher context

Company metadata: Brian Lagunas;Dan Siegel. Product metadata: Prism.DryIoc.Wpf (net461).

Digital signature

Signed by Prism (.NET Foundation). 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.

Prism.DryIoc.Wpf.dll is a Windows file recorded in the ThreatInfo database. It is associated with Prism.DryIoc.Wpf (net461). The reported company name is Brian Lagunas;Dan Siegel. The current detection status is Undefined, based on the latest analysis from 2025-01-13 23:01:22 (a year 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: Prism.DryIoc.Wpf (net461)
Company Name: Brian Lagunas;Dan Siegel
MD5: 94f98a3d52419a5e363ea4b73b1a3221
Size: 26 KB
First Published: 2024-06-25 23:02:36 (2 years ago)
Latest Published: 2025-01-13 23:01:22 (a year ago)
Status: Undefined (on last analysis)
Analysis Date: 2025-01-13 23:01:22 (a year ago)
Signed By: Prism (.NET Foundation)
Status: Valid

The signature on Prism.DryIoc.Wpf.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%\hofmann\hofmann

ThreatInfo has observed Prism.DryIoc.Wpf.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 Prism.DryIoc.Wpf.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.

Prism.DryIoc.Wpf.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 0x00005dd6
Image base 0x10000000

.NET Info:

MVID: 686f6fb5-a82f-4631-8692-a6c2e4142083

PE Sections:

Sections 3
Raw data 17920

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

.text 15872 bytes · 88.6% of section data
MD5 b73db19c73aacc4d9da7bcdc45e43188
.rsrc 1536 bytes · 8.6% of section data
MD5 37fe5f553dc8ba3d4989c6d81b4de56f
.reloc 512 bytes · 2.9% of section data
MD5 3b9194dbf1e87015aa1d9aefa7b9c846

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 94f98a3d52419a5e363ea4b73b1a3221.
  • 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.