GridinSoft Threat Intelligence

UnifiedSDK.Core.dll file report

Under review File reputation report
MD5 2e20884678e3f70d06af6fed3af2d245
Latest seen 2026-04-28 23:01:33 (2 weeks ago)
First seen 2026-02-06 23:02:08 (3 months ago)
Size 219 KB
Publisher AnchorFree Inc.
Signed by Pango LLC

Why it matters

Evidence available for this file

Detection

No final classification is available yet.

Timeline

First seen 2026-02-06 23:02:08 (3 months ago); latest analysis 2026-04-28 23:01:33 (2 weeks ago).

Publisher context

Company metadata: AnchorFree Inc.. Product metadata: Unified Windows SDK.

Digital signature

Signed by Pango LLC. 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.

UnifiedSDK.Core.dll is a Windows file recorded in the ThreatInfo database. It is associated with Unified Windows SDK. The reported company name is AnchorFree Inc.. The current detection status is Undefined, based on the latest analysis from 2026-04-28 23:01:33 (2 weeks 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: Unified Windows SDK
Company Name: AnchorFree Inc.
MD5: 2e20884678e3f70d06af6fed3af2d245
Size: 219 KB
First Published: 2026-02-06 23:02:08 (3 months ago)
Latest Published: 2026-04-28 23:01:33 (2 weeks ago)
Status: Undefined (on last analysis)
Analysis Date: 2026-04-28 23:01:33 (2 weeks ago)
Signed By: Pango LLC
Status: Valid

The signature on UnifiedSDK.Core.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%

ThreatInfo has observed UnifiedSDK.Core.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 UnifiedSDK.Core.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.

UnifiedSDK.Core.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 0x00035896
Image base 0x10000000

.NET Info:

MVID: c41cb902-e1b1-4a94-a6b8-733fc14daf93

PE Sections:

Sections 3
Raw data 213504

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

.text 211456 bytes · 99.0% of section data
MD5 8c14beedf2720c44b0b76f6bf18dd17f
.rsrc 1536 bytes · 0.7% of section data
MD5 c1b21a9ee16bff540ee2bb3cbb5adde8
.reloc 512 bytes · 0.2% of section data
MD5 ba04b24b31b27f3fcc21af29091f931b

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 2e20884678e3f70d06af6fed3af2d245.
  • 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.