Is BleachBit-6.0.4-setup.exe safe?
One generic detection among 75 engines is outweighed by 17 clean tier-one results, a verified signature, broad circulation, and a non-malicious sandbox run.
Gridinsoft alone raised a generic trojan label, while all 17 tier-one engines reported no detection. The file is signed, broadly circulated, and produced no offensive techniques or malicious sandbox verdict, though its UPX packing and unchecked direct-IP contact warrant obtaining it from the official release channel.
c4cd6bb1f4b163dc28…43dcc6e7267a6dRecommended next actions
Before installing
Install it only when it came from the developer's official site or an official app store.
If you already installed 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.
Gridinsoft alone raised a generic trojan label, while all 17 tier-one engines reported no detection. The file is signed, broadly circulated, and produced no offensive techniques or malicious sandbox verdict, though its UPX packing and unchecked direct-IP contact warrant obtaining it from the official release channel.
The antivirus result is highly isolated: 1 of 75 engines flagged the sample, and that detection was a generic label rather than an identified family. All 17 tier-one engines reported no detection, which weighs strongly against the lone Gridinsoft result. A completed sandbox run produced no malicious verdict or offensive-only techniques, and none of seven inspected children was identified as malicious. The executable has a verified signature and substantial recent circulation, although the signer has no recorded history in the supplied evidence. UPX packing, high-entropy code, and direct communication with 162.159.36.2 are cautionary signals, but no complete reputation check is available for that address. The disclosed YARA matches describe signing and UPX characteristics rather than a malware family, making a false alarm the more likely explanation.
What We Detected
Only 1 of 75 antivirus engines flagged the executable. Gridinsoft reported the generic label Trojan.Win32.Gen.cl, while all 17 tier-one engines reported no detection and no engine consensus identified a malware family. The executable carries a verified signature from Open Source Developer, but the available records do not establish historical trust for that signer.
Threat Behavior
One completed sandbox run produced no malicious verdict and recorded no offensive-only techniques or persistence indicators. Seven dropped files were inspected without any being identified as malicious, although their individual outcomes remained unknown. The executable is UPX-packed and contains high-entropy code, and it contacted 162.159.36.2 directly; because contactedHosts is unavailable, no complete reputation result exists for that address. Eight community YARA rules matched, but the disclosed names concern Certum certificates, digital signing, and UPX packing rather than malicious behavior or a named family.
What To Do Now
Use a copy downloaded from the project's official release channel and verify its SHA-256 value and digital signature before installation. Keep endpoint protection enabled, and avoid the file if its source or signature differs from the expected release.
Where this verdict could be wrong4 caveats
- peAnalysis.likelyPacked=true and peAnalysis.highEntropyCode=true, which can obscure executable contents and reduce confidence.
- The sample contacted 162.159.36.2 directly, but contactedHosts=null means no complete host-reputation result is available.
- signing.signerStats.found=false and signing.trustedPublisher.matched=false, so the valid signature lacks corroborating publisher history.
- externalIntel.yaraify.ruleCount=8 is notable, although the disclosed rules are structural certificate and UPX matches rather than malware-family detections.
These are the assessment's weak points. If you believe one applies to your file, report the verdict and we'll re-review it.
- 17 tier-one engines reported no detection
- signing.verified=true
- behaviour.hasMaliciousSandboxVerdict=false
- behaviour.offensiveCount=0
- 577 submissions from 497 sources
- peAnalysis.likelyPacked=true with UPX
- peAnalysis.highEntropyCode=true
- Direct contact with 162.159.36.2 lacks a completed reputation cross-check
- signing.signerStats.found=false
- Gridinsoft reported Trojan.Win32.Gen.cl
Download the installer only from the official BleachBit release channel and verify its SHA-256 hash and signature. Keep antivirus and endpoint protection enabled during installation.
Coverage & freshness
Complete means the check returned a usable result. It does not mean the file is safe.
Antivirus
Complete1 of 75 engines flagged the file.
Sandbox
Complete1 isolated runtime environment contributed observations.
Network
Partial1 runtime contact was observed without a completed reputation cross-check.
YARA
Complete7 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
- 2spawned processes
- 1network contacts
- 20filesystem & 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.
- 162.159.36.2
- HKEY_USERS\S-1-5-21-4270068108-2931534202-3907561125-1001\Software\Microsoft\Windows\CurrentVersion\Explorer\FileExts\.exe\OpenWithProgids\exefile
- C:\Users\<USER>\AppData\Local\Temp\nstC842.tmp
- C:\Users\<USER>\AppData\Local\Temp\nsjC8A1.tmp\System.dll
- C:\Users\<USER>\AppData\Local\Temp\nsjC8A1.tmp\UserInfo.dll
- C:\Users\<USER>\AppData\Local\Temp\nsjC8A1.tmp\UAC.dll
- C:\Users\<USER>\AppData\Local\Temp\nsjC8A1.tmp\LangDLL.dll
- C:\Users\<USER>\AppData\Local\Temp\nsx30FF.tmp
- C:\Users\<USER>\AppData\Local\Temp\nst5A51.tmp
- C:\Users\<USER>\AppData\Local\Temp\nsbFAFB.tmp
- C:\Users\user\AppData\Local\Temp\nsiBAD6.tmp
- C:\Users\user\AppData\Local\Temp\nswB7D6.tmp
Files this sample writes at runtime
This file drops 7 children at runtime. None are currently flagged malicious in our cache.
- 0893c4d31c7d9c2106ee…6a7d15Never scannednever seen before
- 760df89c2341f9c39c02…dc1d8eNever scannednever seen before
- 947580be382ddf446f95…55491fNever scannednever seen before
- 996645d7f16a6294babb…dc51a5Never scannednever seen before
- 715a9b58de0995d1a083…fd2cb5Never scannednever seen before
- 2f7f8fc05dc4fd0d5cda…52dc08Never scannednever seen before
- e44bfda2eb8eef9c72cb…dbb7fcNever 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.
- 7rule hits recorded
- 1 / 75engines flagged
- 497sources in submission history
Why these facts are shown
Each statement identifies whether it was directly recorded or derived from saved scan facts.
- 01
The file has a valid code signature from Open Source Developer.
ProvenanceObservedSourceCode-signing metadataObserved at - 02
6 high-confidence signature or behavior rules matched this file.
Verdict inputView chapterProvenanceDerivedSourceSignature and behavior rulesObserved at - 03
1 of 75 antivirus engines flagged the file, including Gridinsoft.
Verdict inputView chapterProvenanceObservedSourceAntivirus analysisObserved at - 04
Scanned file: BleachBit-6.0.4-setup.exe — c4cd6bb1f4b163dc28b13cef2995423de69e6776f16387f54943dcc6e7267a6d
ProvenanceObservedSourceUploaded fileObserved at - 05
Observed process — "C:\Users\<USER>\Desktop\BleachBit-6.0.4-setup.exe"
ProvenanceObservedSourceIsolated runtime analysisObserved at - 06
Observed process — "C:\Users\user\Desktop\BleachBit-6.0.4-setup.exe"
ProvenanceObservedSourceIsolated runtime analysisObserved at - 07
File written: nstC842.tmp — C:\Users\<USER>\AppData\Local\Temp\nstC842.tmp
ProvenanceObservedSourceIsolated runtime analysisObserved at - 08
File written: System.dll — C:\Users\<USER>\AppData\Local\Temp\nsjC8A1.tmp\System.dll
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.
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.
- certum_issuer
- detect_certum_issuer
- PE_Digital_Certificate
- UPX
- upx_largefile
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.
Evidence162.159.36.2Packed PE with sandbox-observed network activity AND engine flags. Signed packed software exists legitimately, but a signed + packed + flagged binary is a signed dropper pattern.
Evidence162.159.36.2
1 of 75 engines flagged this file
View all 75 engine results
Section entropy & packers
Executable sections have high entropy (7.2+) — the code is compressed or encrypted and only decrypted at runtime. Classic packing behaviour.
Packers compress or encrypt the executable and only unpack it at runtime. Legitimate commercial software uses them too — but if the file is also unsigned and rare, it's a strong malware signal.
How widely this file has been seen
Lots of people are uploading this but it's recent — typical of newly-released legitimate software. Low prior for malware.
Fingerprint and provenance
- File name
- BleachBit-6.0.4-setup.exe
- Format
- Win32 EXE
- Code signing
- Signature valid: Open Source Developer
- Size
- 16.4 MB
- Last analyzed
- Sep 28, 2026, 5:33 PM UTC
c4cd6bb1f4b163dc28b13cef2995423de69e6776f16387f54943dcc6e7267a6dSafety & 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
Install it only when it came from the developer's official site or an official app store.
- 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 BleachBit-6.0.4-setup.exe safe?
What is BleachBit-6.0.4-setup.exe?
How many antivirus engines detected BleachBit-6.0.4-setup.exe?
Is BleachBit-6.0.4-setup.exe digitally signed?
What is the SHA-256 hash of BleachBit-6.0.4-setup.exe?
Is it safe to install BleachBit-6.0.4-setup.exe?
How up to date is this analysis of BleachBit-6.0.4-setup.exe?
Community
Member reviews and reports for this exact file hash.