Is libcrypto-1_1.dll safe?
Widely distributed OpenSSL crypto DLL with zero engine detections and years of clean history.
Zero of 75 engines flagged the file. It is a common, long-standing OpenSSL library component with no malicious indicators in sandbox or child-file analysis.
d57b97e188783c5d88…0d655b51ee4ed4Recommended next actions
Before using
Use it only as part of software obtained from the developer's official site or another source you independently trust.
If you already used 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 common, long-standing OpenSSL library component with no malicious indicators in sandbox or child-file analysis.
The file shows no detections across the entire engine set, including all tier-1 engines. Its prevalence classification as common_old and first-seen date in 2017 indicate it is a widely used legitimate component. Sandbox execution produced only ambient techniques and no malicious verdict. The CIRCL hit is a neutral reference-database entry rather than a malicious flag. No RAG matches or triggered heuristics contradict the clean profile.
What We Detected
75 engines scanned the 2 MB Win32 DLL; none returned a malicious or suspicious result. The file is unsigned but carries the expected import hash and section layout of an OpenSSL build.
Threat Behavior
One sandbox run recorded only routine system queries and no outbound C2 or persistence actions. Ten dropped children were inspected; none carried malicious verdicts. No contacted domains or IPs were present for reputation cross-check.
What To Do Now
The file can be treated as a standard OpenSSL runtime component. Keep endpoint protection enabled and obtain future copies from trusted sources.
- Zero detections across 75 engines
- Common_old prevalence with 1862 submitters
- No malicious sandbox verdict or dropped children
Retain the file; it matches the expected profile of a legitimate OpenSSL library component.
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
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
- 14MITRE ATT&CK techniques
- 15spawned processes
- 0network contacts
- 36filesystem & 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
libcrypto-1_1.dll
d57b97e188783c5d886d0923f395cce53a98acef34f1e420790d655b51ee4ed4
01Uploaded file
Processes
Runtime execution
- ProcessObserved
Observed process
"C:\Windows\System32\rundll32.exe" "C:\Users\<USER>\AppData\Local\Temp\init.dll",#1
02Isolated runtime analysis - ProcessObserved
Observed process
C:\Windows\SysWOW64\WerFault.exe -u -p 2224 -s 748
03Isolated runtime analysis - +1 more recorded observation in Analyst mode
Files
Created or changed
- Written fileObserved
WER53A3.tmp
C:\ProgramData\Microsoft\Windows\WER\Temp\WER53A3.tmp
04Isolated runtime analysis - Written fileObserved
WER53A3.tmp.dmp
C:\ProgramData\Microsoft\Windows\WER\Temp\WER53A3.tmp.dmp
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:\ProgramData\Microsoft\Windows\WER\Temp\WER53A3.tmp
- C:\ProgramData\Microsoft\Windows\WER\Temp\WER53A3.tmp.dmp
- C:\ProgramData\Microsoft\Windows\WER\Temp\WER53F1.tmp
- C:\ProgramData\Microsoft\Windows\WER\Temp\WER53F1.tmp.dmp
- C:\ProgramData\Microsoft\Windows\WER\Temp\WER5569.tmp
- C:\ProgramData\Microsoft\Windows\WER\Temp\WER4BF3.tmp
- C:\ProgramData\Microsoft\Windows\WER\Temp\WER4FAD.tmp
- C:\ProgramData\Microsoft\Windows\WER\Temp\WER5116.tmp
- C:\ProgramData\Microsoft\Windows\WER\Temp\WER4BF3.tmp.dmp
- C:\ProgramData\Microsoft\Windows\WER\Temp\WER4FAD.tmp.WERInternalMetadata.xml
- Local\WERReportingForProcess2224
- Global\AmiProviderMutex_InventoryApplicationFile
- Global\bd4fe5f4-6311-45ce-8764-6df1a44baba8
- \Sessions\1\BaseNamedObjects\Local\WERReportingForProcess4700
- \Sessions\1\BaseNamedObjects\Global\4e11e1fb-0b02-45a0-ac7b-ebb02bf6c9aa
Files this sample writes at runtime
This file drops 10 children at runtime. None are currently flagged malicious in our cache.
- 8ebad4da962282023c74…db5a7aNever scannednever seen before
- 474424b5f941d6d5ad85…5c044bNever scannednever seen before
- 73263f9258efaab22e53…354157Never scannednever seen before
- b781ccef78f9a8707a81…b14cedNever scannednever seen before
- d4ed0c6119c4ee926bd4…28ddfcNever scannednever seen before
- cfa60e39e8ff69f59919…fd0b6fNever scannednever seen before
- 49ca232d155ae7f83ade…0c606bNever scannednever seen before
- f6c3258ec03cb18f619f…b314e2Never scannednever seen before
- 2d5448700bc2321f1db6…d1e111Never scannednever seen before
- 92799b2da1a13c3fa450…00cd5bNever 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 / 75engines flagged
- 1,862sources 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 appears in a known-software reference database.
Verdict inputView chapterProvenanceObservedSourceReference software databaseObserved at - 03
The hash has a long, established submission history across 1,862 sources.
Verdict inputView chapterProvenanceDerivedSourceSubmission historyObserved at - 04
Scanned file: libcrypto-1_1.dll — d57b97e188783c5d886d0923f395cce53a98acef34f1e420790d655b51ee4ed4
ProvenanceObservedSourceUploaded fileObserved at - 05
Observed process — "C:\Windows\System32\rundll32.exe" "C:\Users\<USER>\AppData\Local\Temp\init.dll",#1
ProvenanceObservedSourceIsolated runtime analysisObserved at - 06
Observed process — C:\Windows\SysWOW64\WerFault.exe -u -p 2224 -s 748
ProvenanceObservedSourceIsolated runtime analysisObserved at - 07
File written: WER53A3.tmp — C:\ProgramData\Microsoft\Windows\WER\Temp\WER53A3.tmp
ProvenanceObservedSourceIsolated runtime analysisObserved at - 08
File written: WER53A3.tmp.dmp — C:\ProgramData\Microsoft\Windows\WER\Temp\WER53A3.tmp.dmp
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.
YARA rules
No matchesThe rule pass completed without a saved public match.
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
- libcrypto-1_1.dll
- Format
- Win32 DLL
- Code signing
- No verified publisher
- Size
- 2.0 MB
- Last analyzed
- Aug 9, 2026, 3:00 PM UTC
d57b97e188783c5d886d0923f395cce53a98acef34f1e420790d655b51ee4ed4Safety & 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
Use it only as part of software obtained 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 libcrypto-1_1.dll safe?
What is libcrypto-1_1.dll?
How many antivirus engines detected libcrypto-1_1.dll?
What is the SHA-256 hash of libcrypto-1_1.dll?
Is it safe to use libcrypto-1_1.dll?
How up to date is this analysis of libcrypto-1_1.dll?
Community
Member reviews and reports for this exact file hash.