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 Ransom.STOP. 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
- Ransom.STOP
- Recommended action
- Scan and remove
- Last analysis
- 2024-03-23 23:01:43 (2 years ago)
- File hash
- 40ace790393a32e965f1c098767cf319
Why it matters
Why GridinSoft flags this file
GridinSoft identifies the sample as Ransom.STOP.
First seen 2024-03-23 23:01:43 (2 years ago); latest analysis 2024-03-23 23:01:43 (2 years ago).
Product metadata: Pircuzar.
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 Pircuzar. The current detection status is Ransom.STOP, based on the latest analysis from 2024-03-23 23:01:43 (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 Ransom.STOP.
File Details
| Product Name: | Pircuzar |
| MD5: | 40ace790393a32e965f1c098767cf319 |
| Size: | 410 KB |
| First Published: | 2024-03-23 23:01:43 (2 years ago) |
| Latest Published: | 2024-03-23 23:01:43 (2 years ago) |
| Status: | Ransom.STOP (on last analysis) | |
| Analysis Date: | 2024-03-23 23:01:43 (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% |
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 1 countries. Use this signal to compare local evidence with where the sample is most often reported.
The strongest geographic signal for this file is Egypt with 100.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 7 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
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.
0e4ae2dcd4f0b917a698b0fb93cc12bd
5ecf48a23e165d1f2b49bcd493824067
308037a3816c9bcb0d0fe5208794a0bf
0f343b0931126a20f133d67c2b018a3b
3c63825015aabd810674f44afac6d12b
0f343b0931126a20f133d67c2b018a3b
04bf761fd8a260857f389e096850e730
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 Ransom.STOP
This report identifies build2.exe by MD5 40ace790393a32e965f1c098767cf319. If the same file is present on your device, scan the system and remove the detected object after confirming the hash and location.