GridinSoft Threat Intelligence

updChrome[1].exe threat report

Detected as Trojan.Wacapew File reputation report
MD5 c74b706ecaa058e6e71e7b4b64dff9df
Latest seen 2023-07-19 23:58:45 (2 years ago)
First seen 2023-07-19 23:08:39 (2 years ago)
Size 9 MB

GridinSoft Anti-Malware detection

Detected by GridinSoft before you download

The current ThreatInfo record shows this exact file hash detected as Trojan.Wacapew. 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.Wacapew
Recommended action
Scan and remove
Last analysis
2023-07-19 23:58:45 (2 years ago)
File hash
c74b706ecaa058e6e71e7b4b64dff9df
Download Anti-Malware

Why it matters

Why GridinSoft flags this file

Detection

GridinSoft identifies the sample as Trojan.Wacapew.

Timeline

First seen 2023-07-19 23:08:39 (2 years ago); latest analysis 2023-07-19 23:58:45 (2 years ago).

Digital signature

Signed by Intel Celeron Skylake G3900 OEM v2. 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.

updChrome[1].exe is a Windows file recorded in the ThreatInfo database. The current detection status is Trojan.Wacapew, based on the latest analysis from 2023-07-19 23:58:45 (2 years ago).

If updChrome[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.Wacapew.

MD5: c74b706ecaa058e6e71e7b4b64dff9df
Size: 9 MB
First Published: 2023-07-19 23:08:39 (2 years ago)
Latest Published: 2023-07-19 23:58:45 (2 years ago)
Status: Trojan.Wacapew (on last analysis)
Analysis Date: 2023-07-19 23:58:45 (2 years ago)
updChrome[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.

Signed By: Intel Celeron Skylake G3900 OEM v2
Status: Valid

The signature on updChrome[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.

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

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

75.0%
25.0%

The strongest geographic signal for this file is Argentina with 75.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 updChrome[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.

updChrome[1].exe is identified as pe for 64-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 64-bit
Subsystem Windows GUI
Entry point 0x00e74728
Image base 0x0000000140000000

PE Sections:

Sections 17
Raw data 9656336

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

54272 bytes · 0.6% of section data
Uncommon name
MD5 0c4847251114c116b5764b335a24b9e4
7013888 bytes · 72.6% of section data
Large raw data Uncommon name
MD5 2f08fa1ccf704ea4f3aeaba84ebdbc3e
8704 bytes · 0.1% of section data
Uncommon name
MD5 bfb5e350cc9241d1e6440d0a32eb64e7
4096 bytes · 0.0% of section data
Uncommon name
MD5 e9316918b622d0d485cfe22074a9d845
1536 bytes · 0.0% of section data
Uncommon name
MD5 b93e6512c0b2131c5abd3ffa43856d5b
.bss 0 bytes · 0.0% of section data
MD5 d41d8cd98f00b204e9800998ecf8427e
512 bytes · 0.0% of section data
Uncommon name
MD5 c3766cfbb050a4f0c07acbc233268105
512 bytes · 0.0% of section data
Uncommon name
MD5 42b76cddd6ba9108b8299d14afffc677
512 bytes · 0.0% of section data
Uncommon name
MD5 f7e1c012fd958e7b1170c071b3769298
154624 bytes · 1.6% of section data
Uncommon name
MD5 98485b9867327b255cb148b92fb45218
1024 bytes · 0.0% of section data
Uncommon name
MD5 c5c8834586eec49209bed67f27417041
.idata 512 bytes · 0.0% of section data
MD5 bdb99c57642bc956ebc5475aa11a8e13
.tls 512 bytes · 0.0% of section data
MD5 985e3207d1a73ece666381cc89af691d
.rsrc 214528 bytes · 2.2% of section data
MD5 48c44c45a003037a061399ac2cdcc33c
.themida 0 bytes · 0.0% of section data
Uncommon name
MD5 d41d8cd98f00b204e9800998ecf8427e
.boot 2201088 bytes · 22.8% of section data
Uncommon name
MD5 4441e7d8e18fdd5f844503de2b15f11d
.reloc 16 bytes · 0.0% of section data
MD5 5e63c280deba35cbf424ad156c36e819

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.Wacapew

This report identifies updChrome[1].exe by MD5 c74b706ecaa058e6e71e7b4b64dff9df. 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 c74b706ecaa058e6e71e7b4b64dff9df.
  • 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.