GridinSoft Threat Intelligence

System.Windows.Interactivity.resources.dll file report

Under review File reputation report
MD5 ef7ea257baca1c4515e50a17284d7339
Latest seen 2021-12-06 21:54:47 (4 years ago)
First seen 2017-08-08 18:04:21 (8 years ago)
Size 6 KB

Why it matters

Evidence available for this file

Detection

No final classification is available yet.

Timeline

First seen 2017-08-08 18:04:21 (8 years ago); latest analysis 2021-12-06 21:54:47 (4 years ago).

Publisher context

Company metadata: Microsoft Corporation. Product metadata: System.Windows.Interactivity.

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.

System.Windows.Interactivity.resources.dll is a Windows file recorded in the ThreatInfo database. It is associated with System.Windows.Interactivity. The reported company name is Microsoft Corporation. The current detection status is Undefined, based on the latest analysis from 2021-12-06 21:54:47 (4 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: System.Windows.Interactivity
Company Name: Microsoft Corporation
MD5: ef7ea257baca1c4515e50a17284d7339
Size: 6 KB
First Published: 2017-08-08 18:04:21 (8 years ago)
Latest Published: 2021-12-06 21:54:47 (4 years ago)
Status: Undefined (on last analysis)
Analysis Date: 2021-12-06 21:54:47 (4 years ago)
%programfiles%\iminent\fr
%localappdata%\cdiscount\cdiscount cloud\bin\fr
%localappdata%\cdiscount\cdiscount cloud\bin
%programfiles%\iminent

ThreatInfo has observed System.Windows.Interactivity.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.

Windows 7 72.4%
Windows 10 24.1%
Windows Vista 3.4%

The most common operating system signal for System.Windows.Interactivity.resources.dll is Windows 7 with 72.4% 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.

System.Windows.Interactivity.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 0x00002ebe
Image base 0x00400000

.NET Info:

MVID: be50b757-bef9-4b24-9eff-c06bb806a346

PE Sections:

Sections 3
Raw data 6144

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

.text 4096 bytes · 66.7% of section data
MD5 665e07048c809ce7c8e34aa1644fe72e
.rsrc 1536 bytes · 25.0% of section data
MD5 b31097bb31af2dc48244e5dc38171e0b
.reloc 512 bytes · 8.3% of section data
MD5 8d6eb4cb1af45cd1d88040a139ba4a33

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 ef7ea257baca1c4515e50a17284d7339.
  • 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.