File scan report
Verdict Malicious
Is Capri-
Twenty of the 71 antivirus engines that checked it, six of them from the most reliable group, flag this unsigned .NET installer as the Startun trojan, and nine malware-specific community signatures match its code.
Strong evidence · Two or more major antivirus engines agree.
Do not run this installer and delete it. If it has already been executed, disconnect the machine, keep your security software enabled and run a full scan, and review what was installed or started afterwards.
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
20 of 71 flagged
- Flagged 20
- No detection 51
- No result 4
- Code signing Unsigned
- Test run Completed
- First seen 13d ago
Chapter 02
Why we think so
6 points against it and 3 in its favour, checked against the scan evidence.
The reasoning behind this verdict
This unsigned .NET executable describes itself as a setup program, yet 20 of the 71 antivirus engines that checked it flagged it and Kaspersky, Trend Micro and Lionic all name the Startun trojan family. Five sandbox runs returned a combined clean verdict with no injection target recorded, so the runtime picture is thinner than the static one — but the detection consensus is too broad to ignore.
Six independent high-reliability engines and fourteen others flagged this file, which rules out a single vendor's rule-based misfire. The labels are not random either: Kaspersky, Trend Micro, Lionic and Rising each name Startun, a known .NET trojan family, and the file carries the matching behaviour tags for debugger detection and managed code. It is a 10 MB unsigned .NET executable that markets itself as a setup program, submitted by 376 distinct sources since it first appeared on Oct 28, 2026 — popularity among uploaders is not evidence of legitimacy for a binary with no publisher behind it. Nine malware-specific community signatures match, including a pattern for .NET loaders that unpack code from image pixels and one for messaging-bot frameworks, and nothing in the evidence counters that. Weighing the broad static consensus against that unremarkable sandbox result, the file still cannot be treated as anything but a hostile installer.
What We Detected
This is a 10 MB Windows .NET executable named as a setup package, unsigned, with no publisher identity attached. Twenty of the 71 antivirus engines that checked it flagged it. Six of those come from the most reliable group of scanners: Kaspersky calls it HEUR:Trojan.MSIL.Startun.gen, Trend Micro Trojan.MSIL.STARTUN.USBLJT26, Symantec Trojan.Gen.MBT, Sophos Mal/Generic-S, with Ikarus and Microsoft also flagging. Lionic and Rising agree on Startun, so the product family is named consistently by several independent vendors rather than by one over-eager heuristic.
Nine malware-specific community signatures also match the code, including a pattern for .NET loaders that conceal a second assembly inside image pixel data and load it when it ran, plus patterns for messaging-bot frameworks. Broad hunting rules of that kind are noisy, but a match count this high on a file that engines already condemn is a second, independent line of evidence.
Threat Behavior
The file declares itself an installer and the sandbox did see it write into a Google policy directory and a Google temporary folder under Program Files — writes no ordinary third-party setup program needs to make. Five sandbox runs produced a single combined clean verdict, no process of the sample's own was injected, no drop was collected and no remote control domain was observed. That means the behaviour in the test run does not independently confirm the malware labels; the case rests on the breadth and the specificity of the detections above.
The file is not packed and shows no wrapper; it is a plain .NET build, which is normal for the Startun family and means the code is not hiding behind a crypter.
What To Do Now
Do not run this installer, and do not pass it to colleagues. If it has already been executed on a machine, treat that machine as possibly compromised: disconnect it from the network, scan it with up-to-date security software that stays enabled, and check what was recently installed or started. Delete the file rather than keeping it in a downloads folder.
Where this verdict could be wrong3 caveats
- Five sandbox runs produced a single combined clean verdict, no injected process was recorded and no dropped file or malicious host was identified, so the runtime side is weaker than the static side.
- Some of the matched community signatures are broad hunting patterns (embedded AI-service API keys, messaging-bot frameworks) that ordinary software can also match.
- The contacted-host reputation check was not completed, so nothing is known either way about the single network address the sample touched.
These are the assessment's weak points. If you believe one applies to your file, report the verdict and we'll re-review it.
- Five sandbox runs produced a combined clean verdict, with no injected process, no dropped file and no observed remote control domain.
- The executable is a plain .NET build with no packer, wrapper or high-entropy packed code.
- The file has been submitted by many distinct sources, so its identity is well sampled rather than obscure.
- Twenty of the 71 antivirus engines that checked it flagged the file, six of them among the most reliable scanners.
- Kaspersky, Trend Micro, Lionic and Rising all name the Startun trojan family.
- The executable carries no digital signature, so nothing verifies who built or published it.
- Nine malware-specific community signatures matched, including one for .NET loaders that hide a second program inside image data.
- Sandbox runs recorded writes into a Google policy folder and a Google temporary folder under Program Files, which a normal installer has no reason to do.
- It describes itself as a setup package while showing no publisher identity and no verified download source.
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 5 isolated tests; no test environment rated what it did as risky.
Test run summary
Capture complete- 5isolated sandbox runs
- 24sandbox rule tags
- 4spawned processes
- 0network contacts
- 7filesystem & 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: Unpacked hidden content while it ran.
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: Listed the programs running 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 setting up auto-start; no auto-start entry 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.
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 5: FileSeen in the test run
Capri-Setup.exe
3fc2d1f5ef9ff1ad481dde468d7254e28a03be4e4bd2a47973f53b19a4f87235
Uploaded file
- 2
Processes
What ran
- Evidence 2 of 5: ProcessSeen in the test run
file.exe
"C:\Users\<USER>\Desktop\file.exe"
Test run - Evidence 3 of 5: ProcessSeen in the test run
software.exe
"C:\Users\user\Desktop\software.exe" -install
Test run - +1 more recorded observation
- 2
Files
Created or changed
- Evidence 4 of 5: Written fileSeen in the test run
Policies
C:\Program Files\Google\Policies
Test run - Evidence 5 of 5: Written fileSeen in the test run
GUMD00.tmp
C:\Program Files\Google\Temp\GUMD00.tmp
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 detonated in 5 sandboxes and its runtime behaviour was observed.
Sandbox verdicts
1- VT: CLEANclean
Techniques observed in the sandbox
24MITRE ATT&CK techniques the sandbox mapped. Highlighted ones are rare in normal software; the others are common in legitimate programs too.
- T1012
- T1027· Obfuscated code
- T1027.002· Obfuscated code
- T1033· Reads user info
- T1036
- T1055· Process injection
- T1057· Lists programs
- T1059· Runs commands
- T1082· System recon
- T1083· Scans your files
- T1112
- T1129· Loads modules
- T1140· Deobfuscation
- T1496
- T1497· Sandbox evasion
- T1497.001· Sandbox evasion
- T1518· Checks your AV
- T1547.009· Auto-start
- T1553
- T1553.002
- T1562· Disables security
- T1562.001· Disables security
- T1564· Hides artifacts
- T1574· Execution hijack
Observed activity
Processes started
4Programs the file ran, with their command lines.
file.exe"C:\Users\<USER>\Desktop\file.exe"software.exe"C:\Users\user\Desktop\software.exe" -installsoftware.exe"C:\Users\user\Desktop\software.exe" /installsoftware.exe"C:\Users\user\Desktop\software.exe" /load
Files
7Files the file created, changed or deleted.
- Written
C:\Program Files\Google\Policies - Written
C:\Program Files\Google\Temp\GUMD00.tmp - Written
C:\Program Files\Google\Temp\GUME5D0.tmp - Written
C:\Users\user\AppData\Roaming - Deleted
C:\Program Files\Google\Policies - Deleted
C:\Program Files\Google\Temp\GUMD00.tmp
Show all 7 entries for files
- Deleted
C:\Program Files\Google\Temp\GUME5D0.tmp
Sandbox background — not the file
1The analysis machine's own processes and connections, recorded in every run.
- VM host
162.159.36.2
Chapter 04
Technical details
20 of the 71 antivirus engines that checked it flag it; no publisher signature.
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 20
- Ikarus (major engine)Trojan.SuspectCRC
- Kaspersky (major engine)HEUR:Trojan.MSIL.Startun.gen
- Microsoft (major engine)Trojan:Win32/Wacatac.B!ml
- Sophos (major engine)Mal/Generic-S
- Symantec (major engine)Trojan.Gen.MBT
- TrendMicro (major engine)Trojan.MSIL.STARTUN.USBLJT26
- TrendMicro-HouseCall (major engine)Trojan.MSIL.STARTUN.USBLJT26
- alibabacloudTrojan:MSIL/Wacapew.C9nj
File fingerprint
- Last analyzed
- Nov 4, 2026, 9:20 PM UTC
- SHA-256
3fc2d1f5ef9ff1ad481dde468d7254e28a03be4e4bd2a47973f53b19a4f87235- SHA-1
9102c09aace9c6aa587cfed2cff007b4acf2832d- MD5
c00bc7bf2a176fbc86b22a7ba83d9a87
About this file
Capri-Setup.exe says it is Capri, 10.9 MB.
- Claims to be
- CapriFrom the file's own version information, written by whoever built it.
- Original name
- Capri-Setup.exeMatches the shared file name.
- Type and size
- Win32 EXE · 10.9 MB
- Signer
- UnsignedNo code signature.
- First seen
- Oct 28, 2026On VirusTotal.
- Submitted by
- 376 distinct sources
- Packer
- None detected
- Entropy
- 7.84 of 8
First scanned Updated
Verdict history
- Suspicious
- Maliciousafter 1 engine dropped its detection
Ratings change when antivirus engines, our checks or MalwareTips staff learn more about a file.
Antivirus consensus
20 of 71 engines flagged this file
4 of the 75 engines returned no result for this file (file type not supported, or the scan did not finish), so they did not check it.
The 20 detections come from 19 independent scan engines: several vendors license the same engine, so their results are one vote.
- Tier-118 engines6flagged7 vendors sharing 6 engines
- Tier-236 engines5flagged
- Low-trust17 engines8flagged
View all 75 engine results
- alibabacloudMalicious: Trojan:MSIL/Wacapew.C9nj
- APEXMalicious: Malicious
- BkavMalicious: W32.Malware.CAD47958
- CylanceMalicious: Unsafe
- GoogleMalicious: Detected
- GridinsoftMalicious: Trojan.Win32.Wacatac.bot
- IkarusMalicious: Trojan.SuspectCRC
- KasperskyMalicious: HEUR:Trojan.MSIL.Startun.gen
- LionicMalicious: Trojan.Win32.Startun.4!c
- McAfeeDMalicious: ti!3FC2D1F5EF9F
- MicrosoftMalicious: Trojan:Win32/Wacatac.B!ml
- PaloaltoMalicious: generic.ml
- RisingMalicious: Trojan.Startun!8.112B9 (CLOUD)
- SentinelOneMalicious: Static AI - Suspicious PE
- SophosMalicious: Mal/Generic-S
- SymantecMalicious: Trojan.Gen.MBT
- TrapmineMalicious: suspicious.low.ml.score
- TrendMicroMalicious: Trojan.MSIL.STARTUN.USBLJT26
- TrendMicro-HouseCallMalicious: Trojan.MSIL.STARTUN.USBLJT26
- VaristMalicious: W32/ABTrojan.NUWL-4446
- AcronisClean
- AhnLab-V3Clean
- AlibabaClean
- ALYacClean
- Antiy-AVLClean
- ArcabitClean
- AvastClean
- Avast-MobileNo result
- AVGClean
- AviraClean
- BitDefenderClean
- BitDefenderFalxNo result
- CAT-QuickHealClean
- ClamAVClean
- CMCClean
- CrowdStrikeClean
- CTXClean
- CynetClean
- DeepInstinctClean
- DrWebClean
- ElasticClean
- EmsisoftClean
- ESET-NOD32Clean
- F-SecureClean
- FortinetClean
- GDataClean
- huorongClean
- JiangminClean
- K7AntiVirusClean
- K7GWClean
- KingsoftClean
- MalwarebytesClean
- MaxSecureClean
- MicroWorld-eScanClean
- NANO-AntivirusClean
- PandaClean
- SangforClean
- SkyhighClean
- SUPERAntiSpywareClean
- SymantecMobileInsightNo result
- TACHYONClean
- tehtrisClean
- TencentClean
- TrellixENSClean
- TrustlookNo result
- VBA32Clean
- VIPREClean
- VirITClean
- ViRobotClean
- WebrootClean
- 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.
- hunt_multi_llm_embedded_keys
- HUNT_NET_Loader_ImagePixel_To_AssemblyLoad
- LLM_API_Anthropic
- LLM_API_Gemini
- LLM_API_HuggingFace
- LLM_API_OpenAI
- telebot_framework
- WIN_Malware_Unknown_ForgeAuto_37b4704b
- WIN_Malware_XWorm_ForgeAuto_6b06c990_Extrait
- exploit_any_poppopretgeneric
- golang_bin_JCorn_CSC846generic
- NETexecutableMicrosoftgeneric
- pe_imphashgeneric
- Skystars_Malware_Imphashgeneric
- Sus_CMD_Powershell_Usagegeneric
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)
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.
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
Lots of people are uploading this but it's recent — typical of newly-released legitimate software. Low prior for malware.
Chapter 05
Questions & answers
Short answers to the 8 questions people ask most about this file.
Is Capri-Setup.exe a virus?
What is Capri-Setup.exe?
How many antivirus engines detected Capri-Setup.exe?
What should I do if I already installed Capri-Setup.exe?
How do I remove Capri-Setup.exe?
What kind of malware is Capri-Setup.exe?
What is the SHA-256 hash of Capri-Setup.exe?
How up to date is this analysis of Capri-Setup.exe?
Community
Member reviews and reports for this exact file hash.