Is ZBrush.exe safe?
Unsigned 64-bit executable with zero AV detections but multiple YARA matches and conflicting third-party reports.
No engine flagged the file malicious, yet YARAify returned six rules including botnet_plaintext_c2 and the file remains unsigned. Widespread distribution over nearly three years weighs against a new threat, but the combination of unsigned status and researcher YARA hits leaves the sample in mixed-signal territory.
a9fc44c7d844fc315f…73344d6bec40d9Recommended next actions
Before running
Do not run it until the source and publisher can be verified independently.
If you already ran it
Stop using it, scan the device, and watch for unexpected behavior or security alerts. Get a fresh copy from the developer's official site or an official app store.
Intelligence
The saved assessment, checked against the scan evidence and recorded coverage.
The reasoning behind this verdict
This section explains the evidence supporting the verdict and keeps conflicting or missing signals visible.
No engine flagged the file malicious, yet YARAify returned six rules including botnet_plaintext_c2 and the file remains unsigned. Widespread distribution over nearly three years weighs against a new threat, but the combination of unsigned status and researcher YARA hits leaves the sample in mixed-signal territory.
Zero detections across 74 engines, including 17 tier-1 engines reporting clean, is a strong benign indicator. However, the file is unsigned and YARAify matched six community rules, two of which reference botnet or Golang C2 patterns. Sandbox execution showed only ambient behaviour and no malicious verdict, but the absence of a completed host-reputation check on the 18 no complete contacted-host reputation result was available bill of health. Prevalence data shows the binary has circulated for 977 days among over a thousand submitters, reducing the likelihood of a targeted or brand-new threat.
What We Detected
74 antivirus engines scanned the sample; none returned a malicious or suspicious result. The file is a 42 MB 64-bit PE executable that is not digitally signed. YARAify matched six community-authored rules, among them botnet_plaintext_c2 and golang_bin_JCorn_CSC846. Sandbox telemetry recorded 18 direct-IP connections and several ambient system queries but no offensive MITRE techniques or malicious verdict.
Threat Behavior
No dropped children, persistence mechanisms, or registry modifications were observed. The contacted IP list could not be cross-checked against our malicious-host cache because that coverage block is null. Community comments on third-party scanners are split between clean and likely-malicious labels, but these reports are not corroborated by mainstream engines.
What To Do Now
Keep existing endpoint protection enabled. If the file’s provenance is uncertain, obtain a signed release from the legitimate ZBrush vendor or run it in an isolated virtual machine before trusting it on production systems.
Where this verdict could be wrong1 caveat
- YARAify matched 6 rules including botnet_plaintext_c2 and golang_bin_JCorn_CSC846; community comments also contain LIKELY_MALICIOUS reports from FileScan.IO.
These are the assessment's weak points. If you believe one applies to your file, report the verdict and we'll re-review it.
- 0/74 engines flagged malicious
- Common-old prevalence (1078 submitters)
- No offensive MITRE techniques or malicious sandbox verdict
- File is unsigned
- YARAify matched botnet_plaintext_c2 and golang rules
- Direct-IP connections observed without domain context
Treat the file with caution until its source can be verified; the combination of unsigned status and YARA hits outweighs the clean engine consensus.
Coverage & freshness
Complete means the check returned a usable result. It does not mean the file is safe.
Antivirus
Complete0 of 74 engines flagged the file.
Sandbox
Complete1 isolated runtime environment contributed observations.
Network
Partial20 runtime contacts were observed without a completed reputation cross-check.
YARA
Complete6 signature or behavior rules matched.
External intel
Complete3 of 3 independent reference sources completed.
Behavior
Plain-English impact first, then the observed runtime evidence.
Runtime flight recorder
Capture complete- 1isolated sandbox run
- 7MITRE ATT&CK techniques
- 10spawned processes
- 20network contacts
- 2filesystem & mutex artifacts
What this file does
Observed actions and their security significance
High concern: Manipulated how the operating system loads code, which can redirect execution.
Moderate concern: Contained obfuscated or packed code that makes inspection harder.
Moderate concern: Communicated over a common application protocol; malware can use this for command-and-control.
Moderate concern: Checked the environment for virtualisation or analysis tools.
Note: Collects details about your system.
Note: Loads extra code modules while running.
These are observed capabilities from an isolated analysis. A technique does not prove malicious intent on its own, and the file never ran on your device.
Attack story
Runtime observations grouped by analysis stage. Arrows organize the stages; they do not claim chronology or causality.
Input file
The submitted object
- FileObserved
ZBrush.exe
a9fc44c7d844fc315fdd408517c5b891189be41ef26382058273344d6bec40d9
01Uploaded file
Processes
Runtime execution
- ProcessObserved
Observed process
%SAMPLEPATH%\a9fc44c7d844fc315fdd408517c5b891189be41ef26382058273344d6bec40d9.exe
02Isolated runtime analysis - ProcessObserved
Observed process
C:\Windows\System32\UI0Detect.exe
03Isolated runtime analysis - +1 more recorded observation in Analyst mode
Network
Hosts contacted
- Contacted hostObserved
20.99.133.109
Contact observed during runtime.
04Isolated runtime analysis - Contacted hostObserved
23.216.81.152
Contact observed during runtime.
05Isolated runtime analysis - +1 more recorded observation in Analyst mode
5 recorded facts from one runtime window. Every fact remains independently traceable in Analyst mode.
What this file did when executed
This file was detonated in 1 sandbox and its runtime behaviour was observed.
Adversary techniques mapped to the MITRE ATT&CK framework.
- 20.99.133.109
- 23.216.81.152
- 20.69.140.28
- 152.195.19.97
- 23.215.176.146
- 192.168.0.24
- 23.198.171.50
- 20.99.186.246
- 192.168.0.38
- 52.185.73.156
- C:\Windows\System32\wbem\Performance\WmiApRpl.h
- C:\Windows\System32\wbem\Performance\WmiApRpl.ini
Detection & Forensics
Consensus, attribution, signatures, code structure, prevalence, and identity.
Evidence integrity
Chain of custody for the facts preserved in this report.
- 6rule hits recorded
- 0 / 74engines flagged
- 1,078sources in submission history
Why these facts are shown
Each statement identifies whether it was directly recorded or derived from saved scan facts.
- 01
5 high-confidence signature or behavior rules matched this file.
Verdict inputView chapterProvenanceObservedSourceSignature and behavior rulesObserved at - 02
0 of 74 antivirus engines flagged the file.
ProvenanceObservedSourceAntivirus analysisObserved at - 03
The hash has a long, established submission history across 1,078 sources.
ProvenanceDerivedSourceSubmission historyObserved at - 04
Scanned file: ZBrush.exe — a9fc44c7d844fc315fdd408517c5b891189be41ef26382058273344d6bec40d9
ProvenanceObservedSourceUploaded fileObserved at - 05
Observed process — %SAMPLEPATH%\a9fc44c7d844fc315fdd408517c5b891189be41ef26382058273344d6bec40d9.exe
ProvenanceObservedSourceIsolated runtime analysisObserved at - 06
Observed process — C:\Windows\System32\UI0Detect.exe
ProvenanceObservedSourceIsolated runtime analysisObserved at - 07
Contacted host: 20.99.133.109 — Contact observed during runtime.
ProvenanceObservedSourceIsolated runtime analysisObserved at - 08
Contacted host: 23.216.81.152 — Contact observed during runtime.
ProvenanceObservedSourceIsolated runtime analysisObserved at
Detection sources at a glance
The available sources did not agree on a named threat category.
One or more independent reference databases matched this hash.
Signatures and behavior heuristics
A community signature or high-severity behavioral heuristic matched. Signatures identify known patterns; heuristics are strong leads but are not proof on their own.
- adonunix2
- botnet_plaintext_c2
- golang_bin_JCorn_CSC846
- pe_detect_tls_callbacks
- Sus_CMD_Powershell_Usage
The sample contacted an external IP address directly and no application domain was recorded. Direct-IP traffic also occurs in legitimate installers and infrastructure, so this is supporting context only and requires corroboration from host reputation and other runtime evidence.
Evidence20.99.133.109 · 23.216.81.152 · 20.69.140.28
0 of 74 engines flagged this file
View all 74 engine results
Section entropy & packers
No high-entropy executable section or known packer signature was detected. Data and resource sections can still have high entropy without indicating packed code.
How widely this file has been seen
Widely seen in the wild for a long time. High prior this is legitimate; isolated detections on common-old files are usually false positives.
Fingerprint and provenance
- File name
- ZBrush.exe
- Format
- Win32 EXE
- Code signing
- No verified publisher
- Size
- 40.9 MB
- Last analyzed
- Aug 18, 2026, 12:15 PM UTC
a9fc44c7d844fc315fdd408517c5b891189be41ef26382058273344d6bec40d9Safety & FAQ
Complete recovery guidance and answers for the next decision.
What to do now
We couldn't fully clear this file. Treat it with caution.
- Recovery step 01
Don't run it unless you're certain it came from a source you trust.
- Recovery step 02
Check where you got it — an unexpected attachment or a random download link is a red flag.
- Recovery step 03
If its origin cannot be confirmed, delete this file and use a fresh copy from a trusted source. Get a fresh copy from the developer's official site or an official app store.
- Recovery step 04
If you're still unsure, scan it again in a day or two — detections often catch up on newer files.
Safety FAQ
Direct answers grounded in the saved verdict and evidence in this report.
Is ZBrush.exe safe, or is it malware?
What is ZBrush.exe?
How many antivirus engines detected ZBrush.exe?
I already downloaded and ran ZBrush.exe — what should I do?
How do I remove ZBrush.exe?
What is the SHA-256 hash of ZBrush.exe?
How up to date is this analysis of ZBrush.exe?
Community
Member reviews and reports for this exact file hash.