A0472991.EXE threat report

MD5 da89d2e2d94c44a0f3151a80551b1671
Latest seen 2023-01-22 23:42:37 (3 years ago)
First seen 2023-01-22 23:29:47 (3 years ago)
Size 2 MB

GridinSoft Anti-Malware detection

Detected by GridinSoft before you download

The current ThreatInfo record shows this exact file hash detected as Trojan.Heur!. Download GridinSoft Anti-Malware to scan the device, confirm whether this file is present, and remove the detected object if it is found.

Detection name
Trojan.Heur!
Recommended action
Scan and remove
Last analysis
2023-01-22 23:42:37 (3 years ago)
File hash
da89d2e2d94c44a0f3151a80551b1671
Download Anti-Malware

Why it matters

Why GridinSoft flags this file

Detection

GridinSoft identifies the sample as Trojan.Heur!.

Timeline

First seen 2023-01-22 23:29:47 (3 years ago); latest analysis 2023-01-22 23:42:37 (3 years ago).

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. Compare the MD5 above with the file found on the device.
  2. Check whether the file appears in the observed locations or under one of the alternate names.
  3. Run GridinSoft Anti-Malware to confirm the detection and remove the file if it is present.

A0472991.EXE is a Windows file recorded in the ThreatInfo database. The current detection status is Trojan.Heur!, based on the latest analysis from 2023-01-22 23:42:37 (3 years ago).

If A0472991.EXE appears on your computer unexpectedly, treat it as suspicious. Check its location, digital signature, and recent system changes before allowing it to run. A full anti-malware scan is recommended when this file is detected as Trojan.Heur!.

MD5: da89d2e2d94c44a0f3151a80551b1671
Size: 2 MB
First Published: 2023-01-22 23:29:47 (3 years ago)
Latest Published: 2023-01-22 23:42:37 (3 years ago)
Status: Trojan.Heur! (on last analysis)
Analysis Date: 2023-01-22 23:42:37 (3 years ago)
A0472991.EXE detection screenshot

The screenshot is a visual record of a GridinSoft Anti-Malware detection for this sample. Use the hash and metadata above as the primary identifiers when comparing the file on your system.

%sysdrive%\system volume information\_restore{059d97ae-da1f-4e5c-b8cb-f32ac50b992a}
%sysdrive%\system volume information\_restore{059d97ae-da1f-4e5c-b8cb-f32ac50b992a}

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

100.0%

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

Windows 10 100.0%

The most common operating system signal for A0472991.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.

A0472991.EXE is identified as pe for 32 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.

Subsystem: Windows GUI
PE Type: pe
OS Bitness: 32
Image Base: 0x00400000
Entry Address: 0x000973da

PE Sections:

Name Size of data MD5
.shrink0 0 d41d8cd98f00b204e9800998ecf8427e
BSS 0 d41d8cd98f00b204e9800998ecf8427e
.shrink1 0 d41d8cd98f00b204e9800998ecf8427e
.tls 0 d41d8cd98f00b204e9800998ecf8427e
.rdata 512 b13416d9a4d55c8dedeccc6f18c51585
.shrink2 0 d41d8cd98f00b204e9800998ecf8427e
.shrink3 512 c60a8710f77027b5c59c36c9f9b6a621
.rdata 512 e5e9f519c06ca0c053612db7ace62d34
.data 5632 e341f4198c921abbc2e693f4ef689537
.idata 2560 1a2e20a53d6c41649336e9389c869871
.load 11776 e998443d61b8a05b5b2f323d8303c109
.reloc 1536 b612165323f532126c4153685f2077aa
.rsrc 7168 e2180c6ee6de789f18b60225b7b75d5e

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.

More information: