GridinSoft Threat Intelligence

wup.exe threat report

Detected as Trojan.CoinMiner File reputation report
MD5 4f649a57b7ddf3874c9a2163a73e9b07
Latest seen 2024-11-18 23:01:49 (a year ago)
First seen 2023-01-26 23:45:53 (3 years ago)
Size 5 MB

GridinSoft Anti-Malware detection

Detected by GridinSoft before you download

The current ThreatInfo record shows this exact file hash detected as Trojan.CoinMiner. 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.CoinMiner
Recommended action
Scan and remove
Last analysis
2024-11-18 23:01:49 (a year ago)
File hash
4f649a57b7ddf3874c9a2163a73e9b07
Download Anti-Malware

Why it matters

Why GridinSoft flags this file

Detection

GridinSoft identifies the sample as Trojan.CoinMiner.

Timeline

First seen 2023-01-26 23:45:53 (3 years ago); latest analysis 2024-11-18 23:01:49 (a year 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.

File context

wup.exe is a Windows file recorded in the ThreatInfo database. The current detection status is Trojan.CoinMiner, based on the latest analysis from 2024-11-18 23:01:49 (a year ago).

If wup.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.CoinMiner.

File Details

MD5: 4f649a57b7ddf3874c9a2163a73e9b07
Size: 5 MB
First Published: 2023-01-26 23:45:53 (3 years ago)
Latest Published: 2024-11-18 23:01:49 (a year ago)
Status: Trojan.CoinMiner (on last analysis)
Analysis Date: 2024-11-18 23:01:49 (a year ago)

Detection screenshot

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

Common Places:

%temp%\csrss\wup
%sysdrive%\windows.old\users\kimoit\appdata\local\temp\csrss\wup
%sysdrive%\windows.old\users\fam. rivas\appdata\local\temp\csrss\wup
%sysdrive%\windows.old\users\philip\appdata\local\temp\csrss\wup
%sysdrive%\windows.old\users\anthonio\appdata\local\temp\csrss\wup
%sysdrive%\windows.old\users\naral\appdata\local\temp\csrss\wup
%desktop%\recuperacion\recovered\disco local(c)\archivos perdidos\borrado\users\usuario\appdata\local\temp\csrss\wup
%temp%
%sysdrive%\windows.old\users\dell\appdata\local\temp\csrss\wup
%sysdrive%\windows.old\users\dr el idrissi\appdata\local\temp\csrss\wup

ThreatInfo has observed wup.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 wup.exe across 50 countries. Use this signal to compare local evidence with where the sample is most often reported.

Top country Mexico
Share 9.0%
Low High activity

The strongest geographic signal for this file is Mexico with 9.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 90.5%
Windows 7 5.9%
Windows 8.1 2.4%
Windows 8 1.2%

The most common operating system signal for wup.exe is Windows 10 with 90.5% 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

wup.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 0x00346184
Image base 0x0000000140000000

PE Sections:

Sections 11
Raw data 5414912

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

.text 3655680 bytes · 67.5% of section data
MD5 6ad2a72d23ade83904e90ff32f7778b9
.rdata 1497088 bytes · 27.6% of section data
MD5 af7ca5c8b710ef05d18cd874e47861e2
.data 64000 bytes · 1.2% of section data
MD5 f8c35f0187d35f30ec5e619ab4e3fa3c
.pdata 128000 bytes · 2.4% of section data
MD5 edf2c91e9b6239b640b53253bf8ee8b3
_RANDOMX 3584 bytes · 0.1% of section data
Uncommon name
MD5 9ee63642b94966ecb630ee0843e46b26
_SHA3_25 2560 bytes · 0.0% of section data
Uncommon name
MD5 c14f9aad5e95192cd7523ba6675549fd
_TEXT_CN 10240 bytes · 0.2% of section data
Uncommon name
MD5 afea7882aa31e5987db2f12b8933de56
_TEXT_CN 4608 bytes · 0.1% of section data
Uncommon name
MD5 409bf3f918f2402291cb56c2e9354b47
_RDATA 512 bytes · 0.0% of section data
Uncommon name
MD5 7e27e5e73514cd6d84a3052b82f93b11
.rsrc 15360 bytes · 0.3% of section data
MD5 249bd546af9fec3a8380bc31bb4412de
.reloc 33280 bytes · 0.6% of section data
MD5 a90f66c1eb2a38dec34984456a65f543

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

This report identifies wup.exe by MD5 4f649a57b7ddf3874c9a2163a73e9b07. 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 4f649a57b7ddf3874c9a2163a73e9b07.
  • 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.