How to remove build2.exe
build2.exe
The module build2.exe has been detected as Ransom.Generic
build2.exe is a Windows file recorded in the ThreatInfo database. It is associated with Pircuzar. The current detection status is Ransom.Generic, based on the latest analysis from 2024-06-22 23:06:25 (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.Generic.
File Details
| Product Name: | Pircuzar |
| MD5: | 26544ec9adc1864de80222fb0b38e6dc |
| Size: | 342 KB |
| First Published: | 2024-03-18 23:13:27 (2 years ago) |
| Latest Published: | 2024-06-22 23:06:25 (2 years ago) |
| Status: | Ransom.Generic (on last analysis) | |
| Analysis Date: | 2024-06-22 23:06:25 (2 years ago) |
Common Places:
| %localappdata% |
| %localappdata% |
| %localappdata% |
| %localappdata% |
| %localappdata% |
| %localappdata% |
| %localappdata% |
| %localappdata% |
| %localappdata% |
| %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.
Geography:
| 25.0% | ||
| 20.0% | ||
| 15.0% | ||
| 10.0% | ||
| 5.0% | ||
| 5.0% | ||
| 5.0% | ||
| 5.0% | ||
| 5.0% | ||
| 5.0% |
The strongest geographic signal for this file is Mexico 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:
| Windows 10 | 80.0% | |
| Windows 7 | 15.0% | |
| Windows 8.1 | 5.0% |
The most common operating system signal for build2.exe is Windows 10 with 80.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 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.
| Subsystem: | Windows GUI |
| PE Type: | pe |
| OS Bitness: | 32 |
| Image Base: | 0x00400000 |
| Entry Address: | 0x0000b100 |
PE Sections:
| Name | Size of data | MD5 |
| .text | 91136 | 9b456a0e7e261e87df2236d4766e6a41 |
| .data | 178176 | 5ecf48a23e165d1f2b49bcd493824067 |
| .idata | 3072 | 308037a3816c9bcb0d0fe5208794a0bf |
| .gavucez | 1024 | 0f343b0931126a20f133d67c2b018a3b |
| .wuwof | 6656 | 3c63825015aabd810674f44afac6d12b |
| .sozo | 1024 | 0f343b0931126a20f133d67c2b018a3b |
| .rsrc | 68096 | ae0ae4e15d24ced869d464fa9f78f187 |
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.
More information:
