GridinSoft Threat Intelligence

file300un[1].exe threat report

Detected as Trojan.Glupteba File reputation report
MD5 886e5d7f4e35c0bb6164dc74bf5e371b
Latest seen 2024-05-05 23:00:33 (2 years ago)
First seen 2024-05-04 23:01:24 (2 years ago)
Size 3 MB
Publisher getIsFieldDefPromotedBytes
Product getIsFieldDefPromotedBytes
Signed by Microsoft Code Signing PCA 2011

GridinSoft Anti-Malware detection

Detected by GridinSoft before you download

The current ThreatInfo record shows this exact file hash detected as Trojan.Glupteba. 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.Glupteba
Recommended action
Scan and remove
Last analysis
2024-05-05 23:00:33 (2 years ago)
File hash
886e5d7f4e35c0bb6164dc74bf5e371b
Download Anti-Malware

Why it matters

Why GridinSoft flags this file

Detection

GridinSoft identifies the sample as Trojan.Glupteba.

Timeline

First seen 2024-05-04 23:01:24 (2 years ago); latest analysis 2024-05-05 23:00:33 (2 years ago).

Publisher context

Company metadata: getIsFieldDefPromotedBytes. Product metadata: getIsFieldDefPromotedBytes.

Digital signature

Signed by Microsoft Code Signing PCA 2011. 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. 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.

File context

file300un[1].exe is a Windows file recorded in the ThreatInfo database. It is associated with getIsFieldDefPromotedBytes. The reported company name is getIsFieldDefPromotedBytes. The current detection status is Trojan.Glupteba, based on the latest analysis from 2024-05-05 23:00:33 (2 years ago).

If file300un[1].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.Glupteba.

File Details

Product Name: getIsFieldDefPromotedBytes
Company Name: getIsFieldDefPromotedBytes
MD5: 886e5d7f4e35c0bb6164dc74bf5e371b
Size: 3 MB
First Published: 2024-05-04 23:01:24 (2 years ago)
Latest Published: 2024-05-05 23:00:33 (2 years ago)
Status: Trojan.Glupteba (on last analysis)
Analysis Date: 2024-05-05 23:00:33 (2 years ago)

Detection screenshot

file300un[1].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.

Overview

Signed By: Microsoft Code Signing PCA 2011
Status: Valid

The signature on file300un[1].exe 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.

Common Places:

%localappdata%\microsoft\windows\inetcache\ie
%temp%

ThreatInfo has observed file300un[1].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.

Geographic signal

Observed country distribution

ThreatInfo has seen file300un[1].exe across 2 countries. Use this signal to compare local evidence with where the sample is most often reported.

Top country Costa Rica
Share 50.0%
Low High activity

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

OS Version:

Windows 10 100.0%

The most common operating system signal for file300un[1].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.

Analysis

file300un[1].exe is identified as pe for 64-bit systems. The subsystem is Windows CUI. PE header values are useful for triage, especially when they do not match the expected publisher, product, or release timeline.

Format pe
Architecture 64-bit
Subsystem Windows CUI
Entry point 0x0006aa44
Image base 0x0000000140000000

PE Sections:

Sections 9
Raw data 3576320

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

.text 476672 bytes · 13.3% of section data
MD5 f38cf738ed15a999468eb3edc3287410
.managed 1236480 bytes · 34.6% of section data
Uncommon name
MD5 87186969ec25bf7f483914f22addda1e
.rdata 1516544 bytes · 42.4% of section data
MD5 68052e14d69ab6bb005d444766c26ecf
.data 143360 bytes · 4.0% of section data
MD5 b2ba040acca2cc9d3813e1ba2bf7e884
.pdata 122880 bytes · 3.4% of section data
MD5 999c1a74f964f2181cc9cb7ed2c90e58
_RDATA 512 bytes · 0.0% of section data
Uncommon name
MD5 3fedbbc2126ce48fd8e685e65d921568
.rsrc 1536 bytes · 0.0% of section data
MD5 6ed052bf25b75f9a10cd8b13e502be28
.reloc 67072 bytes · 1.9% of section data
MD5 4b7f447a85ec628aea96df9ab9c9b4ac
.malware 11264 bytes · 0.3% of section data
Uncommon name
MD5 8fc491acb919fcc51f21f2db49d478c7

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

GridinSoft detects this file as Trojan.Glupteba

This report identifies file300un[1].exe by MD5 886e5d7f4e35c0bb6164dc74bf5e371b. If the same file is present on your device, scan the system and remove the detected object after confirming the hash and location.

Download GridinSoft Anti-Malware Scan the device and confirm whether this exact hash is present. Check this hash on VirusTotal

Recommended next steps

  • Compare the local file MD5 with 886e5d7f4e35c0bb6164dc74bf5e371b.
  • Check the file path, publisher, and signature against the details in this report.
  • Run a GridinSoft scan and remove the object if the same hash is found.