File scan report
Verdict Suspicious
Is siege_
Three generic detections and PowerShell activity warrant caution, but no major antivirus engines, named family, malicious runtime result, or corroborating intelligence…
Read the whole reasonShow less
Why Suspicious? 3 antivirus engines flag it, but no major engine agrees; nothing else confirms it.
Limited evidence · One sign points to a problem; nothing else confirms it.
If it came from a link, an attachment or a stranger, delete it.
What to do now4 steps
Some signs point to a problem, but nothing confirms it is harmful. Treat it with caution.
What to do
Don't open or extract it unless you're sure where it came from.
Check where you got it: an unexpected attachment, a link someone sent you or a re-upload is a red flag.
If you can't confirm where it came from, delete it. If you need the program, download it again from the publisher's own website.
If you already opened or extracted it
Stop using it, run a full scan with your antivirus and watch for unexpected behavior or security alerts.
Not sure what to do?
Ask the MalwareTips community before you run it. If you already ran it, follow the cleanup guide.
- Ask for free help on the MalwareTips forumWindows malware removal help, answered by volunteers. (opens malwaretips.com in a new tab)
- Remove malware from WindowsStep-by-step cleanup with free tools. (opens malwaretips.com in a new tab)
Paste this report's link in your topic so helpers can see what was found.
Reads the latest antivirus results for this file's hash. Nothing is uploaded.
Antivirus results
3 of 47 flagged
- Flagged 3
- No detection 44
- No result 27
- Code signing Not applicable
- Test run Completed
- First seen 2mo ago
Chapter 02
Why we think so
4 points against it and 4 in its favour, checked against the scan evidence.
The reasoning behind this verdict
Three of the 47 antivirus engines that checked it flagged this ZIP, but none was major and no recognized malware family was identified. The sandbox observed PowerShell scripts yet found no named injection target, persistence, sample-attributed network traffic, or malicious runtime result, leaving the evidence inconclusive.
Three of the 47 antivirus engines that checked it flagged the archive, with one mid-tier static alert and two less reliable generic labels. No major antivirus engines detected it, and the labels do not identify a recognized malware family. The sandbox observed PowerShell scripts using an execution-policy bypass, but the paths reference source-maintenance scripts for Zydis and no persistence or named injection target was recorded. With no corroborating intelligence, publisher identity, exact release match, or comparable prior verdicts, the available evidence does not support a definitive conclusion.
What We Detected
Three of the 47 antivirus engines that checked it flagged the ZIP. SentinelOne produced a static suspicious-archive alert, while Bkav and MaxSecure used generic malware labels; no major antivirus engines identified a threat and no recognized family was named.
Threat Behavior
The sandbox unpacked the archive and ran several PowerShell scripts with an execution-policy bypass from a Source/Zydis directory. Although mappings for T1055 and T1562.001 appeared, no injected process, persistence mechanism, or sample-attributed network contact was recorded, so those mappings do not prove the corresponding actions occurred. The only recorded IP contact was identified as analysis-environment background traffic.
What To Do Now
Do not run the archive on a production or personal system until its origin and contents are independently verified. Keep security software enabled, inspect the included scripts and executables in an isolated environment, and obtain a fresh scan if a trusted publisher or authoritative release source becomes available.
Where this verdict could be wrong3 caveats
- Three independent engines flagged the archive, including SentinelOne, so the detections cannot be dismissed as exclusively less reliable noise.
- The archive launched PowerShell with an execution-policy bypass and carries anti-analysis-related tags, which can occur in development tooling but also warrants caution.
- No complete reputation check is available for all observed host data, although the only recorded IP was identified as analysis-environment background traffic.
These are the assessment's weak points. If you believe one applies to your file, report the verdict and we'll re-review it.
- No major antivirus engines flagged the archive.
- The sandbox produced no malicious runtime result and recorded no persistence mechanism or named process-injection target.
- The only recorded IP contact was attributed to analysis-environment background activity.
- No inspected child was identified as malicious.
- Three independent antivirus engines flagged the archive, including a static suspicious-archive alert from SentinelOne.
- The archive invoked PowerShell scripts with an execution-policy bypass.
- The file carries long-sleep and debugging-environment-detection tags, which can indicate anti-analysis behavior but are not conclusive alone.
- No complete contacted-host reputation result or external-intelligence coverage is available.
6 sources checked · 5 complete · 1 not needed or not applicable. See every source
Chapter 03
What it did in our test
It ran in our isolated test environment; no test environment rated what it did as risky.
Test run summary
Capture complete- 14sandbox rule tags
- 6spawned processes
- 0network contacts
- 23filesystem & mutex artifacts
What the test run showed
What the file did on a test computer
Confirmed in the test run
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: Read basic details of the test computer, such as its Windows version.
Note: Loaded extra code modules while running.
Note: Checked which security software was installed on the test computer.
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 contacting a server, but no contacted host was recorded.
Not confirmed: A sandbox rule tagged this run as weakening security settings; no setting change 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.
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 5: FileSeen in the test run
siege_[unknowncheats.me]_.zip
03deeea734734edefd363e2fc79c2f000103df7e79c729d46d70ea5f92e68f14
Uploaded file
- 2
Processes
What ran
- Evidence 2 of 5: ProcessSeen in the test run
powershell.exe
"C:\Windows\sysnative\WindowsPowerShell\v1.0\powershell.exe" -NoProfile -ExecutionPolicy bypass -File "C:\Users\<USER>\AppData\Local\Temp\siege/Source/Zydis/fix_include.ps1"
Test run - Evidence 3 of 5: ProcessSeen in the test run
powershell.exe
"C:\Windows\sysnative\WindowsPowerShell\v1.0\powershell.exe" -NoProfile -ExecutionPolicy bypass -File "C:\Users\<USER>\AppData\Local\Temp\siege/Source/Zydis/fix_include2.ps1"
Test run - +1 more recorded observation
- 2
Files
Created or changed
- Evidence 4 of 5: Written fileSeen in the test run
Windows PowerShell.lnk
C:\Users\<USER>\Desktop\%AppData%\Microsoft\Windows\Start Menu\Programs\Windows PowerShell\Windows PowerShell.lnk
Test run - Evidence 5 of 5: Written fileSeen in the test run
7MBESGH40HYMX9B30M8R.temp
C:\Users\<USER>\AppData\Roaming\Microsoft\Windows\Recent\CustomDestinations\7MBESGH40HYMX9B30M8R.temp
Test run - +1 more recorded observation
5 facts from the test run. See the full activity list.
What this file did when executed
This file was run in a sandbox and its runtime behaviour was observed.
Sandbox verdicts
1- VT: CLEANclean
Techniques observed in the sandbox
14MITRE ATT&CK techniques the sandbox mapped. Highlighted ones are rare in normal software; the others are common in legitimate programs too.
- T1027· Obfuscated code
- T1033· Reads user info
- T1055· Process injection
- T1059· Runs commands
- T1071· Application protocol
- T1082· System recon
- T1129· Loads modules
- T1485
- T1497· Sandbox evasion
- T1518· Checks your AV
- T1562· Disables security
- T1562.001· Disables security
- T1573
- T1574· Execution hijack
Observed activity
Processes started
6Programs the file ran, with their command lines.
powershell.exe"C:\Windows\sysnative\WindowsPowerShell\v1.0\powershell.exe" -NoProfile -ExecutionPolicy bypass -File "C:\Users\<USER>\AppData\Local\Temp\siege/Source/Zydis/fix_include.ps1"powershell.exe"C:\Windows\sysnative\WindowsPowerShell\v1.0\powershell.exe" -NoProfile -ExecutionPolicy bypass -File "C:\Users\<USER>\AppData\Local\Temp\siege/Source/Zydis/fix_include2.ps1"powershell.exe"C:\Windows\sysnative\WindowsPowerShell\v1.0\powershell.exe" -NoProfile -ExecutionPolicy bypass -File "C:\Users\<USER>\AppData\Local\Temp\siege/Source/Zydis/fix_vcxproj.ps1"powershell.exe"C:\Windows\sysnative\WindowsPowerShell\v1.0\powershell.exe" -NoProfile -ExecutionPolicy bypass -File "C:\Users\<USER>\AppData\Local\Temp\siege/Source/Zydis/fix_wpo.ps1"powershell.exe"C:\Windows\sysnative\WindowsPowerShell\v1.0\powershell.exe" -NoProfile -ExecutionPolicy bypass -File "C:\Users\<USER>\AppData\Local\Temp\siege/Source/Zydis/fix_zydis.ps1"unarchiver.exeC:\Windows\SysWOW64\unarchiver.exe "C:\Windows\SysWow64\unarchiver.exe" "C:\Users\user\Desktop\siege_[unknowncheats.me]_.zip"
Files
23Files the file created, changed or deleted.
- Written
C:\Users\<USER>\Desktop\%AppData%\Microsoft\Windows\Start Menu\Programs\Windows PowerShell\Windows PowerShell.lnk - Written
C:\Users\<USER>\AppData\Roaming\Microsoft\Windows\Recent\CustomDestinations\7MBESGH40HYMX9B30M8R.temp - Written
C:\Users\<USER>\AppData\Roaming\Microsoft\Windows\Recent\CustomDestinations\590aee7bdd69b59b.customDestinations-ms - Written
C:\Users\<USER>\AppData\Roaming\Microsoft\Windows\Recent\CustomDestinations\590aee7bdd69b59b.customDestinations-ms~RFeb5a.TMP - Written
C:\Users\<USER>\AppData\Local\Microsoft\Windows\PowerShell\StartupProfileData-NonInteractive - Written
C:\Users\<USER>\AppData\Local\Microsoft\CLR_v4.0\UsageLogs\powershell.exe.log
Show all 23 entries for files
- Written
C:\Users\<USER>\AppData\Roaming\Microsoft\Windows\Recent\CustomDestinations\61RY4JBRUY7DBNA890NV.temp - Written
C:\Users\<USER>\AppData\Roaming\Microsoft\Windows\Recent\CustomDestinations\590aee7bdd69b59b.customDestinations-ms~RFeb69.TMP - Written
C:\Users\<USER>\AppData\Roaming\Microsoft\Windows\Recent\CustomDestinations\QZR1VJ79L58Q03RD5U5I.temp - Written
C:\Users\<USER>\AppData\Roaming\Microsoft\Windows\Recent\CustomDestinations\590aee7bdd69b59b.customDestinations-ms~RFf5ba.TMP - Written
D:\R6Autoupdatingsource\Dominate.vcxproj - Written
C:\Users\<USER>\AppData\Roaming\Microsoft\Windows\Recent\CustomDestinations\F0ZK2JV1GJ84640PLJ21.temp - Written
C:\Users\<USER>\AppData\Roaming\Microsoft\Windows\Recent\CustomDestinations\590aee7bdd69b59b.customDestinations-ms~RF1079c.TMP - Written
C:\Users\<USER>\AppData\Roaming\Microsoft\Windows\Recent\CustomDestinations\ZAWNSNRSUKA6ZCL5P23Z.temp - Written
C:\Users\<USER>\AppData\Roaming\Microsoft\Windows\Recent\CustomDestinations\590aee7bdd69b59b.customDestinations-ms~RF10f2d.TMP - Deleted
C:\Users\<USER>\AppData\Roaming\Microsoft\Windows\Recent\CustomDestinations\590aee7bdd69b59b.customDestinations-ms~RFeb5a.TMP - Deleted
C:\Users\<USER>\AppData\Roaming\Microsoft\Windows\Recent\CustomDestinations\590aee7bdd69b59b.customDestinations-ms~RFeb69.TMP - Deleted
C:\Users\<USER>\AppData\Roaming\Microsoft\Windows\Recent\CustomDestinations\61RY4JBRUY7DBNA890NV.temp - Deleted
C:\Users\<USER>\AppData\Roaming\Microsoft\Windows\Recent\CustomDestinations\590aee7bdd69b59b.customDestinations-ms~RFf5ba.TMP - Deleted
C:\Users\<USER>\AppData\Local\Packages\Microsoft.XboxGamingOverlay_8wekyb3d8bbwe\LocalCache\KnownGameList.bin - Deleted
C:\Users\<USER>\AppData\Local\Microsoft\GameDVR\KnownGameList.update - Deleted
C:\Users\<USER>\AppData\Roaming\Microsoft\Windows\Recent\CustomDestinations\590aee7bdd69b59b.customDestinations-ms~RF1079c.TMP - Deleted
C:\Users\<USER>\AppData\Roaming\Microsoft\Windows\Recent\CustomDestinations\590aee7bdd69b59b.customDestinations-ms~RF10f2d.TMP
Registry and auto-start
3Settings the file changed, including ways to start again after a restart.
- Set
HKEY_CURRENT_USER\SOFTWARE\Microsoft\Windows\CurrentVersion\Explorer\SessionInfo\1\ApplicationViewManagement\W32:000000000019018C\VirtualDesktop - Set
HKEY_CURRENT_USER\SOFTWARE\Microsoft\Windows\CurrentVersion\Search\JumplistData\{1AC14E77-02E7-4E5D-B744-2EB1AE5198B7}\WindowsPowerShell\v1.0\powershell.exe - Set
HKEY_CURRENT_USER\SOFTWARE\Microsoft\Windows\CurrentVersion\Explorer\SessionInfo\1\ApplicationViewManagement\W32:0000000000010200\VirtualDesktop
Sandbox background — not the file
10The analysis machine's own processes and connections, recorded in every run.
- VM process
Explorer.EXEC:\Windows\Explorer.EXE - VM process
services.exeC:\Windows\system32\services.exe - VM process
svchost.exeC:\Windows\System32\svchost.exe -k NetworkService -p - VM process
svchost.exeC:\Windows\system32\svchost.exe -k UnistackSvcGroup - VM process
svchost.exeC:\Windows\System32\svchost.exe -k LocalSystemNetworkRestricted -p -s StorSvc - VM process
lsass.exeC:\Windows\system32\lsass.exe
Show all 10 entries for sandbox background — not the file
- VM process
svchost.exeC:\Windows\System32\svchost.exe -k LocalSystemNetworkRestricted -p -s WdiSystemHost - VM process
svchost.exeC:\Windows\system32\svchost.exe -k LocalService -s W32Time - VM process
svchost.exeC:\Windows\system32\svchost.exe -k LocalSystemNetworkRestricted -p - VM host
162.159.36.2
Files this sample writes at runtime
This file drops 9 children at runtime. None are currently flagged malicious in our cache. 9 have no saved verdict and were not checked; that is missing coverage, not a finding.
- 2097cd6d82588a036e89…4b4c2fNot checkedno saved verdict
- 1481ee71bb4289fb7f6b…77bb45Not checkedno saved verdict
- f69a488609742d8d1697…65ffa2Not checkedno saved verdict
- d7281023f0272ba24758…1810f4Not checkedno saved verdict
- 2827328e13030965b463…209c11Not checkedno saved verdict
- 5261fae9eeeec3641e5f…c276f8Not checkedno saved verdict
- 9f99c08d78af93328031…96b0abNot checkedno saved verdict
- cffaacd2c547b0c49d12…bc9442Not checkedno saved verdict
- aeecad2012c761991470…b0e21bNot checkedno saved verdict
Chapter 04
Technical details
3 of the 47 antivirus engines that checked it flag it.
Sources checked
Every check behind this verdict
6 sources checked · 5 complete · 1 not needed or not applicable. Complete means the check returned a usable result; it does not mean the file is safe.
Engines that flagged it 3
- BkavW32.Malware.AF890EA3
- MaxSecureTrojan.Malware.8328611.susgen
- SentinelOneStatic AI - Suspicious Archive
File fingerprint
- Last analyzed
- Oct 16, 2026, 7:37 AM UTC
- SHA-256
03deeea734734edefd363e2fc79c2f000103df7e79c729d46d70ea5f92e68f14- SHA-1
be8f6a72f50e13dd86cbbc868244325f06111871- MD5
ec80188f90efe27942bb285178e4eeab
About this file
siege_[unknowncheats.me]_.zip is a ZIP file of 4.7 MB.
- Type and size
- ZIP · 4.7 MB
- Signer
- Not applicable
- First seen
- Aug 21, 2026On VirusTotal.
- Submitted by
- 34 distinct sources
First scanned Updated
Antivirus consensus
3 of 47 engines flagged this file
27 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-110 engines0flagged
- Tier-226 engines1flagged
- Low-trust11 engines2flagged
View all 74 engine results
- BkavMalicious: W32.Malware.AF890EA3
- MaxSecureMalicious: Trojan.Malware.8328611.susgen
- SentinelOneMalicious: Static AI - Suspicious Archive
- AcronisClean
- AhnLab-V3No result
- AlibabaClean
- alibabacloudClean
- ALYacNo result
- Antiy-AVLClean
- APEXNo result
- ArcabitClean
- AvastNo result
- Avast-MobileClean
- AVGNo result
- AviraClean
- BitDefenderNo result
- BitDefenderFalxNo result
- CAT-QuickHealNo result
- ClamAVClean
- CMCClean
- CrowdStrikeClean
- CTXClean
- CylanceNo result
- CynetClean
- DeepInstinctNo result
- DrWebNo result
- ElasticClean
- EmsisoftClean
- ESET-NOD32No result
- F-SecureClean
- FortinetClean
- GDataClean
- GoogleNo result
- GridinsoftClean
- huorongClean
- IkarusClean
- JiangminClean
- K7AntiVirusClean
- K7GWClean
- KasperskyNo result
- KingsoftClean
- LionicClean
- MalwarebytesClean
- McAfeeDClean
- MicrosoftClean
- MicroWorld-eScanClean
- NANO-AntivirusClean
- PaloaltoNo result
- PandaNo result
- RisingClean
- SangforNo result
- SkyhighNo result
- SophosClean
- SUPERAntiSpywareClean
- SymantecClean
- SymantecMobileInsightNo result
- TACHYONClean
- tehtrisNo result
- TencentClean
- TrellixENSNo result
- TrendMicroNo result
- TrendMicro-HouseCallClean
- TrustlookClean
- VaristNo result
- VBA32No result
- VIPREClean
- VirITClean
- ViRobotClean
- WebrootClean
- XcitiumNo result
- YandexNo result
- ZillyaNo result
- ZoneAlarmClean
- ZonerClean
Signatures and behavior heuristics
Low-severity pattern matches — worth noting but not on their own cause for alarm.
VirusTotal'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)
How widely this file has been seen
Moderate prevalence — neither rare nor common. No strong prior applies.
Chapter 05
Questions & answers
Short answers to the 6 questions people ask most about this file.
Is siege_[unknowncheats.me]_.zip safe, or is it malware?
What is siege_[unknowncheats.me]_.zip?
How many antivirus engines detected siege_[unknowncheats.me]_.zip?
What should I do if I already opened or extracted siege_[unknowncheats.me]_.zip?
What is the SHA-256 hash of siege_[unknowncheats.me]_.zip?
How up to date is this analysis of siege_[unknowncheats.me]_.zip?
Community
Member reviews and reports for this exact file hash.