File scan report
Verdict Malicious
Is GHOST SETUP safe? No, we rate this exact file malicious.
Nine of the 69 antivirus engines that checked it flagged this unsigned, protected executable, while evidence from the test run recorded concrete policy changes aimed at disabling…
Read the whole reasonShow less
Strong evidence · Two or more major antivirus engines agree.
If you already installed it, follow the steps below.
What to do now4 steps
This file is harmful. Don't run it, and remove it.
If you haven't installed it
Don't install this file. Delete it, then empty the Recycle Bin.
If you already installed it
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.
If you typed passwords on the device after running it, change them from another device you trust.
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.
- Trojan removal guideClear steps for Windows, Mac and Android. (opens malwaretips.com in a new tab)
- Remove malware from WindowsStep-by-step cleanup with free tools. (opens malwaretips.com in a new tab)
- Ask for free help on the MalwareTips forumWindows malware removal help, answered by volunteers. (opens malwaretips.com in a new tab)
Paste this report's link in your topic so helpers can see what was found.
Antivirus results
9 of 69 flagged
- Flagged 9
- No detection 60
- No result 5
- Code signing Unsigned
- Test run Completed
- First seen 6y ago
Chapter 02
Why we think so
5 points against it and 4 in its favour, checked against the scan evidence.
The reasoning behind this verdict
Three major antivirus engines and six other independent engines detected the executable, mainly as a generic or MSIL loader. More importantly, evidence from the test run recorded Windows Defender real-time protection policy changes, corroborating the defence-evasion mapping; keep security software enabled and do not run the file.
Nine of the 69 antivirus engines that checked it flagged the executable, including three major antivirus engines, although they did not establish a strong consensus on a specific family. The runtime record contains registry changes targeting Windows Defender real-time protection, providing concrete support for the defence-evasion mapping. The file is also unsigned and protected with Smart Assembly, which adds concern when combined with the detections and runtime artefact. The mapping is not counted as evidence of injection because no target process was recorded. Contrary evidence includes a clean combined sandbox verdict, no adverse host-reputation matches among the inspected contacts, and broad historical prevalence, but these points do not adequately explain the defence changes.
What We Detected
Nine of the 69 antivirus engines that checked it flagged this Windows executable. Fortinet, TrellixENS, and TrendMicro-HouseCall were among the major detectors, while several labels described an MSIL loader or generic trojan rather than agreeing on one specific family. The executable is unsigned and protected with Smart Assembly.
Threat Behavior
The runtime record shows registry policy changes targeting Windows Defender real-time protection. This concretely supports the T1562.001 defence-evasion mapping and is substantially stronger evidence than a behavioural label alone. PowerShell also ran during execution. A T1055 mapping appeared, but no injected target process was recorded, so it is not treated as observed process injection. The combined sandbox verdict was clean, and none of the inspected contacted hosts matched the malicious or suspicious cache; these are meaningful counter-signals but do not negate the protection-tampering artefact.
What To Do Now
Do not run or reinstall this executable. Keep Windows Defender or other security software enabled, let your antivirus remove the file, and if it has already run, restore protection settings and perform a full endpoint scan.
Where this verdict could be wrong3 caveats
- The combined sandbox verdict was clean despite the recorded Windows Defender policy changes.
- No inspected contacted host matched the malicious or suspicious cache.
- The file has been submitted by 177 distinct sources and was first seen on May 21, 2020.
These are the assessment's weak points. If you believe one applies to your file, report the verdict and we'll re-review it.
- The combined sandbox verdict was clean.
- None of the 11 inspected contacted hosts matched the malicious or suspicious cache.
- The file was submitted by 177 distinct sources and was first seen on May 21, 2020.
- No injected target process or persistence indicator was recorded.
- Nine antivirus engines detected the executable, including Fortinet, TrellixENS, and TrendMicro-HouseCall.
- Evidence from the test run recorded policy changes aimed at disabling Windows Defender real-time protection.
- The executable is unsigned.
- Smart Assembly protection can conceal program logic and raises concern alongside the other hostile evidence.
- PowerShell was launched during execution.
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
- 22sandbox rule tags
- 4spawned 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.
Note: Read the user name of the test computer.
Note: Listed the programs running on 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 trojans work
A trojan pretends to be something useful or harmless so that you run it. Once open, it does its real job in the background, from stealing data to opening a back door or downloading more malware.
Bottom line:The disguise is the whole trick, so a trustworthy-looking name or icon means nothing.
Recorded behavior
What happened in the test
Grouped by step. The order is not a timeline.
- 1
Input file
The submitted object
- Evidence 1 of 6: FileSeen in the test run
GHOST SETUP
3322f736503a1e2adf80af1c578809f69d2bc5b4a686bc509413f574ae0dd6d1
Uploaded file
- 2
Processes
What ran
- Evidence 2 of 6: ProcessSeen in the test run
program.exe
"C:\Users\<USER>\AppData\Local\Temp\program.exe"
Test run - Evidence 3 of 6: ProcessSeen in the test run
powershell.exe
"C:\Windows\System32\WindowsPowerShell\v1.0\powershell.exe" sources\setup.exe /compact:on
Test run - +1 more recorded observation
- 2
Files
Created or changed
- Evidence 4 of 6: Written fileSeen in the test run
executable.exe.log
C:\Users\user\AppData\Local\Microsoft\CLR_v4.0\UsageLogs\executable.exe.log
Test run - Evidence 5 of 6: Written fileSeen in the test run
Caches
C:\Users\user\AppData\Local\Microsoft\Windows\Caches
Test run - +1 more recorded observation
- 1
Network
Hosts contacted
- Evidence 6 of 6: Contacted hostSeen in the test run
217.20.54.38
Contacted during the test run.
Test run
6 facts from the test run. See the full activity list.
What this file did when executed
This file was detonated in 6 sandboxes and its runtime behaviour was observed.
Sandbox verdicts
1- VT: CLEANclean
Techniques observed in the sandbox
22MITRE ATT&CK techniques the sandbox mapped. Highlighted ones are rare in normal software; the others are common in legitimate programs too.
- T1010
- T1027· Obfuscated code
- T1033· Reads user info
- T1036
- T1055· Process injection
- T1057· Lists programs
- T1059· Runs commands
- T1064
- T1071· Application protocol
- T1082· System recon
- T1083· Scans your files
- T1106
- T1112
- T1134.001
- T1497· Sandbox evasion
- T1518.001· Checks your AV
- T1539
- T1560
- T1562· Disables security
- T1562.001· Disables security
- T1562.006· Disables security
- T1574.002· Execution hijack
Observed activity
Processes started
4Programs the file ran, with their command lines.
program.exe"C:\Users\<USER>\AppData\Local\Temp\program.exe"powershell.exe"C:\Windows\System32\WindowsPowerShell\v1.0\powershell.exe" sources\setup.exe /compact:on3322f736503a1e2adf80af1c578809f69d2bc5b4a686bc509413f574ae0dd6d1.exe%SAMPLEPATH%\3322f736503a1e2adf80af1c578809f69d2bc5b4a686bc509413f574ae0dd6d1.exepowershell.exeC:\Windows\System32\WindowsPowerShell\v1.0\powershell.exe
Network contacts
11 host, listed as 1 address. Links show the host and path only.
- IP address
217.20.54.38
Files
30Files the file created, changed or deleted.
- Written
C:\Users\user\AppData\Local\Microsoft\CLR_v4.0\UsageLogs\executable.exe.log - Written
C:\Users\user\AppData\Local\Microsoft\Windows\Caches - Written
C:\Users\user\AppData\Local\Temp\__PSScriptPolicyTest_3o0gfcq2.vwe.ps1 - Written
C:\Users\user\AppData\Local\Temp\__PSScriptPolicyTest_jqjkddjj.byr.psm1 - Written
C:\Users\user\AppData\Roaming - Written
\Device\ConDrv\\Connect
Show all 30 entries for files
- Written
C:\Users\user\AppData\Local\Microsoft\Windows\PowerShell\StartupProfileData-NonInteractive - Written
C:\Users\user\AppData\Local\Temp\__PSScriptPolicyTest_j2k30sox.w22.ps1 - Written
C:\Users\user\AppData\Local\Temp\__PSScriptPolicyTest_mgpabxxl.dlk.ps1 - Written
C:\Users\user\AppData\Local\Temp\__PSScriptPolicyTest_owyslf3u.yzn.psm1 - Written
C:\Users\user\AppData\Local\Temp\__PSScriptPolicyTest_uz5hiru5.adw.psm1 - Written
C:\Users\user\Documents\20210528 - Written
C:\Users\user\Documents\20210528\PowerShell_transcript.899552.+Ra2nmEk.20210528152648.txt - Written
C:\Windows\system32\catroot - Written
C:\Windows\system32\catroot2 - Deleted
%USERPROFILE%\AppData\Local\Temp\__PSScriptPolicyTest_dacxwbqd.kww.ps1 - Deleted
%USERPROFILE%\AppData\Local\Temp\__PSScriptPolicyTest_ok0yfmbf.hmv.psm1 - Deleted
%USERPROFILE%\AppData\Local\Microsoft\CLR_v4.0\UsageLogs\powershell.exe.log - Deleted
C:\ProgramData\Microsoft\Windows\WER\Temp\WERD1A.tmp.WERInternalMetadata.xml - Deleted
C:\ProgramData\Microsoft\Windows\WER\Temp\WERDD6.tmp.csv - Deleted
C:\ProgramData\Microsoft\Windows\WER\Temp\WERE06.tmp.txt - Deleted
C:\ProgramData\Microsoft\Windows\WER\Temp\WER126B.tmp.WERInternalMetadata.xml - Deleted
C:\ProgramData\Microsoft\Windows\WER\Temp\WER126C.tmp.csv - Deleted
C:\ProgramData\Microsoft\Windows\WER\Temp\WER127C.tmp.txt - Deleted
C:\Windows\System32\spp\store\2.0\cache\cache.dat - Deleted
%USERPROFILE%\AppData\Local\Temp\__PSScriptPolicyTest_m5f1tq5r.pu5.ps1 - Deleted
%USERPROFILE%\AppData\Local\Temp\__PSScriptPolicyTest_lhoabflt.0ch.psm1 - Deleted
C:\ProgramData\Microsoft\Windows\WER\Temp\WER342A.tmp.WERInternalMetadata.xml - Deleted
C:\ProgramData\Microsoft\Windows\WER\Temp\WER342B.tmp.WERInternalMetadata.xml - Deleted
C:\ProgramData\Microsoft\Windows\WER\Temp\WER35B1.tmp.csv
Registry and auto-start
30Settings the file changed, including ways to start again after a restart.
- Set
HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Group Policy Objects\{4526E47C-BF8F-42B2-9C65-B0234CD04523}Machine\Software\Policies\Microsoft\Windows Defender\Real-Time Protection - Set
HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Group Policy Objects\{4526E47C-BF8F-42B2-9C65-B0234CD04523}Machine\Software\Policies\Microsoft\Windows Defender\Real-Time Protection\DisableRealtimeMonitoring - Set
HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Group Policy Objects\{E2EB9E9D-E3BE-4E71-9677-50ABA297A4F2}Machine\Software\Policies\Microsoft\Windows Defender\Real-Time Protection - Set
HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Group Policy Objects\{E2EB9E9D-E3BE-4E71-9677-50ABA297A4F2}Machine\Software\Policies\Microsoft\Windows Defender\Real-Time Protection\DisableRealtimeMonitoring - Set
HKLM\Software\Microsoft\WBEM\WDM\%windir%\system32\drivers\ndis.sys[MofResourceName] - Set
HKLM\Software\Microsoft\WBEM\WDM\%windir%\System32\Drivers\portcls.SYS[PortclsMof]
Show all 30 entries for registry and auto-start
- Set
HKLM\Software\Microsoft\WBEM\WDM\%windir%\system32\drivers\en-US\ACPI.sys.mui[ACPIMOFResource] - Set
HKLM\Software\Microsoft\WBEM\WDM\%windir%\system32\DRIVERS\HDAudBus.sys[HDAudioMofName] - Set
HKLM\Software\Microsoft\WBEM\WDM\%windir%\System32\Drivers\en-US\portcls.SYS.mui[PortclsMof] - Set
HKLM\Software\Microsoft\WBEM\WDM\%windir%\system32\advapi32.dll[MofResourceName] - Set
HKLM\Software\Microsoft\WBEM\WDM\%windir%\system32\en-US\advapi32.dll.mui[MofResourceName] - Set
HKLM\Software\Microsoft\WBEM\WDM\%windir%\system32\drivers\en-US\mssmbios.sys.mui[MofResource] - Set
HKLM\Software\Microsoft\WBEM\WDM\%windir%\system32\DRIVERS\en-US\HDAudBus.sys.mui[HDAudioMofName] - Set
HKLM\Software\Microsoft\WBEM\WDM\%windir%\system32\drivers\en-US\ndis.sys.mui[MofResourceName] - Set
HKLM\Software\Microsoft\WBEM\WDM\%windir%\system32\DRIVERS\en-US\intelppm.sys.mui[PROCESSORWMI] - Deleted
HKLM\SYSTEM\ControlSet001\Services\WmiApRpl\Performance\First Counter - Deleted
HKLM\SYSTEM\ControlSet001\Services\WmiApRpl\Performance\Last Counter - Deleted
HKLM\SYSTEM\ControlSet001\Services\WmiApRpl\Performance\First Help - Deleted
HKLM\SYSTEM\ControlSet001\Services\WmiApRpl\Performance\Last Help - Deleted
HKLM\SYSTEM\ControlSet001\Services\WmiApRpl\Performance\Object List - Deleted
HKCU\Software\Microsoft\Windows\CurrentVersion\Group Policy Objects\{E62CBEE7-DDE8-490A-92BE-1F914260F453}User - Deleted
HKCU\Software\Microsoft\Windows\CurrentVersion\Group Policy Objects - Deleted
HKCU\Software\Microsoft\Windows\CurrentVersion\Group Policy Objects\{E62CBEE7-DDE8-490A-92BE-1F914260F453}Machine - Deleted
HKCU\Software\Microsoft\Windows\CurrentVersion\Group Policy Objects\{E62CBEE7-DDE8-490A-92BE-1F914260F453}Machine\Software - Deleted
HKCU\Software\Microsoft\Windows\CurrentVersion\Group Policy Objects\{E62CBEE7-DDE8-490A-92BE-1F914260F453}Machine\Software\Policies - Deleted
HKCU\Software\Microsoft\Windows\CurrentVersion\Group Policy Objects\{E62CBEE7-DDE8-490A-92BE-1F914260F453}Machine\Software\Policies\Microsoft - Deleted
HKCU\Software\Microsoft\Windows\CurrentVersion\Group Policy Objects\{E62CBEE7-DDE8-490A-92BE-1F914260F453}Machine\Software\Policies\Microsoft\Windows - Deleted
HKCU\Software\Microsoft\Windows\CurrentVersion\Group Policy Objects\{E62CBEE7-DDE8-490A-92BE-1F914260F453}Machine\Software\Policies\Microsoft\Windows\PowerShell - Deleted
HKCU\Software\Microsoft\Windows\CurrentVersion\Group Policy Objects\{E62CBEE7-DDE8-490A-92BE-1F914260F453}Machine\Software\Policies\Microsoft\Windows\PowerShell\ModuleLogging - Deleted
HKCU\Software\Microsoft\Windows\CurrentVersion\Group Policy Objects\{E62CBEE7-DDE8-490A-92BE-1F914260F453}Machine\Software\Policies\Microsoft\Windows\PowerShell\ModuleLogging\ModuleNames
Mutexes
5Named locks a program uses so only one copy runs; malware families often reuse them.
Local\ZonesCacheCounterMutexLocal\ZonesLockedCacheCounterMutex\Sessions\1\BaseNamedObjects\Global\SyncRootManager\Sessions\1\BaseNamedObjects\Local\ZonesCacheCounterMutex\Sessions\1\BaseNamedObjects\Local\ZonesLockedCacheCounterMutex
Sandbox background — not the file
24The analysis machine's own processes and connections, recorded in every run.
- VM process
services.exeC:\Windows\system32\services.exe - VM process
svchost.exeC:\Windows\system32\svchost.exe -k DcomLaunch -p - VM process
wuapihost.exeC:\Windows\System32\wuapihost.exe - VM injection target
\\?\C:\Windows\system32\wbem\WMIADAP.EXE - VM host
www.microsoft.com - VM host
204.79.197.203
Show all 24 entries for sandbox background — not the file
- VM host
192.168.0.10 - VM host
131.253.33.203 - VM host
a83f:8110:7400:6500:6d00:5300:6800:6f00 - VM host
192.168.0.92 - VM host
a83f:8110:0:0:100:0:1800:0 - VM host
20.99.132.105 - VM host
23.216.147.64 - VM host
a83f:8110:6300:6100:7400:6900:6f00:6e00 - VM host
20.99.133.109 - VM host
23.216.147.76 - VM host
192.168.0.35 - VM host
192.229.211.108 - VM host
20.99.186.246 - VM host
a83f:8110:80df:0:100:0:0:0 - VM host
23.216.81.152 - VM host
a83f:8110:7406:ff15:7c75:0:488b:748 - VM host
192.168.0.6 - VM host
a83f:8110:45:3bfb:f84:1b02:0:4183
Files this sample writes at runtime
This file drops 10 children at runtime. None are currently flagged malicious in our cache. 10 have no saved verdict and were not checked; that is missing coverage, not a finding.
- 72c16badddb6a1cdc403…10394bNot checkedno saved verdict
- 0af31773dff2f7d467dc…8ce22eNot checkedno saved verdict
- 5f432a8b10428c18c6ca…9b5feaNot checkedno saved verdict
- fb80337063af92016cca…7b3463Not checkedno saved verdict
- e6b74d6ee22b346f6ae2…c18080Not checkedno saved verdict
- 1060e5bb4566ffbd5803…16ddeaNot checkedno saved verdict
- b3acfb92770e9b6f0846…ee9ba1Not checkedno saved verdict
- 22e7aecc2be3322a7e2a…254627Not checkedno saved verdict
- 9d2d4abe97f6e693a262…27d8aeNot checkedno saved verdict
- 599884a7b2259db7e4f2…d19944Not checkedno saved verdict
Chapter 04
Technical details
9 of the 69 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.
Engines that flagged it 9
- Fortinet (major engine)Adware/ExtGPi
- TrellixENS (major engine)Artemis!E9D76E0B38FD
- TrendMicro-HouseCall (major engine)Trojan.MSIL.LOADER.TL0101EK26YV
- GoogleDetected
- huorongTrojan/MSIL.Loader.j
- KingsoftMsil.Troj.loader.j
- Paloaltogeneric.ml
- RisingTrojan.Loader!8.15A8 (CLOUD)
File fingerprint
- Last analyzed
- Nov 1, 2026, 4:27 AM UTC
- SHA-256
3322f736503a1e2adf80af1c578809f69d2bc5b4a686bc509413f574ae0dd6d1- SHA-1
0df2dda3c81b3757622f4c329a6e628c86538024- MD5
e9d76e0b38fd3ffccfef64ffc9ed7935
About this file
GHOST SETUP says it is GHOST SPECTRE (GHOST SETUP), 149.5 kB.
- Claims to be
- GHOST SPECTRE (GHOST SETUP)From the file's own version information, written by whoever built it.
- Original name
- GHOST SETUPMatches the shared file name.
- Type and size
- Win32 EXE · 149.5 kB
- Signer
- UnsignedNo code signature.
- First seen
- May 21, 2020On VirusTotal.
- Submitted by
- 177 distinct sources
- Packer
- Smart Assembly (DetectItEasy protector)Packing hides code; legitimate installers use it too.
- Entropy
- 5.15 of 8
First scanned
Antivirus consensus
9 of 69 engines flagged this file
5 of the 74 engines returned no result for this file (file type not supported, or the scan did not finish), so they did not check it.
- Tier-117 engines3flagged
- Tier-235 engines3flagged
- Low-trust17 engines3flagged
View all 74 engine results
- FortinetMalicious: Adware/ExtGPi
- GoogleMalicious: Detected
- huorongMalicious: Trojan/MSIL.Loader.j
- KingsoftMalicious: Msil.Troj.loader.j
- PaloaltoMalicious: generic.ml
- RisingMalicious: Trojan.Loader!8.15A8 (CLOUD)
- TrellixENSMalicious: Artemis!E9D76E0B38FD
- TrendMicro-HouseCallMalicious: Trojan.MSIL.LOADER.TL0101EK26YV
- WebrootMalicious: W32.Malware.Gen
- AcronisClean
- AhnLab-V3Clean
- AlibabaClean
- alibabacloudClean
- ALYacClean
- Antiy-AVLClean
- APEXClean
- ArcabitClean
- AvastClean
- Avast-MobileNo result
- AVGClean
- AviraClean
- BitDefenderClean
- BitDefenderFalxNo result
- BkavClean
- CAT-QuickHealClean
- ClamAVClean
- CMCClean
- CrowdStrikeClean
- CTXClean
- CylanceClean
- CynetClean
- DrWebClean
- ElasticClean
- EmsisoftClean
- ESET-NOD32Clean
- F-SecureClean
- GDataClean
- GridinsoftClean
- IkarusNo result
- JiangminClean
- K7AntiVirusClean
- K7GWClean
- KasperskyClean
- LionicClean
- MalwarebytesClean
- MaxSecureClean
- McAfeeDClean
- MicrosoftClean
- MicroWorld-eScanClean
- NANO-AntivirusClean
- PandaClean
- SangforClean
- SentinelOneClean
- SkyhighClean
- SophosClean
- SUPERAntiSpywareClean
- SymantecClean
- SymantecMobileInsightNo result
- TACHYONClean
- tehtrisClean
- TencentClean
- TrapmineClean
- TrendMicroClean
- TrustlookNo result
- VaristClean
- VBA32Clean
- VIPREClean
- VirITClean
- ViRobotClean
- XcitiumClean
- YandexClean
- ZillyaClean
- ZoneAlarmClean
- ZonerClean
Signatures and behavior heuristics
A community signature or high-severity behavioral heuristic matched. Signatures identify known patterns; heuristics are strong leads but are not proof on their own.
Sample disabled Windows Defender real-time protection or added an AV exclusion path. This is the blow-the-doors-off move malware makes right before dropping a second-stage payload.
EvidenceHKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Group Policy Objects\{4526E47C-BF8F-42B2-9C65-B0234CD04523}Machine\Software\Policies\Microsoft\Windows Defender\Real-Time ProtectionVirusTotal's sandbox summary maps this run to MITRE T1055 (Process Injection), but no injected process of the sample's own was recorded (the analysis VM's own WMI adapter, crash handlers and Chrome updater are not counted). VirusTotal maps T1055 on about half of all files no engine flags, so the mapping alone is not evidence of injection.
EvidenceT1055 (sandbox MITRE mapping)PE is packed (high-entropy code or known packer) AND unsigned AND at least one engine flagged it. Packing alone is common in legit software; packing + unsigned + signal is the malware-dropper pattern.
Evidencepackers: Smart Assembly (DetectItEasy protector)The sample contacted an external IP address directly and no application domain was recorded. Direct-IP traffic also occurs in legitimate installers and infrastructure, so this is supporting context only and requires corroboration from host reputation and other runtime evidence.
Evidence217.20.54.38Unsigned, packed PE with sandbox-observed network activity. The packing step hides the payload until execution; the network call fetches / reports for the next stage. Classic dropper / stager behaviour.
Evidence217.20.54.38
Section entropy & packers
A known packer signature (UPX / Themida / VMProtect / etc.) matched this file. Packers aren't malicious on their own, but most malware uses them.
Packers compress or encrypt the executable and only unpack it at runtime. Legitimate commercial software uses them too — but if the file is also unsigned and rare, it's a strong malware signal.
These identify the compiler, runtime or installer used to build the file. They are not packing and are not a risk signal on their own.
How widely this file has been seen
Widely seen in the wild for a long time. High prior this is legitimate; isolated detections on common-old files are usually false positives.
Chapter 05
Questions & answers
Short answers to the 8 questions people ask most about this file.
Is GHOST SETUP a virus?
What is GHOST SETUP?
How many antivirus engines detected GHOST SETUP?
What should I do if I already installed GHOST SETUP?
How do I remove GHOST SETUP?
What kind of malware is GHOST SETUP?
What is the SHA-256 hash of GHOST SETUP?
How up to date is this analysis of GHOST SETUP?
Community
Member reviews and reports for this exact file hash.