Threat LensFile scan report

Is Gothic.exe safe?

Verdict
Safe

Only APEX flagged this long-established file, while 17 tier-1 engines, completed runtime checks, child inspection, and host-reputation checks supplied no corroborating threat evidence.

Only 1 of 75 engines detected the file, and that result came from low-trust APEX while every tier-1 engine remained silent. Although runtime mapping includes process injection and service creation, the completed sandbox produced no malicious verdict, all observed hosts were covered without hostile findings, and none of the ten inspected children was identified as malware.

Run with normal care

Keep security protection enabled and prefer a copy obtained from the original trusted source. Exercise extra caution only if the file's origin is unknown or its Edge-update-related activity is inconsistent with its expected purpose.

Read the full analysis
Saved file evidenceAntivirus consensus
1of 75 flagged
Flagged 1No detection 74
Digital specimenGothic.exe4a6920bf69a259efdb…0026e9439effbc
Size8.2 MB
Code signingUnsigned
SandboxRuntime complete
First seen17y ago
Evidence3 priority signals
The hash has a long, established submission history across 267 sources.

Recommended next actions

01

Before running

Run it only when it came from the developer's official site or another source you independently trust.

02

If you already ran 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.

88%Confidence
Very high
Analyst conclusion

Only 1 of 75 engines detected the file, and that result came from low-trust APEX while every tier-1 engine remained silent. Although runtime mapping includes process injection and service creation, the completed sandbox produced no malicious verdict, all observed hosts were covered without hostile findings, and none of the ten inspected children was identified as malware.

Where this verdict could be wrong3 caveats
  • The executable is unsigned even though signing.applicable=true, so no publisher identity can be authenticated.
  • Runtime evidence includes offensive techniques T1055 and T1543.003, including a high-severity process-injection heuristic; these mappings warrant caution despite lacking corroboration.
  • The sandbox recorded long-sleep and debugging-environment indicators, which can reflect evasion but can also occur in older or complex software.

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

Keep security protection enabled and prefer a copy obtained from the original trusted source. Exercise extra caution only if the file's origin is unknown or its Edge-update-related activity is inconsistent with its expected purpose.

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

    1 of 75 engines flagged the file.

  • Sandbox

    Complete

    1 isolated runtime environment contributed observations.

  • Network

    Partial

    12 of 26 contacted hosts were cross-checked; coverage is incomplete.

  • 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
  • 12MITRE ATT&CK techniques
  • 4spawned processes
  • 26network contacts
  • 40filesystem & mutex artifacts
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

    Run it only when it came 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.

6 evidence-based answers
Is Gothic.exe safe?
Evidence-based answer
Gothic.exe appears safe. 1 of 75 antivirus engines flagged it; the 1 detection were treated as non-decisive after the wider evidence was weighed. Run it only when it came from the developer's official site or another source you independently trust.
What is Gothic.exe?
Evidence-based answer
Gothic.exe is a Windows executable program, about 8.2 MB. 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).
How many antivirus engines detected Gothic.exe?
Evidence-based answer
1 of 75 antivirus engines flagged Gothic.exe, 1 of them as outright malicious. The raw count alone does not establish safety or danger; we also weigh which engines flagged it and corroborating behavior, identity, reputation, and rule evidence.
What is the SHA-256 hash of Gothic.exe?
Evidence-based answer
The SHA-256 hash of Gothic.exe is 4a6920bf69a259efdbb94dbcd8ddd4a0ac81d4d39711a2d6df0026e9439effbc, and its MD5 is e0144b8b8cc690cd2e416e473d94d0a8. 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 run Gothic.exe?
Evidence-based answer
Based on the recorded evidence, Gothic.exe 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.
How up to date is this analysis of Gothic.exe?
Evidence-based answer
This report reflects the scan run on September 28, 2026. Because a file's hash never changes, the identity of Gothic.exe 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.