Is Decryptolocker.exe safe?
Unsigned 4.4 MB PE with zero detections across 74 engines and long benign submission history.
No antivirus engine flagged the file. The sample is unsigned but shows only ambient behaviour in a single sandbox run and has been submitted by 196 sources since 2014 without malicious labels.
58b35c63ddab8f7f14…3aabc93dca02b8Recommended 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.
No antivirus engine flagged the file. The sample is unsigned but shows only ambient behaviour in a single sandbox run and has been submitted by 196 sources since 2014 without malicious labels.
Zero malicious detections from 74 engines, including 17 tier-1 engines, rules out active malware consensus. The file is unsigned, yet its age, prevalence, and lack of sandbox malice or dropped malicious children support a benign classification. Community comments reference a historical CryptoLocker recovery portal, but this does not alter the current clean engine results.
What We Detected
74 engines scanned the sample; none returned a malicious or suspicious result. The PE is unsigned and contains no packers. Sandbox execution produced only ambient MITRE techniques and wrote temporary Python runtime files.
Threat Behavior
No offensive techniques, no complete contacted-host reputation result was available contacts, and no malicious child files were observed. External intelligence sources (YARAify, CIRCL, MalwareBazaar) returned no hits.
What To Do Now
The file can be executed in an isolated environment if its purpose is understood. Keep endpoint protection enabled and avoid running untrusted executables from unknown sources.
Where this verdict could be wrong1 caveat
- communityComments contain references to CryptoLocker decryption portal and Hybrid-Analysis threat-score 58/100 — historical association with ransomware recovery tooling.
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 74 engines
- Long submission history without malicious labels
- No malicious dropped children or sandbox verdicts
The evidence supports treating the file as safe for its observed context; continue normal security practices.
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
Not runNo contacted-host reputation check is recorded.
No timestamp recordedYARA
CompleteRule evaluation completed with no recorded matches.
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
- 6spawned processes
- 0network contacts
- 31filesystem & 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
Decryptolocker.exe
58b35c63ddab8f7f1467bd753d4bcb7478c88b63f486b0acbb3aabc93dca02b8
01Uploaded file
Processes
Runtime execution
- ProcessObserved
Observed process
"C:\Users\<USER>\Desktop\executable.exe"
02Isolated runtime analysis - ProcessObserved
Observed process
C:\Documents and Settings\Administrator\Local Settings\Temp\EB93A6\996E.exe
03Isolated runtime analysis - +1 more recorded observation in Analyst mode
Files
Created or changed
- Written fileObserved
Microsoft.VC90.CRT.manifest
C:\Users\<USER>\AppData\Local\Temp\_MEI40402\Microsoft.VC90.CRT.manifest
04Isolated runtime analysis - Written fileObserved
msvcr90.dll
C:\Users\<USER>\AppData\Local\Temp\_MEI40402\msvcr90.dll
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.
- C:\Users\<USER>\AppData\Local\Temp\_MEI40402\Microsoft.VC90.CRT.manifest
- C:\Users\<USER>\AppData\Local\Temp\_MEI40402\msvcr90.dll
- C:\Users\<USER>\AppData\Local\Temp\_MEI40402\msvcp90.dll
- C:\Users\<USER>\AppData\Local\Temp\_MEI40402\msvcm90.dll
- C:\Users\<USER>\AppData\Local\Temp\_MEI40402\python27.dll
- C:\Documents and Settings\Administrator\Local Settings\Temp\_MEI4042\bz2.pyd
- C:\Documents and Settings\Administrator\Local Settings\Temp\_MEI4042\Crypto.Cipher._AES.pyd
- C:\Documents and Settings\Administrator\Local Settings\Temp\_MEI4042\Crypto.Cipher._DES.pyd
- C:\Documents and Settings\Administrator\Local Settings\Temp\_MEI4042\Crypto.Cipher._DES3.pyd
- C:\Documents and Settings\Administrator\Local Settings\Temp\_MEI4042\Crypto.Hash._SHA256.pyd
- ShimCacheMutex
Files this sample writes at runtime
This file drops 10 children at runtime. None are currently flagged malicious in our cache.
- 17fbe1dd26ac0b49b776…3a0fdbNever scannednever seen before
- 51054f4d28782b6698b1…bf4dfeNever scannednever seen before
- 4589dabefbfeb7f43250…bed384Never scannednever seen before
- 69c2d16001339775dba6…41f52cNever scannednever seen before
- 58e5017105a62445a85e…c0b044Never scannednever seen before
- f6435ab82110d7bd92a6…bd7a41Never scannednever seen before
- 3ca87759e0a427bd8f84…7df1a4Never scannednever seen before
- 1f9d29a98c029a0e5886…4bbd38Never scannednever seen before
- ff718390133b400ee679…5b3303Never scannednever seen before
- 36314665fa2a6effbe7a…e8e4d0Never 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.
- 0rule hits recorded
- 0 / 74engines flagged
- 196sources 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 74 antivirus engines flagged the file.
Verdict inputView chapterProvenanceObservedSourceAntivirus analysisObserved at - 02
The hash has a long, established submission history across 196 sources.
Verdict inputView chapterProvenanceDerivedSourceSubmission historyObserved at - 03
The hash has been submitted 203 times from 196 sources.
ProvenanceDerivedSourceSaved report factsObserved at - 04
Scanned file: Decryptolocker.exe — 58b35c63ddab8f7f1467bd753d4bcb7478c88b63f486b0acbb3aabc93dca02b8
ProvenanceObservedSourceUploaded fileObserved at - 05
Observed process — "C:\Users\<USER>\Desktop\executable.exe"
ProvenanceObservedSourceIsolated runtime analysisObserved at - 06
Observed process — C:\Documents and Settings\Administrator\Local Settings\Temp\EB93A6\996E.exe
ProvenanceObservedSourceIsolated runtime analysisObserved at - 07
File written: Microsoft.VC90.CRT.manifest — C:\Users\<USER>\AppData\Local\Temp\_MEI40402\Microsoft.VC90.CRT.manifest
ProvenanceObservedSourceIsolated runtime analysisObserved at - 08
File written: msvcr90.dll — C:\Users\<USER>\AppData\Local\Temp\_MEI40402\msvcr90.dll
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.
YARA rules
No matchesThe rule pass completed without a saved public match.
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
- Decryptolocker.exe
- Format
- Win32 EXE
- Code signing
- No verified publisher
- Size
- 4.2 MB
- Last analyzed
- Aug 17, 2026, 2:16 PM UTC
58b35c63ddab8f7f1467bd753d4bcb7478c88b63f486b0acbb3aabc93dca02b8Safety & 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 Decryptolocker.exe safe?
What is Decryptolocker.exe?
How many antivirus engines detected Decryptolocker.exe?
What is the SHA-256 hash of Decryptolocker.exe?
Is it safe to run Decryptolocker.exe?
How up to date is this analysis of Decryptolocker.exe?
Community
Member reviews and reports for this exact file hash.