GridinSoft Threat Intelligence

System.ComponentModel.Composition.Registration.dll file report

Under review File reputation report
MD5 aff4faf177f73d0e257b544538bddcca
Latest seen 2026-01-31 23:01:23 (4 months ago)
First seen 2020-10-15 13:36:10 (5 years ago)
Size 35 KB

Why it matters

Evidence available for this file

Detection

No final classification is available yet.

Timeline

First seen 2020-10-15 13:36:10 (5 years ago); latest analysis 2026-01-31 23:01:23 (4 months ago).

Publisher context

Company metadata: Microsoft Corporation. Product metadata: Microsoft® .NET Core.

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.ComponentModel.Composition.Registration.dll is a Windows file recorded in the ThreatInfo database. It is associated with Microsoft® .NET Core. The reported company name is Microsoft Corporation. The current detection status is Undefined, based on the latest analysis from 2026-01-31 23:01:23 (4 months 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: Microsoft® .NET Core
Company Name: Microsoft Corporation
MD5: aff4faf177f73d0e257b544538bddcca
Size: 35 KB
First Published: 2020-10-15 13:36:10 (5 years ago)
Latest Published: 2026-01-31 23:01:23 (4 months ago)
Status: Undefined (on last analysis)
Analysis Date: 2026-01-31 23:01:23 (4 months ago)
%programfiles%

ThreatInfo has observed System.ComponentModel.Composition.Registration.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 89.9%
Windows 7 7.0%
Windows 8.1 1.7%
Windows Vista 0.3%
Windows Server 2008 R2 0.3%
Windows Server 2012 R2 0.3%
Windows Embedded 8.1 0.3%

The most common operating system signal for System.ComponentModel.Composition.Registration.dll is Windows 10 with 89.9% 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.ComponentModel.Composition.Registration.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 0x0000a2ae
Image base 0x00400000

.NET Info:

MVID: 79d6fc6e-91a0-4fd9-9581-20c6cfb2a92c

PE Sections:

Sections 3
Raw data 35840

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

.text 33792 bytes · 94.3% of section data
MD5 b65b29df1c50c8ddbc2471d2b90df270
.rsrc 1536 bytes · 4.3% of section data
MD5 378a6cc98b9f62b0df15bc3b57b4b1f7
.reloc 512 bytes · 1.4% of section data
MD5 5b7836c1c73c1af289341b04a8f9d956

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