GridinSoft Threat Intelligence

atl90.dll file report

Clean record File reputation report
MD5 64eca1f64e4a988a6c5c93f3e5d66236
Latest seen 2021-01-14 18:59:37 (5 years ago)
First seen 2017-08-23 18:08:28 (8 years ago)
Size 157 KB

Why it matters

Evidence available for this file

Detection

Latest status is clean for this hash.

Timeline

First seen 2017-08-23 18:08:28 (8 years ago); latest analysis 2021-01-14 18:59:37 (5 years ago).

Publisher context

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

Digital signature

Signed by Microsoft Corporation. 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. 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.

atl90.dll is a Windows file recorded in the ThreatInfo database. It is associated with Microsoft® Visual Studio® 2008. The reported company name is Microsoft Corporation. The current detection status is Clean, based on the latest analysis from 2021-01-14 18:59:37 (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® 2008
Company Name: Microsoft Corporation
MD5: 64eca1f64e4a988a6c5c93f3e5d66236
Size: 157 KB
First Published: 2017-08-23 18:08:28 (8 years ago)
Latest Published: 2021-01-14 18:59:37 (5 years ago)
Status: Clean (on last analysis)
Analysis Date: 2021-01-14 18:59:37 (5 years ago)
Signed By: Microsoft Corporation
Status: Valid

The signature on atl90.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%\explorer\bin\microsoft.vc90.atl
%programfiles%\explorer\bin
%programfiles%

ThreatInfo has observed atl90.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 71.4%
Windows 7 28.6%

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

atl90.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.

Format pe
Architecture 32-bit
Subsystem Windows GUI
Entry point 0x00013216
Image base 0x78e20000

PE Sections:

Sections 4
Raw data 151552

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

.text 126976 bytes · 83.8% of section data
MD5 f237e04e244f25f9c7a206d846be11dc
.data 5120 bytes · 3.4% of section data
MD5 a558a2540a6e1b51f35050e79c9b0d18
.rsrc 9216 bytes · 6.1% of section data
MD5 f05d1dc703adffe1f30a25ad867ac7fb
.reloc 10240 bytes · 6.8% of section data
MD5 562f5e493d75c224bdebba882144094d

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 64eca1f64e4a988a6c5c93f3e5d66236.
  • 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.