GridinSoft Threat Intelligence

A0002070.exe file report

Clean record File reputation report
MD5 4266462c8d4173912b13581827efe220
Latest seen 2021-03-03 16:53:45 (5 years ago)
First seen 2021-03-03 16:53:45 (5 years ago)
Size 20 KB
Product Adobe Acrobat

Why it matters

Evidence available for this file

Detection

Latest status is clean for this hash.

Timeline

First seen 2021-03-03 16:53:45 (5 years ago); latest analysis 2021-03-03 16:53:45 (5 years ago).

Publisher context

Company metadata: Adobe Systems Incorporated. Product metadata: Adobe Acrobat.

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.

A0002070.exe is a Windows file recorded in the ThreatInfo database. It is associated with Adobe Acrobat. The reported company name is Adobe Systems Incorporated. The current detection status is Clean, based on the latest analysis from 2021-03-03 16:53:45 (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: Adobe Acrobat
Company Name: Adobe Systems Incorporated
MD5: 4266462c8d4173912b13581827efe220
Size: 20 KB
First Published: 2021-03-03 16:53:45 (5 years ago)
Latest Published: 2021-03-03 16:53:45 (5 years ago)
Status: Clean (on last analysis)
Analysis Date: 2021-03-03 16:53:45 (5 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%\system volume information\_restore{ee263b9b-a159-4895-a93e-be815cd458f0}

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

The most common operating system signal for A0002070.exe is Windows 7 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.

A0002070.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 0x00001b8f
Image base 0x00400000

PE Sections:

Sections 5
Raw data 12288

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

.text 4608 bytes · 37.5% of section data
MD5 5e777d5ae808f15bb8e4e6f77d70c867
.rdata 3072 bytes · 25.0% of section data
MD5 5501ea5d56a33ec0227a000edcd8dd5c
.data 512 bytes · 4.2% of section data
MD5 3395948ff99a4414eb23a9da06b24dac
.rsrc 3072 bytes · 25.0% of section data
MD5 d7d002eb2170e65ab35786ed0ef6ab72
.reloc 1024 bytes · 8.3% of section data
MD5 65c1fbb918c12d5d6f1a037376457ae9

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 4266462c8d4173912b13581827efe220.
  • 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.