GridinSoft Threat Intelligence

AdobeAIRInstaller.exe file report

Clean record File reputation report
MD5 03c0413305ba30c4b5f08dfff38c4265
Latest seen 2023-11-03 23:30:00 (2 years ago)
First seen 2023-11-03 23:30:00 (2 years ago)
Size 8 MB
Publisher Adobe Systems Inc.
Product Adobe AIR

Why it matters

Evidence available for this file

Detection

Latest status is clean for this hash.

Timeline

First seen 2023-11-03 23:30:00 (2 years ago); latest analysis 2023-11-03 23:30:00 (2 years ago).

Publisher context

Company metadata: Adobe Systems Inc.. Product metadata: Adobe AIR .

Digital signature

Signed by Adobe Systems Incorporated. ThreatInfo marks this publisher as trusted for this record.

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.

AdobeAIRInstaller.exe is a Windows file recorded in the ThreatInfo database. It is associated with Adobe AIR . The reported company name is Adobe Systems Inc.. The current detection status is Clean, based on the latest analysis from 2023-11-03 23:30:00 (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.

Product Name: Adobe AIR
Company Name: Adobe Systems Inc.
MD5: 03c0413305ba30c4b5f08dfff38c4265
Size: 8 MB
First Published: 2023-11-03 23:30:00 (2 years ago)
Latest Published: 2023-11-03 23:30:00 (2 years ago)
Status: Clean (on last analysis)
Analysis Date: 2023-11-03 23:30:00 (2 years ago)
Signed By: Adobe Systems Incorporated
Status: Trusted Publisher

ThreatInfo marks this publisher as trusted for this record, but the file hash and source should still match the expected software distribution.

%sysdrive%\adobe cs6 master\payloads

ThreatInfo has observed AdobeAIRInstaller.exe 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 100.0%

The most common operating system signal for AdobeAIRInstaller.exe is Windows 10 with 100.0% 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.

AdobeAIRInstaller.exe 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 0x00001362
Image base 0x00400000

PE Sections:

Sections 5
Raw data 127488

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

.text 56832 bytes · 44.6% of section data
MD5 26d21d6a7672881db4b27db68ac72c14
.rdata 21504 bytes · 16.9% of section data
MD5 669f21953588de0be2126ae0a7fc35ca
.data 3584 bytes · 2.8% of section data
MD5 12317320838bf305bfb273526d7c2ab1
.rsrc 39936 bytes · 31.3% of section data
MD5 ba2e703088525ec9bc8aa05acb02de90
.reloc 5632 bytes · 4.4% of section data
MD5 ff52822c2676f59d14cceb96b4c13c68

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 03c0413305ba30c4b5f08dfff38c4265.
  • 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.