Threat LensFile scan report

Is EOSSDK-Win32-Shipping.dll safe?

Verdict
Safe

The verified Epic Games DLL drew no detections from 75 engines, while its isolated behavioral mappings lack corroborating malware or network evidence.

The DLL carries a verified Epic Games Inc. signature, and none of 75 antivirus engines detected it, including all 17 tier-1 engines. One sandbox mapped three offensive-capable techniques, but produced no malicious verdict, observed no network contacts, and found no known-malicious child.

Use with normal care

The evidence supports using this DLL when it came with an official Epic Games component or trusted game installation. Keep endpoint protection enabled and obtain a fresh copy from the official distribution channel if its origin is uncertain.

Read the full analysis
Saved file evidenceAntivirus consensus
0of 75 flagged
Flagged 0No detection 75
Digital specimenEOSSDK-Win32-Shipping.dll0372e1bc98993ba997…75949a6fe46372
Size13.5 MB
Code signingEpic Games Inc.
SandboxRuntime complete
First seen1y ago
Evidence3 priority signals
0 of 75 antivirus engines flagged the file.

Recommended next actions

01

Before using

Use it only as part of software obtained from the developer's official site or another source you independently trust.

02

If you already used it

Keep normal device protection enabled and stop if the file behaves unexpectedly.

Chapter 02

Intelligence

The saved assessment, checked against the scan evidence and recorded coverage.

MT AI Engine · Verdict analysis

The reasoning behind this verdict

This section explains the evidence supporting the verdict and keeps conflicting or missing signals visible.

94%Confidence
Very high
Analyst conclusion

The DLL carries a verified Epic Games Inc. signature, and none of 75 antivirus engines detected it, including all 17 tier-1 engines. One sandbox mapped three offensive-capable techniques, but produced no malicious verdict, observed no network contacts, and found no known-malicious child.

Where this verdict could be wrong4 caveats
  • behaviour.offensiveTechniques includes T1055, T1560, and T1562.001; the T1055 mapping came from rundll32 loading the DLL and does not by itself prove hostile process injection.
  • contactedHosts=null, so no completed host-reputation cross-check is available; however, the sandbox recorded no contacted domains, IPs, or URLs.
  • signing.signerStats.found=false, so no sample-history record independently supports the otherwise verified Epic Games signature.
  • All 10 droppedChildren.children entries have verdict=null, despite droppedChildren.hasMaliciousChild=false.

These are the assessment's weak points. If you believe one applies to your file, report the verdict and we'll re-review it.

Recommended action

The evidence supports using this DLL when it came with an official Epic Games component or trusted game installation. Keep endpoint protection enabled and obtain a fresh copy from the official distribution channel if its origin is uncertain.

Scan transparency

Coverage & freshness

4 of 5 complete

Complete means the check returned a usable result. It does not mean the file is safe.

  • Antivirus

    Complete

    0 of 75 engines flagged the file.

  • Sandbox

    Complete

    1 isolated runtime environment contributed observations.

  • Network

    Not run

    No contacted-host reputation check is recorded.

    No timestamp recorded
  • YARA

    Complete

    1 signature or behavior rule matched.

  • External intel

    Complete

    3 of 3 independent reference sources completed.

Chapter 03

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
  • 40filesystem & mutex artifacts
Recorded behavior

Attack story

Runtime observations grouped by analysis stage. Arrows organize the stages; they do not claim chronology or causality.

ObservedDerived

5 recorded facts from one runtime window. Every fact remains independently traceable in Analyst mode.

Chapter 04

Detection & Forensics

Consensus, attribution, signatures, code structure, prevalence, and identity.

Chapter 05

Safety & 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.

  1. Recovery step 01

    Use it only as part of software obtained from the developer's official site or another source you independently trust.

  2. Recovery step 02

    A clean result reduces known risk, but it cannot guarantee that every new or targeted threat has been detected.

  3. 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.

7 evidence-based answers
Is EOSSDK-Win32-Shipping.dll safe?
Evidence-based answer
EOSSDK-Win32-Shipping.dll appears safe. 0 of 75 antivirus engines flagged it. It carries a verified digital signature from Epic Games Inc.. Use it only as part of software obtained from the developer's official site or another source you independently trust.
What is EOSSDK-Win32-Shipping.dll?
Evidence-based answer
EOSSDK-Win32-Shipping.dll is a Windows library or loadable module, about 13.5 MB. Our analysis did not identify a verdict-driving threat signal. It carries a verified digital signature from Epic Games Inc.. A file's name can be reused by different files, so we identify it by its cryptographic hash (below).
How many antivirus engines detected EOSSDK-Win32-Shipping.dll?
Evidence-based answer
None — 0 of 75 antivirus engines flagged EOSSDK-Win32-Shipping.dll. That's reassuring, though it is not proof that a file is safe, so we also weigh its behaviour, identity, and reputation.
Is EOSSDK-Win32-Shipping.dll digitally signed?
Evidence-based answer
Yes — EOSSDK-Win32-Shipping.dll carries a valid digital signature from Epic Games Inc., which confirms the file hasn't been tampered with since that publisher signed it. A valid signature is a positive signal, but note that malware is occasionally signed with stolen or abused certificates, so it isn't proof of safety on its own.
What is the SHA-256 hash of EOSSDK-Win32-Shipping.dll?
Evidence-based answer
The SHA-256 hash of EOSSDK-Win32-Shipping.dll is 0372e1bc98993ba9976e9d4678295c8bc6ad3adf2555b368e275949a6fe46372, and its MD5 is 9b029fda8555b94198cd838a740bd8b7. 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.
Is it safe to use EOSSDK-Win32-Shipping.dll?
Evidence-based answer
Based on the recorded evidence, EOSSDK-Win32-Shipping.dll has a low observed risk and is properly signed. 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.
How up to date is this analysis of EOSSDK-Win32-Shipping.dll?
Evidence-based answer
This report reflects the scan run on September 13, 2026. Because a file's hash never changes, the identity of EOSSDK-Win32-Shipping.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.
Chapter 06

Community

Member reviews and reports for this exact file hash.

The raw file is processed temporarily and is not retained after processing. Its hash and report are public and permanent, so the next person who checks the same file gets an instant answer. Unknown files may be submitted to VirusTotal for analysis. If you ran this file on your computer and are worried, scan your system with an up-to-date antivirus and change critical passwords from a different device.