GridinSoft Threat Intelligence

aa596c7.rbf file report

Clean record File reputation report
MD5 7caa1b97a3311eb5a695e3c9028616e7
Latest seen 2021-02-08 16:59:38 (5 years ago)
First seen 2017-05-27 23:09:09 (9 years ago)
Size 645 KB

Why it matters

Evidence available for this file

Detection

Latest status is clean for this hash.

Timeline

First seen 2017-05-27 23:09:09 (9 years ago); latest analysis 2021-02-08 16:59:38 (5 years ago).

Publisher context

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

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.

aa596c7.rbf is a Windows file recorded in the ThreatInfo database. It is associated with Microsoft® Visual Studio® 2012. The reported company name is Microsoft Corporation. The current detection status is Clean, based on the latest analysis from 2021-02-08 16:59:38 (5 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® 2012
Company Name: Microsoft Corporation
MD5: 7caa1b97a3311eb5a695e3c9028616e7
Size: 645 KB
First Published: 2017-05-27 23:09:09 (9 years ago)
Latest Published: 2021-02-08 16:59:38 (5 years ago)
Status: Clean (on last analysis)
Analysis Date: 2021-02-08 16:59:38 (5 years ago)
Signed By: Microsoft Corporation
Status: Valid

The signature on aa596c7.rbf 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.

%appdata%\taskmgr\win64
%appdata%
%localappdata%
%programfiles%\minergate
%appdata%\hgemxnrtqrutsfsuxpwnbtfjnsnillbo
%appdata%\dll-files.com\dll-files.com client\backup
%commonappdata%\ea56063c-ccf6-4a50-a577-5ca19bc9f4c8\dell\drivers\video_driver_ffyvx_wn32_16.400.2301_a02\bin64
%programfiles%\drivertoolkit\download\329e689a8b870f3664ae00942d276ed0\system32\64
%sysdrive%\sysdata
%appdata%\ujlwdgbyninkgnzwijzdldzzwjbbnghu

ThreatInfo has observed aa596c7.rbf 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.

msvcp110.dll 17 7 6 5 2467f6b7.rbf 149c7ce.rbf 2cd77.rbf 501a732.rbf 1a890c.rbf 1255da9b.rbf 6b7dc1f6.rbf aa596c7.rbf msvcp110.dll.quarantined

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 58.4%
Windows 7 32.7%
Windows 8.1 7.4%
Windows Server 2008 R2 0.8%
Windows 8 0.8%

The most common operating system signal for aa596c7.rbf is Windows 10 with 58.4% 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.

aa596c7.rbf is identified as pe for 64-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.

Format pe
Architecture 64-bit
Subsystem Windows GUI
Entry point 0x0004b93c
Image base 0x0000000180000000

PE Sections:

Sections 6
Raw data 644608

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

.text 331264 bytes · 51.4% of section data
MD5 7fa4a9d44f9f940da92e55b33de34095
.rdata 260096 bytes · 40.3% of section data
MD5 8ebbcc9b9c316d03295c657f520f633f
.data 14848 bytes · 2.3% of section data
MD5 3ea201bacdea50cd5c529e5b03b9f838
.pdata 17920 bytes · 2.8% of section data
MD5 1a0ccaed027cd07779bd90cb57beae5c
.rsrc 1024 bytes · 0.2% of section data
MD5 34833605f7e1a92aa0721d2fbe581468
.reloc 19456 bytes · 3.0% of section data
MD5 ee51d435404b8d86763174c33ab8b66c

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