MalwareTips
Threat LensFile scan report

Is unins000.exe safe?

Verdict
Safe

No antivirus engine detected this established, GOG-signed uninstaller, while its broad prevalence and matching signer history outweigh the unverified direct-IP heuristic.

All 74 antivirus engines were free of detections, including 17 tier-1 engines, and the executable has a verified GOG signature. It has been widely submitted since 2019, while the direct-IP heuristic lacks a completed host-reputation check and is not corroborated by malware detections or sandbox verdicts.

Run with normal care

Use it if its verified GOG certificate and installation location match an expected GOG product. Keep endpoint protection enabled and obtain a fresh copy from the official installer if its origin is uncertain.

Read the full analysis
Saved file evidenceAntivirus consensus
0of 74 flagged
Flagged 0No detection 74
Digital specimenunins000.exe5761e7789d813626cd…c4ae9ec1dbaff3
Size1.3 MB
Code signingGOG Sp. z o.o.
SandboxRuntime complete
First seen7y ago
Evidence3 priority signals
0 of 74 antivirus engines flagged the file.

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.

91%Confidence
Very high
Analyst conclusion

All 74 antivirus engines were free of detections, including 17 tier-1 engines, and the executable has a verified GOG signature. It has been widely submitted since 2019, while the direct-IP heuristic lacks a completed host-reputation check and is not corroborated by malware detections or sandbox verdicts.

Where this verdict could be wrong4 caveats
  • behaviour.offensiveTechniques includes T1134, T1543.003, and T1547.001, although the single sandbox produced no malicious verdict or explicit persistence indicator.
  • MalwareTips.Synth.DirectIpC2 fired after direct-IP contacts were recorded; contactedHosts=null leaves those external addresses without a complete reputation cross-check.
  • One communityComments entry reports a malicious sandbox classification, but another report calls the sample informational, and neither is corroborated by the 0/74 engine result.
  • signing.signerStats.totalSamples=2 is too small to establish automatic signer trust.

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

Use it if its verified GOG certificate and installation location match an expected GOG product. Keep endpoint protection enabled and obtain a fresh copy from the official installer 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 74 engines flagged the file.

  • Sandbox

    Complete

    1 isolated runtime environment contributed observations.

  • Network

    Partial

    20 runtime contacts were observed without a completed reputation cross-check.

  • 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
  • 29MITRE ATT&CK techniques
  • 15spawned processes
  • 20network contacts
  • 33filesystem & mutex artifacts
Recorded behavior

Attack story

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

ObservedDerived

7 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

    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.

7 evidence-based answers
Is unins000.exe safe?
Evidence-based answer
unins000.exe appears safe. 0 of 74 antivirus engines flagged it. It carries a verified digital signature from GOG Sp. z o.o.. Run it only when it came from the developer's official site or another source you independently trust.
What is unins000.exe?
Evidence-based answer
unins000.exe is a Windows executable program, about 1.3 MB. Our analysis did not identify a verdict-driving threat signal. It carries a verified digital signature from GOG Sp. z o.o.. A file's name can be reused by different files, so we identify it by its cryptographic hash (below).
How many antivirus engines detected unins000.exe?
Evidence-based answer
None — 0 of 74 antivirus engines flagged unins000.exe. That's reassuring, though it is not proof that a file is safe, so we also weigh its behaviour, identity, and reputation.
Is unins000.exe digitally signed?
Evidence-based answer
Yes — unins000.exe carries a valid digital signature from GOG Sp. z o.o., 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 unins000.exe?
Evidence-based answer
The SHA-256 hash of unins000.exe is 5761e7789d813626cd68ee1e62429cfeb92bdd814cd29ef12fc4ae9ec1dbaff3, and its MD5 is 01190d8b6805fd4d2a68750fbd041966. 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 unins000.exe?
Evidence-based answer
Based on the recorded evidence, unins000.exe 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 unins000.exe?
Evidence-based answer
This report reflects the scan run on September 23, 2026. Because a file's hash never changes, the identity of unins000.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.

Scan another
Check a different file
URL instead?
Check if a link is safe
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.