Safe
Unsigned 18 kB DLL with zero engine detections and clean sandbox behaviour.
5f63675b27263c4462…2fa4296e6eThe reasoning behind this verdict
This section explains the evidence supporting the verdict and keeps conflicting or missing signals visible.
All 74 engines returned clean results, including 16 tier-1 engines. The file is unsigned and only one day old, yet the sandbox recorded only ambient techniques and no malicious verdict. The single triggered heuristic (DirectIpC2) is medium severity and can occur with legitimate software. Medium prevalence across five sources further supports a benign classification.
No antivirus engine flagged the file. The only notable signal is a medium-severity heuristic for direct-IP contact without DNS, which is inconclusive on its own. Sandbox execution produced no malicious indicators and no children were malicious.
What We Detected
74 engines scanned the 18 kB Win32 DLL; none returned a malicious or suspicious result. The file is unsigned and first appeared one day ago.
Threat Behavior
Sandbox execution showed 14 ambient MITRE techniques and zero offensive techniques. One external IP was contacted directly without DNS resolution, triggering a medium-severity heuristic, but no malicious verdict was issued and no malicious children were dropped.
What To Do Now
The file can be treated as clean for most purposes. If it must run in a high-security environment, monitor the direct-IP connection or request the original source for verification.
The strongest scan facts behind the verdict, preserved with their exact names and counts.
0 of 74 antivirus engines flagged the file.
The hash has been submitted 6 times from 5 sources.
- Zero engine detections across 74 scanners
- Clean sandbox verdict
- No malicious dropped children
- Unsigned DLL
- Direct IP contact without DNS (medium heuristic)
The sample shows no malicious indicators from engines or sandbox; treat as safe unless additional context suggests otherwise.
What to do now
This file looks safe based on everything we checked.
This file is safe to use.
Good habit: only download files from the official website or an app store.
Keep your antivirus and Windows updates switched on so you stay protected.
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:\Users\<USER>\AppData\Local\Microsoft\Windows\AdobeGCInvoker\winhttp.dll
- C:\Users\<USER>\AppData\Local\Microsoft\Windows\AdobeGCInvoker\AdobeGCInvoker.exe
- C:\Users\<USER>\AppData\Local\Microsoft\Windows\AdobeGCInvoker\Adobe.Acrobat.Dependencies.manifest
- C:\Users\user\AppData\Local\Microsoft\Windows\AdobeGCInvoker\
- C:\Users\user\AppData\Local\Microsoft\Windows\AdobeGCInvoker\winhttp.dll
Files this sample writes at runtime
This file drops 2 children at runtime. None are currently flagged malicious in our cache.
- 5f63675b27263c446278…296e6eNever scannednever seen before
- 255a65d30841ab4082bd…c12309Never scannednever seen before
Signatures and behavior heuristics
Behavioral heuristics matched patterns associated with malware. Corroborating evidence determines how much weight they carry.
Sample contacted 1 external IP address(es) and zero domains. Benign software virtually always uses DNS; no-DNS direct-IP C2 is a strong malware indicator because it bypasses reputation systems and dodges domain-based blocklists.
Evidence162.159.36.2
0 detections across 74 engines
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.
Forensic fingerprint
- File name
- winhttp.dll
- Size
- 18.0 KB
- MIME type
- (unknown)
- Detected type
- Win32 DLL
- SHA-256
- 5f63675b27263c446278bac88dc24345106b44294da8c20adfaa012fa4296e6e
- MD5
- eb4ce706240023cda8317b50043af383
- SHA-1
- b7c309770f9097f05a532babd11d432b0eb5cff2
- PE imphash
- 73d729634b70f5e80a6b5d0b43005322
- First seen (VT)
- Jul 22, 2026, 12:01 PM UTC
- Last analysis (VT)
- Jul 22, 2026, 12:01 PM UTC
- First scan (MalwareTips)
- Jul 23, 2026, 12:46 PM UTC
- Last scan (MalwareTips)
- Jul 23, 2026, 12:46 PM UTC
Safety FAQ
Common questions about winhttp.dll, answered from the scan data above.
- winhttp.dll appears safe. 74 of 74 antivirus engines report it clean. As a habit, only run files you downloaded from the official source, since attackers sometimes distribute trojanised copies of legitimate software under the same name.
- winhttp.dll is a Windows executable program, about 18 KB. Our analysis found no threat indicators for it. A file's name can be reused by different files, so we identify it by its cryptographic hash (below).
- None — all 74 antivirus engines we queried report winhttp.dll as clean. That's reassuring, though brand-new malware can briefly evade detection before vendors add signatures, so we also weigh the file's behaviour and reputation.
- The SHA-256 hash of winhttp.dll is 5f63675b27263c446278bac88dc24345106b44294da8c20adfaa012fa4296e6e, and its MD5 is eb4ce706240023cda8317b50043af383. 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 this scan, yes — winhttp.dll shows no threat indicators. 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 while we report it clean, that is most often a false positive, but verify the source before overriding your antivirus.
- This report reflects the scan run on July 23, 2026. Because a file's hash never changes, the identity of winhttp.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.
Reviews & malware reports(0)
Tell the community what you saw. Tag the sample — Trojan, Adware, False Positive — and share what the file did on your system. Your report helps confirm or dispute the AV verdict.