GridinSoft Threat Intelligence

MahApps.Metro.IconPacks.Unicons.dll file report

Under review File reputation report
MD5 f3bf5f2817e44c4ccd3d992cf4f78091
Latest seen 2026-02-18 23:01:02 (3 months ago)
First seen 2021-06-04 20:54:31 (4 years ago)
Size 1 MB
Publisher MahApps

Why it matters

Evidence available for this file

Detection

No final classification is available yet.

Timeline

First seen 2021-06-04 20:54:31 (4 years ago); latest analysis 2026-02-18 23:01:02 (3 months ago).

Publisher context

Company metadata: MahApps. Product metadata: MahApps.Metro.IconPacks.

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.

MahApps.Metro.IconPacks.Unicons.dll is a Windows file recorded in the ThreatInfo database. It is associated with MahApps.Metro.IconPacks. The reported company name is MahApps. The current detection status is Undefined, based on the latest analysis from 2026-02-18 23:01:02 (3 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: MahApps.Metro.IconPacks
Company Name: MahApps
MD5: f3bf5f2817e44c4ccd3d992cf4f78091
Size: 1 MB
First Published: 2021-06-04 20:54:31 (4 years ago)
Latest Published: 2026-02-18 23:01:02 (3 months ago)
Status: Undefined (on last analysis)
Analysis Date: 2026-02-18 23:01:02 (3 months ago)
%programfiles%

ThreatInfo has observed MahApps.Metro.IconPacks.Unicons.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.

12.1%
9.1%
9.1%
9.1%
6.1%
6.1%
3.0%
3.0%
3.0%
3.0%
3.0%
3.0%
3.0%
3.0%
3.0%
3.0%
3.0%
3.0%
3.0%
3.0%
3.0%
3.0%

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

Windows 10 88.2%
Windows 7 11.8%

The most common operating system signal for MahApps.Metro.IconPacks.Unicons.dll is Windows 10 with 88.2% 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.

MahApps.Metro.IconPacks.Unicons.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 0x0012f506
Image base 0x10000000

.NET Info:

MVID: 91f32ebd-166d-460f-8791-f1c9393aaa56

PE Sections:

Sections 3
Raw data 1236480

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

.text 1234432 bytes · 99.8% of section data
MD5 8d8dd7c682a78e0ab3acc99f966db5c3
.rsrc 1536 bytes · 0.1% of section data
MD5 86a7ec0b2bb232bf7bbe6a8bc7f307ae
.reloc 512 bytes · 0.0% of section data
MD5 893ca6104bb0339d6e418427bd3dbef4

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