GridinSoft Threat Intelligence

{484C5CB2-2A4F-485C-AEBC-9E3832D5FCDD}.dll file report

Clean record File reputation report
MD5 ab15feb56d735f4589217d02464b1a06
Latest seen 2022-08-20 23:21:27 (3 years ago)
First seen 2017-10-11 09:10:19 (8 years ago)
Size 620 KB

Why it matters

Evidence available for this file

Detection

Latest status is clean for this hash.

Timeline

First seen 2017-10-11 09:10:19 (8 years ago); latest analysis 2022-08-20 23:21:27 (3 years ago).

Publisher context

Company metadata: Microsoft Corporation. Product metadata: Microsoft® Visual Studio® 2015.

Digital signature

Signed by Microsoft Corporation. The signature is reported as valid, but signed files can still be bundled or abused.

Aliases

This hash has appeared under multiple file names, which can happen with repackaging, bundling, or deliberate renaming.

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. Confirm the hash and publisher match the expected software.
  2. Review the observed locations and signature information below.
  3. Rescan if the file was downloaded from an unknown source or appears in an unusual path.

{484C5CB2-2A4F-485C-AEBC-9E3832D5FCDD}.dll is a Windows file recorded in the ThreatInfo database. It is associated with Microsoft® Visual Studio® 2015. The reported company name is Microsoft Corporation. The current detection status is Clean, based on the latest analysis from 2022-08-20 23:21:27 (3 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.

Product Name: Microsoft® Visual Studio® 2015
Company Name: Microsoft Corporation
MD5: ab15feb56d735f4589217d02464b1a06
Size: 620 KB
First Published: 2017-10-11 09:10:19 (8 years ago)
Latest Published: 2022-08-20 23:21:27 (3 years ago)
Status: Clean (on last analysis)
Analysis Date: 2022-08-20 23:21:27 (3 years ago)
Signed By: Microsoft Corporation
Status: Valid

The signature on {484C5CB2-2A4F-485C-AEBC-9E3832D5FCDD}.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.

%sysdrive%\config.msi
%localappdata%\winminer\miners
%programfiles%\tencent\weiyunsync\weiyunsync
%programfiles%\tencent\weiyunsync\weiyunsync\bin
%programfiles%
%commonappdata%
%commondir%\insta360
%appdata%\kryptex\miners

ThreatInfo has observed {484C5CB2-2A4F-485C-AEBC-9E3832D5FCDD}.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.

4f01d5d.rbf msvcp140.dll {484C5CB2-2A4F-485C-AEBC-9E3832D5FCDD}.dll

This hash has been seen with multiple file names. Alternate names can appear when software is updated, copied between folders, packed by an installer, or deliberately renamed to avoid recognition. Compare the exact MD5 above before assuming two names refer to the same file.

Windows 10 86.6%
Windows 8.1 6.5%
Windows 7 6.5%
Windows 8 0.5%

The most common operating system signal for {484C5CB2-2A4F-485C-AEBC-9E3832D5FCDD}.dll is Windows 10 with 86.6% 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.

{484C5CB2-2A4F-485C-AEBC-9E3832D5FCDD}.dll is identified as pe for 64-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 64-bit
Subsystem Windows CUI
Entry point 0x00049d40
Image base 0x0000000180000000

PE Sections:

Sections 7
Raw data 617984

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

.text 324608 bytes · 52.5% of section data
MD5 aa3fa2c96de1ae4e89ed72b51adb651b
.rdata 264192 bytes · 42.8% of section data
MD5 81742656d5b0372947515bc3b4c73a79
.data 7168 bytes · 1.2% of section data
MD5 0753004d59adbca725e5ceee56941841
.pdata 17408 bytes · 2.8% of section data
MD5 6370db1e5dca054f48474e60c6308583
.didat 512 bytes · 0.1% of section data
Uncommon name
MD5 11670cb25cdd71bdac7898cf3bbcc0de
.rsrc 1024 bytes · 0.2% of section data
MD5 bcdb58dad2cd27f47987b02bfe9d74bc
.reloc 3072 bytes · 0.5% of section data
MD5 64fcfc8ebf5763789ff91b9ad0c50935

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.

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