Our call: Is glfw3.dll safe?Safe
- 0 of 75 antivirus engines flagged the file.Observed · Antivirus analysis
- The hash has a long, established submission history across 2,546 sources.Derived · Submission history
- 3 high-confidence signature or behavior rules matched this file.Derived · Signature and behavior rules
e15c2dca331d4c15b7…016eaa93eaRecommended 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.
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
Partial1 of 2 contacted hosts were cross-checked; coverage is incomplete.
YARA
Complete4 signature or behavior rules matched.
External intel
Complete3 of 3 independent reference sources completed.
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
glfw3.dll
e15c2dca331d4c15b7f60fbad81f7774ec4cf23c94484d4dc1912c016eaa93ea
01Uploaded file
Processes
Runtime execution
- ProcessObserved
Observed process
"C:\Windows\sysnative\rundll32.exe" "C:\Users\<USER>\AppData\Local\Temp\attachment.dll",#1
02Isolated runtime analysis - ProcessObserved
Observed process
C:\Windows\System32\loaddll64.exe loaddll64.exe "C:\Users\user\Desktop\readme.dll"
03Isolated runtime analysis - +1 more recorded observation in Analyst mode
Files
Created or changed
- Written fileObserved
AppCrash_rundll32.exe_rea_10248191228da35c8a822e1cfc30372e64a5adfb_b7758387_1fbf672a
C:\ProgramData\Microsoft\Windows\WER\ReportQueue\AppCrash_rundll32.exe_rea_10248191228da35c8a822e1cfc30372e64a5adfb_b7758387_1fbf672a
04Isolated runtime analysis - Written fileObserved
Report.wer
C:\ProgramData\Microsoft\Windows\WER\ReportQueue\AppCrash_rundll32.exe_rea_10248191228da35c8a822e1cfc30372e64a5adfb_b7758387_1fbf672a\Report.wer
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
crt.sectigo.com
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.
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 2,546 sources.
Verdict inputView chapterProvenanceDerivedSourceSubmission historyObserved at - 03
3 high-confidence signature or behavior rules matched this file.
Verdict inputView chapterProvenanceDerivedSourceSignature and behavior rulesObserved at - 04
Scanned file: glfw3.dll — e15c2dca331d4c15b7f60fbad81f7774ec4cf23c94484d4dc1912c016eaa93ea
ProvenanceObservedSourceUploaded fileObserved at - 05
Observed process — "C:\Windows\sysnative\rundll32.exe" "C:\Users\<USER>\AppData\Local\Temp\attachment.dll",#1
ProvenanceObservedSourceIsolated runtime analysisObserved at - 06
Observed process — C:\Windows\System32\loaddll64.exe loaddll64.exe "C:\Users\user\Desktop\readme.dll"
ProvenanceObservedSourceIsolated runtime analysisObserved at - 07
File written: AppCrash_rundll32.exe_rea_10248191228da35c8a822e1cfc30372e64a5adfb_b7758387_1fbf672a — C:\ProgramData\Microsoft\Windows\WER\ReportQueue\AppCrash_rundll32.exe_rea_10248191228da35c8a822e1cfc30372e64a5adfb_b7758387_1fbf672a
ProvenanceObservedSourceIsolated runtime analysisObserved at - 08
File written: Report.wer — C:\ProgramData\Microsoft\Windows\WER\ReportQueue\AppCrash_rundll32.exe_rea_10248191228da35c8a822e1cfc30372e64a5adfb_b7758387_1fbf672a\Report.wer
ProvenanceObservedSourceIsolated runtime analysisObserved at - 09
Contacted host: 204.79.197.203 — Contact observed during runtime.
ProvenanceObservedSourceIsolated runtime analysisObserved at - 10
Contacted host: crt.sectigo.com — Contact observed during runtime.
ProvenanceObservedSourceIsolated runtime analysisObserved at
Intelligence
The saved assessment, checked against the scan evidence and recorded coverage.
No saved analyst narrative
This report keeps the verified scan facts available below without inventing an analysis that was not saved with the scan.
Behavior
Plain-English impact first, then the observed runtime evidence.
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
- http://crt.sectigo.com/SectigoPublicCodeSigningCAR36.crt
- http://crt.sectigo.com/SectigoPublicCodeSigningRootR46.p7c
- C:\ProgramData\Microsoft\Windows\WER\ReportQueue\AppCrash_rundll32.exe_rea_10248191228da35c8a822e1cfc30372e64a5adfb_b7758387_1fbf672a
- C:\ProgramData\Microsoft\Windows\WER\ReportQueue\AppCrash_rundll32.exe_rea_10248191228da35c8a822e1cfc30372e64a5adfb_b7758387_1fbf672a\Report.wer
- C:\ProgramData\Microsoft\Windows\WER\Temp\WER5651.tmp
- C:\ProgramData\Microsoft\Windows\WER\Temp\WER5651.tmp.dmp
- C:\ProgramData\Microsoft\Windows\WER\Temp\WER5817.tmp
- C:\ProgramData\Microsoft\Windows\WER\Temp\WER5651.tmp
- C:\ProgramData\Microsoft\Windows\WER\Temp\WER5651.tmp.dmp
- C:\ProgramData\Microsoft\Windows\WER\Temp\WER5817.tmp
- C:\ProgramData\Microsoft\Windows\WER\Temp\WER5817.tmp.WERInternalMetadata.xml
- C:\ProgramData\Microsoft\Windows\WER\Temp\WER5941.tmp
- \Sessions\1\BaseNamedObjects\Local\WERReportingForProcess7804
- \Sessions\1\BaseNamedObjects\Global\82646432-8982-491f-8358-0cb65b371d5d
Files this sample writes at runtime
This file drops 3 children at runtime. None are currently flagged malicious in our cache.
- b33efcb95235b98b4850…29307fNever scannednever seen before
- 3693bf8896e0a274503c…b1d60dNever scannednever seen before
- 33f064cb06a737ea3c0e…fccee1Never scannednever seen before
Detection & Forensics
Consensus, attribution, signatures, code structure, prevalence, and identity.
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.
- cobalt_strike_tmp01925d3f
- DebuggerCheck__API
MITRE T1055 (Process Injection) observed — CreateRemoteThread / APC / reflective-DLL injection. The payload is being smuggled into a legitimate process to bypass AV hooks.
Evidence"C:\Windows\sysnative\rundll32.exe" "C:\Users\<USER>\AppData\Local\Temp\attachment.dll",#1The 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
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
- glfw3.dll
- Format
- Win32 DLL
- Code signing
- No verified publisher
- Size
- 346.5 KB
- Last analyzed
- Jun 10, 2026, 1:38 PM UTC
e15c2dca331d4c15b7f60fbad81f7774ec4cf23c94484d4dc1912c016eaa93eaSafety & 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.
Use it only as part of software obtained from the developer's official site or another source you independently trust.
A clean result reduces known risk, but it cannot guarantee that every new or targeted threat has been detected.
Keep your antivirus and Windows updates switched on so you stay protected.
Safety FAQ
- glfw3.dll appears safe. 0 of 75 antivirus engines flagged it. Use it only as part of software obtained from the developer's official site or another source you independently trust.
- glfw3.dll is a Windows library or loadable module, about 347 KB. Our analysis did not identify a verdict-driving threat signal. A file's name can be reused by different files, so we identify it by its cryptographic hash (below).
- None — 0 of 75 antivirus engines flagged glfw3.dll. That's reassuring, though it is not proof that a file is safe, so we also weigh its behaviour, identity, and reputation.
- The SHA-256 hash of glfw3.dll is e15c2dca331d4c15b7f60fbad81f7774ec4cf23c94484d4dc1912c016eaa93ea, and its MD5 is 529bf9fb63a41e5cc66cb1fc0b4303d7. This hash is the file's unique fingerprint — two files with the same SHA-256 are identical. Use it to confirm you're looking at exactly this file (not just one with the same name) when comparing against antivirus databases or a download's published checksum.
- Based on the recorded evidence, glfw3.dll has a low observed risk. The important caveat is source: make sure you downloaded it from the official website or a trusted store, because attackers sometimes distribute malware-laced copies under a legitimate file's name. If your own antivirus flags it, verify the source and the exact hash before overriding the warning.
- This report reflects the scan run on June 10, 2026. Because a file's hash never changes, the identity of glfw3.dll is fixed — but antivirus coverage improves over time, so a file that looks clean today can pick up detections later (and vice-versa). If you need the latest picture, MalwareTips staff can re-run the analysis from scratch.