MSIE4D9.tmp threat report

MD5 c0e57f3a0d3e0c33223b6b13f712d466
Latest seen 2026-01-05 23:06:19 (4 months ago)
First seen 2026-01-05 23:06:19 (4 months ago)
Size 1 MB

GridinSoft Anti-Malware detection

Detected by GridinSoft before you download

The current ThreatInfo record shows this exact file hash detected as Trojan.Vigorf. 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.Vigorf
Recommended action
Scan and remove
Last analysis
2026-01-05 23:06:19 (4 months ago)
File hash
c0e57f3a0d3e0c33223b6b13f712d466
Download Anti-Malware

Why it matters

Why GridinSoft flags this file

Detection

GridinSoft identifies the sample as Trojan.Vigorf.

Timeline

First seen 2026-01-05 23:06:19 (4 months ago); latest analysis 2026-01-05 23:06:19 (4 months ago).

Publisher context

Company metadata: Adguard Software Limited. Product metadata: Adguard.CustomActions.

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.

MSIE4D9.tmp is a Windows file recorded in the ThreatInfo database. It is associated with Adguard.CustomActions. The reported company name is Adguard Software Limited. The current detection status is Trojan.Vigorf, based on the latest analysis from 2026-01-05 23:06:19 (4 months ago).

If MSIE4D9.tmp 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.Vigorf.

Product Name: Adguard.CustomActions
Company Name: Adguard Software Limited
MD5: c0e57f3a0d3e0c33223b6b13f712d466
Size: 1 MB
First Published: 2026-01-05 23:06:19 (4 months ago)
Latest Published: 2026-01-05 23:06:19 (4 months ago)
Status: Trojan.Vigorf (on last analysis)
Analysis Date: 2026-01-05 23:06:19 (4 months ago)
MSIE4D9.tmp 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.

%windir%

ThreatInfo has observed MSIE4D9.tmp 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 Russia 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 MSIE4D9.tmp 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.

MSIE4D9.tmp is identified as pe for 64 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: 64
Image Base: 0x0000000180000000
Entry Address: 0x000054bc

PE Sections:

Name Size of data MD5
.text 111616 49ea06e230ee2a2e3119230628663309
.rdata 104448 9fed770c8cdbb1ec3527c58081cb0688
.data 3072 677f6eb5af11c0fabbc7cc75a3520a70
.pdata 6144 c0d827474755204aaeccf6c0e13d2e4c
.gxfg 5632 30ebe4bf69c5c6950b626f6c399a7180
.gehcont 512 d65f52ec5cca347fc256bef9112b8cec
.rsrc 2560 c1d68a567b9b19ea368e5a26d9d6431f
.reloc 2048 0b418768d545bc99f276f17a796f919c

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: