Is WinRAR.exe safe?
The verified WinRAR publisher signature, zero detections across 73 engines, and absence of a malicious sandbox verdict outweigh several uncorroborated behavioral alerts.
This executable is signed and verified by win.rar GmbH, with the publisher matching WinRAR, and 0 of 73 engines detected malware. One sandbox produced process-injection, LSASS, and direct-IP heuristic signals, but it issued no malicious verdict, and no inspected child was identified as malicious.
bbc088fc6e1b990425…b91ea7f869436cRecommended 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.
This executable is signed and verified by win.rar GmbH, with the publisher matching WinRAR, and 0 of 73 engines detected malware. One sandbox produced process-injection, LSASS, and direct-IP heuristic signals, but it issued no malicious verdict, and no inspected child was identified as malicious.
The strongest evidence is the verified signature from win.rar GmbH and the trusted-publisher match for WinRAR. None of 73 engines flagged the sample, including all 17 reporting tier-1 engines. One completed sandbox run generated heuristic mappings for T1055 and T1134 and referenced LSASS, but it did not issue a malicious sandbox verdict. Ten dropped children were inspected without identifying a malicious child, although their individual classifications remain unknown. A prior file sharing this imphash and signer was also assessed as benign, while meaningful submission prevalence further supports legitimate distribution. Network reputation remains unresolved because the observed IP did not receive a saved host-reputation cross-check.
What We Detected
The file is a 64-bit Windows executable signed by win.rar GmbH. Its signature verifies successfully and matches the trusted WinRAR publisher entry. None of 73 antivirus engines reported a detection, including 17 tier-1 engines.
Threat Behavior
One sandbox run mapped activity to T1055 and T1134, referenced LSASS-related process activity, and recorded direct communication with 162.159.36.2. These are legitimate caution signals, but the sandbox issued no malicious verdict, no persistence indicators were recorded, and none of 10 inspected dropped children was identified as malicious. The contacted IP was not covered by a completed saved reputation check, so its status remains unresolved.
What To Do Now
Confirm that the digital signature still reports win.rar GmbH before installation and prefer obtaining WinRAR directly from its official release channel. Keep endpoint protection enabled and rescan if the signature fails verification or the file behaves differently from a normal archive utility installer.
Where this verdict could be wrong4 caveats
- behaviour.offensiveTechniques includes T1055 and T1134, and the heuristic evidence references LSASS activity; these observations warrant caution despite lacking a malicious sandbox verdict.
- behaviour.contactedIps includes 162.159.36.2, but contactedHosts=null, so no complete reputation result is available for that network contact.
- signing.signerStats contains only 1 historical sample, so its 100% safe rate is too small to establish a strong publisher history.
- All 10 dropped children have unknown individual verdicts even though droppedChildren.hasMaliciousChild=false.
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 73 antivirus engines detected the file.
- Verified digital signature from win.rar GmbH.
- Trusted-publisher match identifies WinRAR.
- No malicious sandbox verdict was produced.
- No malicious child was identified among 10 inspected files.
- Sandbox heuristic mapped possible process-injection activity to T1055.
- Sandbox heuristic mapped token-related activity to T1134.
- Saved process evidence referenced lsass.exe, producing a credential-access warning.
- Direct-IP communication to 162.159.36.2 lacks a completed host-reputation cross-check.
- The signer history contains only 1 prior sample.
- The 10 dropped children lack individual verdicts.
Use the file only if its Windows signature verifies as win.rar GmbH and it came from WinRAR's official release channel. Keep endpoint protection enabled and investigate any unexpected credential-access or process-injection alerts during use.
Coverage & freshness
Complete means the check returned a usable result. It does not mean the file is safe.
Antivirus
Complete0 of 73 engines flagged the file.
Sandbox
Complete1 isolated runtime environment contributed observations.
Network
Partial1 runtime contact was observed without a completed reputation cross-check.
YARA
Complete3 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
- 28MITRE ATT&CK techniques
- 9spawned processes
- 1network contacts
- 40filesystem & 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
WinRAR.exe
bbc088fc6e1b99042567144cd6601901d955703d8062e299bdb91ea7f869436c
01Uploaded file
Processes
Runtime execution
- ProcessObserved
Observed process
"C:\Users\<USER>\Desktop\winrar-x64-722.exe"
02Isolated runtime analysis - ProcessObserved
Observed process
"C:\Program Files\WinRAR\uninstall.exe" /setup
03Isolated runtime analysis - +1 more recorded observation in Analyst mode
Files
Created or changed
- Written fileObserved
__tmp_rar_sfx_access_check_58187
C:\Program Files\WinRAR\__tmp_rar_sfx_access_check_58187
04Isolated runtime analysis - Written fileObserved
Descript.ion
C:\Program Files\WinRAR\Descript.ion
05Isolated runtime analysis - +1 more recorded observation in Analyst mode
Network
Hosts contacted
- Contacted hostObserved
162.159.36.2
Contact observed during runtime.
06Isolated runtime analysis
6 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.
- 162.159.36.2
- C:\Program Files\WinRAR\__tmp_rar_sfx_access_check_58187
- C:\Program Files\WinRAR\Descript.ion
- C:\Program Files\WinRAR\ReadMe.txt
- C:\Program Files\WinRAR\License.txt
- C:\Program Files\WinRAR\Rar.txt
- C:\Program Files\WinRAR\__tmp_rar_sfx_access_check_58187
- C:\Users\Public\Desktop\WinRAR.lnk
- C:\Users\user\AppData\Roaming\Microsoft\Windows\Start Menu\Programs\WinRAR\Guida a WinRAR.lnk
- C:\Users\user\AppData\Roaming\Microsoft\Windows\Start Menu\Programs\WinRAR\Manuale di RAR in modalit\xe0 carattere.lnk
- C:\Users\user\AppData\Roaming\Microsoft\Windows\Start Menu\Programs\WinRAR\Novit\xe0 dell'ultima versione.lnk
- Local\MSCTF.Asm.MutexDefault1
- DefaultTabtip-MainUI
- Local\ZonesCacheCounterMutex
- Local\ZonesLockedCacheCounterMutex
- !IECompat!Mutex
Files this sample writes at runtime
This file drops 10 children at runtime. None are currently flagged malicious in our cache.
- fcd13e1b97af47b8b923…f7f2e6Never scannednever seen before
- fd545dc2151054002f9d…1a87fcNever scannednever seen before
- 9cc712f36c3b6dbf8970…a3c7c9Never scannednever seen before
- 6c1bdd724c333d88b927…1cf08fNever scannednever seen before
- 412c0b61282119c7b62a…25f4caNever scannednever seen before
- ed99246ebc6fad80103f…884ab2Never scannednever seen before
- 830d8bafaa773e1163dd…44b01aNever scannednever seen before
- 7a83c9c255d3893eb86c…2b943dNever scannednever seen before
- a7bb097441d9f06dd7a8…1b52f0Never scannednever seen before
- 8d42f3961e0e381ee32d…cd98e6Never 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.
- 3rule hits recorded
- 0 / 73engines flagged
- 3,211sources 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 73 antivirus engines flagged the file.
Verdict inputView chapterProvenanceObservedSourceAntivirus analysisObserved at - 02
The file has a valid code signature from win.rar GmbH.
ProvenanceObservedSourceCode-signing metadataObserved at - 03
1 high-confidence signature or behavior rule matched this file.
Verdict inputView chapterProvenanceDerivedSourceSignature and behavior rulesObserved at - 04
Scanned file: WinRAR.exe — bbc088fc6e1b99042567144cd6601901d955703d8062e299bdb91ea7f869436c
ProvenanceObservedSourceUploaded fileObserved at - 05
Observed process — "C:\Users\<USER>\Desktop\winrar-x64-722.exe"
ProvenanceObservedSourceIsolated runtime analysisObserved at - 06
Observed process — "C:\Program Files\WinRAR\uninstall.exe" /setup
ProvenanceObservedSourceIsolated runtime analysisObserved at - 07
File written: __tmp_rar_sfx_access_check_58187 — C:\Program Files\WinRAR\__tmp_rar_sfx_access_check_58187
ProvenanceObservedSourceIsolated runtime analysisObserved at - 08
File written: Descript.ion — C:\Program Files\WinRAR\Descript.ion
ProvenanceObservedSourceIsolated runtime analysisObserved at - 09
Contacted host: 162.159.36.2 — 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.
EvidenceC:\Windows\System32\svchost.exe -k NetworkService -pSandbox observed process activity targeting LSASS (Windows credential store). Legitimate software has no business reading LSASS memory — this is Mimikatz-shape behaviour.
EvidenceC:\Windows\system32\lsass.exeThe 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.
Evidence162.159.36.2
0 of 73 engines flagged this file
View all 73 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
- WinRAR.exe
- Format
- Win32 EXE
- Code signing
- Signature valid: win.rar GmbH
- Size
- 3.6 MB
- Last analyzed
- Sep 22, 2026, 7:25 AM UTC
bbc088fc6e1b99042567144cd6601901d955703d8062e299bdb91ea7f869436cSafety & 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 WinRAR.exe safe?
What is WinRAR.exe?
How many antivirus engines detected WinRAR.exe?
Is WinRAR.exe digitally signed?
What is the SHA-256 hash of WinRAR.exe?
Is it safe to run WinRAR.exe?
How up to date is this analysis of WinRAR.exe?
Community
Member reviews and reports for this exact file hash.