Is z0nreccs.exe safe?
No antivirus engine detected the signed executable, and its completed runtime check showed no malware-specific behavior, although one ransomware-oriented YARA rule warrants caution.
The file has no detections among 75 antivirus engines, carries a verified NetEase signature, and produced no malicious sandbox verdict or offensive behavior. Four community YARA matches—especially VECT_Ransomware—are the main concern, but they are not corroborated by runtime activity, malicious children, network reputation, or engine detections.
56c244aded0313ebda…6d5de39c417cb2Recommended next actions
Before running
Run it only when it came from the developer's official site or another source you independently trust.
If you already ran it
Keep normal device protection enabled and stop if the file behaves unexpectedly.
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.
The file has no detections among 75 antivirus engines, carries a verified NetEase signature, and produced no malicious sandbox verdict or offensive behavior. Four community YARA matches—especially VECT_Ransomware—are the main concern, but they are not corroborated by runtime activity, malicious children, network reputation, or engine detections.
All 75 antivirus engines returned no malicious or suspicious classification, including 17 tier-1 engines. The executable has a verified signature from NetEase (Hangzhou) Network Co., though no established signer history is available in this dataset. One completed sandbox run recorded only benign-common techniques and no malware-specific behavior or malicious verdict. The sole contacted domain was fully checked against the available host cache and had no malicious or suspicious classification. Four community YARA rules matched, but the ransomware-oriented rule is isolated and unsupported by detections, packing indicators, dropped malware, persistence, or ransomware behavior.
What We Detected
No antivirus engine flagged the sample: 0 of 75 reported it as malicious or suspicious, and all 17 tier-1 engines reported no detection. The executable is signed with a verified certificate issued to NetEase (Hangzhou) Network Co. It is not packed and its code section does not show unusually high entropy.
Threat Behavior
One completed sandbox run produced no malicious verdict and no malware-specific offensive technique. The observed techniques were common capabilities such as command execution, system-information discovery, and network communication. The only contacted domain, cl-glcb907925.gcdn.co, was covered by the host-reputation check and was not listed as malicious or suspicious. No malicious child file, persistence indicator, or file-writing activity was reported.
What To Do Now
Four community YARA rules matched, including VECT_Ransomware, so the file should still come from a trusted NetEase distribution channel before execution. Keep endpoint protection enabled, verify the signature remains valid on the local copy, and avoid running it if its origin or expected purpose cannot be confirmed.
Where this verdict could be wrong3 caveats
- YARAify matched four rules, including 'VECT_Ransomware'; researcher-rule convergence can indicate malware even before antivirus detections appear.
- signing.signerStats.found=false and signing.trustedPublisher.matched=false, so the verified NetEase signature lacks corroborating publisher history in this dataset.
- The filename 'z0nreccs.exe' is opaque and does not identify a recognizable product, although brandMismatch was not detected.
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 of 75 antivirus engines reported a malicious or suspicious result.
- All 17 tier-1 engines reported no detection.
- The code signature for NetEase (Hangzhou) Network Co. is verified.
- One completed sandbox run produced no malicious verdict and no offensive technique.
- The sole observed host was fully inspected and had no malicious or suspicious cache result.
- Four community YARA rules matched, including VECT_Ransomware.
- No historical signer statistics are available for NetEase (Hangzhou) Network Co. in this dataset.
- The opaque filename does not clearly identify the expected NetEase product.
Use the file only if it came from an official or otherwise trusted NetEase distribution channel, and verify its digital signature locally. Keep endpoint protection enabled because the ransomware-oriented YARA match remains an unresolved caution.
Coverage & freshness
Complete means the check returned a usable result. It does not mean the file is safe.
Antivirus
Complete0 of 75 engines flagged the file.
Sandbox
Complete1 isolated runtime environment contributed observations.
Network
Complete1 contacted host was cross-checked.
YARA
Complete4 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
- 6MITRE ATT&CK techniques
- 1spawned processes
- 1network contacts
- 0filesystem & mutex artifacts
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.
- cl-glcb907925.gcdn.co
Detection & Forensics
Consensus, attribution, signatures, code structure, prevalence, and identity.
Evidence integrity
Chain of custody for the facts preserved in this report.
- 4rule hits recorded
- 0 / 75engines flagged
- 16sources in submission history
Why these facts are shown
Each statement identifies whether it was directly recorded or derived from saved scan facts.
- 01
0 of 75 antivirus engines flagged the file.
Verdict inputView chapterProvenanceObservedSourceAntivirus analysisObserved at - 02
The file has a valid code signature from NetEase (Hangzhou) Network Co..
ProvenanceObservedSourceCode-signing metadataObserved at - 03
4 high-confidence signature or behavior rules matched this file.
Verdict inputView chapterProvenanceObservedSourceSignature and behavior rulesObserved at - 04
Scanned file: z0nreccs.exe — 56c244aded0313ebda795841c0db38dbe3e3321f5c9302cc166d5de39c417cb2
ProvenanceObservedSourceUploaded fileObserved at - 05
Observed process — "C:\Users\user\Desktop\Thunder.exe"
ProvenanceObservedSourceIsolated runtime analysisObserved at - 06
Contacted host: cl-glcb907925.gcdn.co — 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.
- DebuggerCheck__API
- golang_bin_JCorn_CSC846
- PE_Digital_Certificate
- VECT_Ransomware
0 of 75 engines flagged this file
View all 75 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
Moderate prevalence — neither rare nor common. No strong prior applies.
Fingerprint and provenance
- File name
- z0nreccs.exe
- Format
- Win32 EXE
- Code signing
- Signature valid: NetEase (Hangzhou) Network Co.
- Size
- 350.7 KB
- Last analyzed
- Oct 5, 2026, 6:14 AM UTC
56c244aded0313ebda795841c0db38dbe3e3321f5c9302cc166d5de39c417cb2Safety & FAQ
Complete recovery guidance and answers for the next decision.
What to do now
This file appears low risk based on the evidence available now.
- Recovery step 01
Run it only when it came from the developer's official site or another source you independently trust.
- Recovery step 02
A clean result reduces known risk, but it cannot guarantee that every new or targeted threat has been detected.
- Recovery step 03
Keep your antivirus and Windows updates switched on so you stay protected.
Safety FAQ
Direct answers grounded in the saved verdict and evidence in this report.
Is z0nreccs.exe safe?
What is z0nreccs.exe?
How many antivirus engines detected z0nreccs.exe?
Is z0nreccs.exe digitally signed?
What is the SHA-256 hash of z0nreccs.exe?
Is it safe to run z0nreccs.exe?
How up to date is this analysis of z0nreccs.exe?
Community
Member reviews and reports for this exact file hash.