Is zip_repair.exe safe?
Long-standing DiskInternals ZIP Repair installer with zero engine detections and widespread historical submissions.
Zero of 75 engines flagged the file. It is a 17-year-old NSIS installer for DiskInternals ZIP Repair that has been submitted by 1 293 sources and shows no malicious sandbox verdict or dropped malicious children.
0ffb1f63749877807b…35bb892463ac25Recommended 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.
Zero of 75 engines flagged the file. It is a 17-year-old NSIS installer for DiskInternals ZIP Repair that has been submitted by 1 293 sources and shows no malicious sandbox verdict or dropped malicious children.
The complete absence of detections across tier-1 and tier-2 engines, combined with the file’s age and prevalence, outweighs the two sandbox heuristics that themselves note the observed behaviour is also consistent with legitimate installers. No external-intel corroboration exists and no children or contacted hosts were flagged malicious. The unsigned status is typical for older NSIS packages and does not override the clean multi-engine record.
What We Detected
75-engine scan returned zero malicious or suspicious labels. The sample is an NSIS-packaged Win32 executable first submitted in 2008 and still widely distributed.
Threat Behavior
Sandbox execution recorded MITRE techniques T1055 and T1547.001 plus direct-IP connections, but no malicious verdict was issued and no malicious child files were dropped. Community comments reference the legitimate DiskInternals domain and product pages.
What To Do Now
The file matches a known commodity utility; keep endpoint protection enabled and download only from the vendor site if reinstallation is required.
Where this verdict could be wrong1 caveat
- Unsigned NSIS installer with direct-IP traffic and MITRE T1055/T1547.001 observed; contactedHosts cross-check not completed so no complete contacted-host reputation result was available.
These are the assessment's weak points. If you believe one applies to your file, report the verdict and we'll re-review it.
- Zero detections across 75 engines
- Common_old prevalence with 1 293 submitters since 2008
- No malicious sandbox verdict or dropped children
- Unsigned executable
- Direct-IP network traffic observed
The evidence supports treating the file as benign; retain existing security software and obtain future copies only from official vendor channels.
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
Partial20 runtime contacts were observed without a completed reputation cross-check.
YARA
Complete2 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
- 20MITRE ATT&CK techniques
- 12spawned processes
- 20network contacts
- 39filesystem & mutex artifacts
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
zip_repair.exe
0ffb1f63749877807bd61fcceb6e178c2902ab15f80a7bf41535bb892463ac25
01Uploaded file
Processes
Runtime execution
- ProcessObserved
Observed process
"C:\Users\<USER>\AppData\Local\Temp\executable.exe"
02Isolated runtime analysis - ProcessObserved
Observed process
%SAMPLEPATH%\0ffb1f63749877807bd61fcceb6e178c2902ab15f80a7bf41535bb892463ac25.exe
03Isolated runtime analysis - +1 more recorded observation in Analyst mode
Files
Created or changed
- Written fileObserved
ioSpecial.ini
C:\Documents and Settings\Administrator\Local Settings\Temp\nsa3.tmp\ioSpecial.ini
04Isolated runtime analysis - Written fileObserved
modern-wizard.bmp
C:\Documents and Settings\Administrator\Local Settings\Temp\nsa3.tmp\modern-wizard.bmp
05Isolated runtime analysis - +1 more recorded observation in Analyst mode
Network
Hosts contacted
- Contacted hostObserved
204.79.197.203
Contact observed during runtime.
06Isolated runtime analysis - Contacted hostObserved
23.215.176.154
Contact observed during runtime.
07Isolated runtime analysis - +1 more recorded observation in Analyst mode
7 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.
- 204.79.197.203
- 23.215.176.154
- 192.168.0.102
- a83f:8110:e0:ffff:e0:ffff:e0:ffff
- 23.216.147.64
- 23.216.147.76
- a83f:8110:0:0:a0b1:b403:0:0
- 20.99.132.105
- a83f:8110:0:0:9902:0:0:0
- 104.86.182.8
- C:\Documents and Settings\Administrator\Local Settings\Temp\nsa3.tmp\ioSpecial.ini
- C:\Documents and Settings\Administrator\Local Settings\Temp\nsa3.tmp\modern-wizard.bmp
- C:\Documents and Settings\Administrator\Local Settings\Temp\nsa3.tmp\InstallOptions.dll
- C:\Documents and Settings\Administrator\Local Settings\Temp\nsa3.tmp\StartMenu.dll
- C:\Program Files\DiskInternals\ZipRepair\ZipRepair.exe
- C:\Windows\System32\spp\store\2.0\cache\cache.dat
- C:\ProgramData\Microsoft\Windows\WER\Temp\WERE678.tmp.WERInternalMetadata.xml
- C:\ProgramData\Microsoft\Windows\WER\Temp\WERE7C0.tmp.csv
- C:\ProgramData\Microsoft\Windows\WER\Temp\WERE82E.tmp.txt
- C:\ProgramData\Microsoft\Windows\WER\Temp\WERF4D.tmp.WERInternalMetadata.xml
- CTF.LBES.MutexDefaultS-1-5-21-1482476501-1645522239-1417001333-500
- CTF.Compart.MutexDefaultS-1-5-21-1482476501-1645522239-1417001333-500
- CTF.Asm.MutexDefaultS-1-5-21-1482476501-1645522239-1417001333-500
- CTF.Layouts.MutexDefaultS-1-5-21-1482476501-1645522239-1417001333-500
- CTF.TMD.MutexDefaultS-1-5-21-1482476501-1645522239-1417001333-500
Files this sample writes at runtime
This file drops 10 children at runtime. None are currently flagged malicious in our cache.
- eaaac5d639a5371c27af…2ecc18Never scannednever seen before
- 0bd1f9a89d62b981bd92…e81a69Never scannednever seen before
- 3091623495d6e81bc0aa…eeaf51Never scannednever seen before
- 3ad2dc318056d0a2024a…056cf2Never scannednever seen before
- 77a9163ef4a05ee1ea06…8cc26fNever scannednever seen before
- 1e034ecb54c30417e810…d478c9Never scannednever seen before
- cb0063c30ee62104ee13…4fea9cNever scannednever seen before
- 1a62a6d50e45cdb19a31…e9c592Never scannednever seen before
- 993a81d62eed8a67f46a…22135bNever scannednever seen before
- 30a1d630dfcfd3b5b8af…2f77f2Never scannednever seen before
Detection & Forensics
Consensus, attribution, signatures, code structure, prevalence, and identity.
Evidence integrity
Chain of custody for the facts preserved in this report.
- 2rule hits recorded
- 0 / 75engines flagged
- 1,293sources 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 hash has a long, established submission history across 1,293 sources.
Verdict inputView chapterProvenanceDerivedSourceSubmission historyObserved at - 03
1 high-confidence signature or behavior rule matched this file.
Verdict inputView chapterProvenanceDerivedSourceSignature and behavior rulesObserved at - 04
Scanned file: zip_repair.exe — 0ffb1f63749877807bd61fcceb6e178c2902ab15f80a7bf41535bb892463ac25
ProvenanceObservedSourceUploaded fileObserved at - 05
Observed process — "C:\Users\<USER>\AppData\Local\Temp\executable.exe"
ProvenanceObservedSourceIsolated runtime analysisObserved at - 06
Observed process — %SAMPLEPATH%\0ffb1f63749877807bd61fcceb6e178c2902ab15f80a7bf41535bb892463ac25.exe
ProvenanceObservedSourceIsolated runtime analysisObserved at - 07
File written: ioSpecial.ini — C:\Documents and Settings\Administrator\Local Settings\Temp\nsa3.tmp\ioSpecial.ini
ProvenanceObservedSourceIsolated runtime analysisObserved at - 08
File written: modern-wizard.bmp — C:\Documents and Settings\Administrator\Local Settings\Temp\nsa3.tmp\modern-wizard.bmp
ProvenanceObservedSourceIsolated runtime analysisObserved at - 09
Contacted host: 204.79.197.203 — Contact observed during runtime.
ProvenanceObservedSourceIsolated runtime analysisObserved at - 10
Contacted host: 23.215.176.154 — Contact observed during runtime.
ProvenanceObservedSourceIsolated runtime analysisObserved at
Detection sources at a glance
The available sources did not agree on a named threat category.
MalwareBazaar, YARAify, and CIRCL hashlookup completed and returned no entries for 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.
The saved runtime evidence maps this activity to MITRE T1055 (Process Injection). The mapping supports possible process injection, but it does not prove the exact injection method or the operator's intent.
Evidence"C:\Users\<USER>\AppData\Local\Temp\executable.exe"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.
Evidence204.79.197.203 · 23.215.176.154 · a83f:8110:e0:ffff:e0:ffff:e0:ffff
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
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
- zip_repair.exe
- Format
- Win32 EXE
- Code signing
- No verified publisher
- Size
- 520.1 KB
- Last analyzed
- Sep 4, 2026, 5:13 AM UTC
0ffb1f63749877807bd61fcceb6e178c2902ab15f80a7bf41535bb892463ac25Safety & 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 zip_repair.exe safe?
What is zip_repair.exe?
How many antivirus engines detected zip_repair.exe?
What is the SHA-256 hash of zip_repair.exe?
Is it safe to run zip_repair.exe?
How up to date is this analysis of zip_repair.exe?
Community
Member reviews and reports for this exact file hash.