GridinSoft Threat Intelligence

atl110.dll file report

Clean record File reputation report
MD5 fe00086a2fc935af640c7f302c12fe89
Latest seen 2021-02-08 16:49:51 (5 years ago)
First seen 2017-07-21 20:08:53 (8 years ago)
Size 188 KB
Publisher Microsoft Corporation
Product Microsoft® Visual Studio® 2012
Signed by Microsoft Corporation

Why it matters

Evidence available for this file

Detection

Latest status is clean for this hash.

Timeline

First seen 2017-07-21 20:08:53 (8 years ago); latest analysis 2021-02-08 16:49:51 (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.

File context

atl110.dll 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:49:51 (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.

File Details

Product Name: Microsoft® Visual Studio® 2012
Company Name: Microsoft Corporation
MD5: fe00086a2fc935af640c7f302c12fe89
Size: 188 KB
First Published: 2017-07-21 20:08:53 (8 years ago)
Latest Published: 2021-02-08 16:49:51 (5 years ago)
Status: Clean (on last analysis)
Analysis Date: 2021-02-08 16:49:51 (5 years ago)

Overview

Signed By: Microsoft Corporation
Status: Valid

The signature on atl110.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%\dll-files.com\dll-files.com client\backup
%programfiles%\dllescort\sysscan\windows\system32
%commonappdata%
%programfiles%\dllescort2021\sysscan\windows
%commonappdata%\bromium\vsentry\4.2.4.52\stage1\stage1image0002\swapdata-c38ff989-d42f-492b-bcd8-f79bb204a254

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

File Names:

2 observed names
19 atl110.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.

Geographic signal

Observed country distribution

ThreatInfo has seen atl110.dll across 4 countries. Use this signal to compare local evidence with where the sample is most often reported.

Top country Saudi Arabia
Share 33.3%
Low High activity

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

OS Version:

Windows 10 83.3%
Windows 7 16.7%

The most common operating system signal for atl110.dll is Windows 10 with 83.3% 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

atl110.dll 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 0x0000f444
Image base 0x0000000180000000

PE Sections:

Sections 6
Raw data 175616

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

.text 105984 bytes · 60.3% of section data
MD5 60d2ce16ede4750ed40e08cc84b6a7a3
.rdata 43520 bytes · 24.8% of section data
MD5 289d08ef34e622a3c68c5b6f611a10a4
.data 7168 bytes · 4.1% of section data
MD5 9b4a4a49702f409e698d5c41a430a453
.pdata 6144 bytes · 3.5% of section data
MD5 a3263c51b936f67e0636da6988a837a7
.rsrc 9216 bytes · 5.2% of section data
MD5 13df26136e0f5486ee96c79080c2f68d
.reloc 3584 bytes · 2.0% of section data
MD5 b1820beadc97d0c471614313d47ac601

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