GridinSoft Threat Intelligence
build2.exe threat report
GridinSoft Anti-Malware detection
Detected by GridinSoft before you download
The current ThreatInfo record shows this exact file hash detected as Spy.Vidar. 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
- Spy.Vidar
- Recommended action
- Scan and remove
- Last analysis
- 2024-05-22 23:01:30 (2 years ago)
- File hash
- a04031208441077a014f42095ff86107
Why it matters
Why GridinSoft flags this file
GridinSoft identifies the sample as Spy.Vidar.
First seen 2024-04-24 23:00:45 (2 years ago); latest analysis 2024-05-22 23:01:30 (2 years ago).
Product metadata: Smelfie.
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
- Compare the MD5 above with the file found on the device.
- Check whether the file appears in the observed locations or under one of the alternate names.
- Run GridinSoft Anti-Malware to confirm the detection and remove the file if it is present.
File context
build2.exe is a Windows file recorded in the ThreatInfo database. It is associated with Smelfie. The current detection status is Spy.Vidar, based on the latest analysis from 2024-05-22 23:01:30 (2 years ago).
If build2.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 Spy.Vidar.
File Details
| Product Name: | Smelfie |
| MD5: | a04031208441077a014f42095ff86107 |
| Size: | 289 KB |
| First Published: | 2024-04-24 23:00:45 (2 years ago) |
| Latest Published: | 2024-05-22 23:01:30 (2 years ago) |
| Status: | Spy.Vidar (on last analysis) | |
| Analysis Date: | 2024-05-22 23:01:30 (2 years ago) |
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:
| %localappdata% |
| %sysdrive%\windows.old.000\users\admin\appdata\local |
ThreatInfo has observed build2.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 build2.exe across 7 countries. Use this signal to compare local evidence with where the sample is most often reported.
The strongest geographic signal for this file is Pakistan with 25.0% of observed hits. Geographic distribution can help identify targeted campaigns, regional software bundles, or where a file is most commonly reported.
OS Version:
The most common operating system signal for build2.exe is Windows 10 with 91.7% 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
build2.exe is identified as pe for 32-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.
PE Sections:
Section layout highlights raw-size concentration, repeated names, packer markers, and hashes that can be compared across related samples.
d7c47d8258635550e4696a88511466a8
42e1cc3e9d5d61d2697fbf4129459dc6
84d925b0cb7ba1a58a1f664a5fdb73c5
4499ec878633c90948a53b1e19c4abbc
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 Spy.Vidar
This report identifies build2.exe by MD5 a04031208441077a014f42095ff86107. If the same file is present on your device, scan the system and remove the detected object after confirming the hash and location.