GridinSoft Threat Intelligence
agcore.dll file report
Why it matters
Evidence available for this file
Latest status is clean for this hash.
First seen 2017-06-24 02:08:55 (8 years ago); latest analysis 2024-10-09 23:00:47 (2 years ago).
Company metadata: Microsoft Corporation. Product metadata: Microsoft® Silverlight.
Signed by Microsoft Corporation. The signature is reported as valid, but signed files can still be bundled or abused.
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
- Confirm the hash and publisher match the expected software.
- Review the observed locations and signature information below.
- Rescan if the file was downloaded from an unknown source or appears in an unusual path.
File context
agcore.dll is a Windows file recorded in the ThreatInfo database. It is associated with Microsoft® Silverlight. The reported company name is Microsoft Corporation. The current detection status is Clean, based on the latest analysis from 2024-10-09 23:00:47 (2 years ago).
This record is currently marked as clean, but file reputation can depend on the exact path, hash, and source. Compare the MD5 and publisher data below with the file on your system.
File Details
| Product Name: | Microsoft® Silverlight |
| Company Name: | Microsoft Corporation |
| MD5: | 18e563ce22e4a2ca421ed1ee55f30cae |
| Size: | 6 MB |
| First Published: | 2017-06-24 02:08:55 (8 years ago) |
| Latest Published: | 2024-10-09 23:00:47 (2 years ago) |
| Status: | Clean (on last analysis) | |
| Analysis Date: | 2024-10-09 23:00:47 (2 years ago) |
Overview
| Signed By: | Microsoft Corporation |
| Status: | Valid |
The signature on agcore.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.
Common Places:
| %appdata%\windows\plugins\pln |
| %windir%\inf\netlibrariestip\0009\v3.5.56385\1049\5.0\plugins |
| %localappdata%\google\profile\plugins |
| %system%\config\systemprofile\appdata\local\google\profile\plugins |
| %commonappdata%\system32\plugins |
| %commonappdata%\system32\x86\plugins |
| %commonappdata%\windows\profile\plugins |
| %appdata%\windows\plugins |
| %commonappdata%\microsoft\drm\wa\plugins |
ThreatInfo has observed agcore.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.
Geographic signal
Observed country distribution
ThreatInfo has seen agcore.dll across 16 countries. Use this signal to compare local evidence with where the sample is most often reported.
The strongest geographic signal for this file is Russian Federation with 60.5% of observed hits. Geographic distribution can help identify targeted campaigns, regional software bundles, or where a file is most commonly reported.
OS Version:
The most common operating system signal for agcore.dll is Windows 10 with 56.7% 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.
Analysis
agcore.dll is identified as pe for 32-bit systems. The subsystem is Windows GUI. PE header values are useful for triage, especially when they do not match the expected publisher, product, or release timeline.
PE Sections:
Section layout highlights raw-size concentration, repeated names, packer markers, and hashes that can be compared across related samples.
d98faf8c4fd70e8b8d56e85d6d0992ec
3b9620144491ce07e9928a27ac58fea4
8991ebed300ac7839f2fb82b17470b25
f8b158f627b305b971f6fa53b74a35bd
46170310d2246abfe9e7bef5df4a19e0
502b2f8b17ae0da2b0f934999f5ca40d
0acddbbad6045090de123f4dcb437e0b
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 hash is currently recorded as clean
Use the MD5, publisher, signature, and observed paths in this report to verify that the file on your device is the same copy described here.