Is ClassicShellSetup.exe safe?
No antivirus engine detected this long-established, verified-signed installer, although generic YARA matches and several offensive-technique mappings justify normal source verification.
All 75 antivirus engines returned no detection, including 17 tier-1 engines, and the verified-signed file has circulated widely since 2018. Several YARA rules and offensive-technique mappings are concerning, but they are not corroborated by an engine detection, a malicious sandbox verdict, or a known-malicious dropped child.
942c7ee37303c96262…18dd20ddebe5e2Recommended next actions
Before running
Run it only when it came from the developer's official site or another source you independently trust.
If you already ran it
Keep normal device protection enabled and stop if the file behaves unexpectedly.
Intelligence
The saved assessment, checked against the scan evidence and recorded coverage.
The reasoning behind this verdict
This section explains the evidence supporting the verdict and keeps conflicting or missing signals visible.
All 75 antivirus engines returned no detection, including 17 tier-1 engines, and the verified-signed file has circulated widely since 2018. Several YARA rules and offensive-technique mappings are concerning, but they are not corroborated by an engine detection, a malicious sandbox verdict, or a known-malicious dropped child.
The strongest evidence is the complete absence of detections across 75 antivirus engines, including 17 tier-1 engines. The file is verified-signed by Ivaylo Beltchev, has no detected brand mismatch, and has been submitted 5,270 times by 3,310 sources since 2018. One completed sandbox recorded installer execution through msiexec and mapped four offensive techniques, but it produced no malicious sandbox verdict. Seven researcher YARA rules matched, including an Elysium-oriented rule, creating meaningful uncertainty despite the much broader contrary evidence. Host-reputation coverage was incomplete because only one host was inspected despite numerous recorded contacts, so the network activity cannot be described as fully checked. Overall, the long prevalence, signing, and unanimous antivirus results outweigh the uncorroborated behavioral and YARA alerts.
What We Detected
The sample is a Windows installer signed with a verified certificate issued to Ivaylo Beltchev. None of 75 antivirus engines detected it, and all 17 reporting tier-1 engines—including BitDefender, ESET-NOD32, and Kaspersky—returned undetected results. It has also been observed since 2018 across 3,310 sources and 5,270 submissions.
Threat Behavior
One completed sandbox observed MSI installation activity and mapped T1055, T1543.003, T1547.001, and T1562.001. No malicious sandbox verdict was recorded, and no inspected child was identified as malicious, although all ten child verdicts remain individually unknown. Seven YARA rules matched, including “elysium,” but other matches concern certificates, debugging checks, overlays, or obfuscation and may be generic. Only one contacted host received a reputation cross-check despite numerous recorded IP and URL contacts, so no complete network-reputation result is available.
What To Do Now
Confirm that the SHA-256 hash 942c7ee37303c962628555e196eb35f4465bb45d204600dd2518dd20ddebe5e2 came from the intended Classic Shell release channel before running it. Keep endpoint protection enabled and avoid copies obtained from unofficial download mirrors.
Where this verdict could be wrong5 caveats
- YARAify matched 7 rules, including the malware-specific-looking 'elysium' rule; researcher rules can produce false positives, but this remains meaningful contrary evidence.
- The completed sandbox mapped activity to T1055, T1543.003, T1547.001, and T1562.001, techniques that warrant caution despite the absence of a malicious sandbox verdict.
- contactedHosts.inspected=1 does not cover all 15 listed IP contacts and two URLs, so no complete host-reputation result is available.
- All 10 inspected dropped children have unknown individual verdicts; droppedChildren.hasMaliciousChild=false does not establish that each child is benign.
- adversarialInputFlags.commentInjectionSuspected=true, so contaminated community commentary was ignored rather than treated as trustworthy evidence.
These are the assessment's weak points. If you believe one applies to your file, report the verdict and we'll re-review it.
- 0/75 antivirus engines detected the sample.
- All 17 reporting tier-1 engines returned undetected results.
- The signature for 'Ivaylo Beltchev' is verified and brandMismatch=null.
- The file has 5,270 submissions from 3,310 sources dating to 2018.
- behaviour.hasMaliciousSandboxVerdict=false and droppedChildren.hasMaliciousChild=false.
- externalIntel.yaraify.ruleCount=7 includes the 'elysium' rule associated with stealer detection.
- Runtime mappings include T1055, T1543.003, T1547.001, and T1562.001.
- contactedHosts.inspected=1 provides incomplete coverage of the recorded network contacts.
- droppedChildren inspected 10 files, but each child's individual verdict is unknown.
- signing.signerStats.found=false, so no internal signer-history record is available.
Use the file only if its SHA-256 matches a copy obtained from the intended official or otherwise trusted release source. Keep antivirus and endpoint protection enabled during installation.
Coverage & freshness
Complete means the check returned a usable result. It does not mean the file is safe.
Antivirus
Complete0 of 75 engines flagged the file.
Sandbox
Complete1 isolated runtime environment contributed observations.
Network
Partial1 of 21 contacted hosts were cross-checked; coverage is incomplete.
YARA
Complete7 signature or behavior rules matched.
External intel
Complete3 of 3 independent reference sources completed.
Behavior
Plain-English impact first, then the observed runtime evidence.
Runtime flight recorder
Capture complete- 1isolated sandbox run
- 28MITRE ATT&CK techniques
- 15spawned processes
- 22network contacts
- 40filesystem & mutex artifacts
Attack story
Runtime observations grouped by analysis stage. Arrows organize the stages; they do not claim chronology or causality.
Input file
The submitted object
- FileObserved
ClassicShellSetup.exe
942c7ee37303c962628555e196eb35f4465bb45d204600dd2518dd20ddebe5e2
01Uploaded file
Processes
Runtime execution
- ProcessObserved
Observed process
"C:\Users\<USER>\AppData\Local\Temp\ClassicShellSetup.exe"
02Isolated runtime analysis - ProcessObserved
Observed process
msiexec.exe /i "C:\ProgramData\ClassicShellSetup64_4_3_1.msi"
03Isolated runtime analysis - +1 more recorded observation in Analyst mode
Files
Created or changed
- Written fileObserved
ClassicShellSetup64_4_3_1.msi
C:\ProgramData\ClassicShellSetup64_4_3_1.msi
04Isolated runtime analysis - Written fileObserved
MSIdf5f2.tmp
C:\MSIdf5f2.tmp
05Isolated runtime analysis - +1 more recorded observation in Analyst mode
Network
Hosts contacted
- Contacted hostObserved
13.107.4.50
Contact observed during runtime.
06Isolated runtime analysis - Contacted hostObserved
a83f:8110:2800:1800:4000:1800:1800:100
Contact observed during runtime.
07Isolated runtime analysis - +1 more recorded observation in Analyst mode
7 recorded facts from one runtime window. Every fact remains independently traceable in Analyst mode.
What this file did when executed
This file was detonated in 1 sandbox and its runtime behaviour was observed.
Adversary techniques mapped to the MITRE ATT&CK framework.
- 13.107.4.50
- a83f:8110:2800:1800:4000:1800:1800:100
- 131.253.33.203
- 192.168.0.20
- a83f:8110:a0a3:a8a3:b0a3:b8a3:c0a3:c8a3
- a83f:8110:0:0:1400:0:200:3000
- a83f:8110:584a:b5b1:17cb:1ec8:0:0
- a83f:8110:e0:ffff:e0:ffff:e0:ffff
- 192.168.0.74
- a83f:8110:22:3cff:d39:50ff:e39:4cff
- http://ocsp.digicert.com/MFEwTzBNMEswSTAJBgUrDgMCGgUABBT3xL4LQLXDRDM9P665TW442vrsUQQUReuir/SSy4IxLVGLp6chnfNtyA8CEAQJGBtf1btmdVNDtW+VUAg=
- http://ocsp.digicert.com/MFEwTzBNMEswSTAJBgUrDgMCGgUABBSnR4FoxLLkI7vkvsUIFlZt+lGH3gQUWsS5eyoKo6XqcQPAYPkt9mV1DlgCEAO8Mw76cwRWJWQVB4vPpBA=
- C:\ProgramData\ClassicShellSetup64_4_3_1.msi
- C:\MSIdf5f2.tmp
- C:\ProgramData
- C:\ProgramData\Microsoft\Windows\Templates
- C:\Users\user\AppData\Local\Microsoft\Windows\Caches
- C:\ProgramData\Microsoft\Windows\WER\Temp\WER1392.tmp.WERInternalMetadata.xml
- C:\ProgramData\Microsoft\Windows\WER\Temp\WER13A4.tmp.csv
- C:\ProgramData\Microsoft\Windows\WER\Temp\WER13B5.tmp.txt
- C:\Windows\System32\spp\store\2.0\cache\cache.dat
- C:\Windows\ServiceProfiles\LocalService\AppData\Roaming\Microsoft\Crypto\Keys\de7cf8a7901d2ad13e5c67c29e5d1662_cbbb49d6-b7ff-44ca-aba5-8a5e250d4d42
- CTF.LBES.MutexDefaultS-1-5-21-1482476501-1645522239-1417001333-500
- CTF.Compart.MutexDefaultS-1-5-21-1482476501-1645522239-1417001333-500
- CTF.Asm.MutexDefaultS-1-5-21-1482476501-1645522239-1417001333-500
- CTF.Layouts.MutexDefaultS-1-5-21-1482476501-1645522239-1417001333-500
- CTF.TMD.MutexDefaultS-1-5-21-1482476501-1645522239-1417001333-500
Files this sample writes at runtime
This file drops 10 children at runtime. None are currently flagged malicious in our cache.
- 37065dc9fa0b843d5be2…c69c97Never scannednever seen before
- e094d2ed40e5b375b9e1…51fcd5Never scannednever seen before
- fcb396c990b74afc267c…139d28Never scannednever seen before
- 7766768a210dcf8c4ab7…682759Never scannednever seen before
- 347d8e65f200ea8c4eb9…fbffcfNever scannednever seen before
- 79b0a1d7ef25ba27066e…b49217Never scannednever seen before
- 4290bf0069acc5fb40a9…0d8bc7Never scannednever seen before
- 680677a7a060490f5944…ee3189Never scannednever seen before
- eacfe2b4db968adc2ad0…7fdbbbNever scannednever seen before
- 30279aef794d838ccea3…976412Never scannednever seen before
Detection & Forensics
Consensus, attribution, signatures, code structure, prevalence, and identity.
Evidence integrity
Chain of custody for the facts preserved in this report.
- 7rule hits recorded
- 0 / 75engines flagged
- 3,310sources in submission history
Why these facts are shown
Each statement identifies whether it was directly recorded or derived from saved scan facts.
- 01
0 of 75 antivirus engines flagged the file.
Verdict inputView chapterProvenanceObservedSourceAntivirus analysisObserved at - 02
The hash has a long, established submission history across 3,310 sources.
Verdict inputView chapterProvenanceDerivedSourceSubmission historyObserved at - 03
The file has a valid code signature from Ivaylo Beltchev.
ProvenanceObservedSourceCode-signing metadataObserved at - 04
Scanned file: ClassicShellSetup.exe — 942c7ee37303c962628555e196eb35f4465bb45d204600dd2518dd20ddebe5e2
ProvenanceObservedSourceUploaded fileObserved at - 05
Observed process — "C:\Users\<USER>\AppData\Local\Temp\ClassicShellSetup.exe"
ProvenanceObservedSourceIsolated runtime analysisObserved at - 06
Observed process — msiexec.exe /i "C:\ProgramData\ClassicShellSetup64_4_3_1.msi"
ProvenanceObservedSourceIsolated runtime analysisObserved at - 07
File written: ClassicShellSetup64_4_3_1.msi — C:\ProgramData\ClassicShellSetup64_4_3_1.msi
ProvenanceObservedSourceIsolated runtime analysisObserved at - 08
File written: MSIdf5f2.tmp — C:\MSIdf5f2.tmp
ProvenanceObservedSourceIsolated runtime analysisObserved at - 09
Contacted host: 13.107.4.50 — Contact observed during runtime.
ProvenanceObservedSourceIsolated runtime analysisObserved at - 10
Contacted host: a83f:8110:2800:1800:4000:1800:1800:100 — Contact observed during runtime.
ProvenanceObservedSourceIsolated runtime analysisObserved at
Detection sources at a glance
The available sources did not agree on a named threat category.
One or more independent reference databases matched this hash.
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.
- DebuggerCheck__API
- elysium
- golang_bin_JCorn_CSC846
- PE_Digital_Certificate
- Sus_Obf_Enc_Spoof_Hide_PE
The saved runtime evidence maps this activity to MITRE T1055 (Process Injection). The mapping supports possible process injection, but it does not prove the exact injection method or the operator's intent.
EvidenceC:\Windows\system32\svchost.exe -k DcomLaunch -pThe 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.
Evidence13.107.4.50 · a83f:8110:2800:1800:4000:1800:1800:100 · 131.253.33.203
0 of 75 engines flagged this file
View all 75 engine results
Section entropy & packers
No high-entropy executable section or known packer signature was detected. Data and resource sections can still have high entropy without indicating packed code.
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.
Fingerprint and provenance
- File name
- ClassicShellSetup.exe
- Format
- Win32 EXE
- Code signing
- Signature valid: Ivaylo Beltchev
- Size
- 6.9 MB
- Last analyzed
- Sep 12, 2026, 2:19 PM UTC
942c7ee37303c962628555e196eb35f4465bb45d204600dd2518dd20ddebe5e2Safety & 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.
- Recovery step 01
Run it only when it came from the developer's official site or another source you independently trust.
- Recovery step 02
A clean result reduces known risk, but it cannot guarantee that every new or targeted threat has been detected.
- 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.
Is ClassicShellSetup.exe safe?
What is ClassicShellSetup.exe?
How many antivirus engines detected ClassicShellSetup.exe?
Is ClassicShellSetup.exe digitally signed?
What is the SHA-256 hash of ClassicShellSetup.exe?
Is it safe to run ClassicShellSetup.exe?
How up to date is this analysis of ClassicShellSetup.exe?
Community
Member reviews and reports for this exact file hash.