File scan report
Verdict Suspicious
Is Capri- Setup. exe safe? Treat it as suspicious.
15 of the 71 antivirus engines that checked it flag this unsigned .NET installer with generic MSIL trojan labels, yet four sandbox runs stayed clean with no persistence, dropped files or hostile network traffic.
Why Suspicious? 15 antivirus engines flag it; nothing else confirms it.
Limited evidence · One sign points to a problem; nothing else confirms it.
Do not run this installer unless you obtained it directly from the publisher you expect and can verify the download. If you have already run it, keep your security protection fully enabled, run a full system scan and review newly installed programs and startup entries.
What to do now5 steps
Some signs point to a problem, but nothing confirms it is harmful. Treat it with caution.
What to do
Don't install 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.
It is only 1 day old. If you're unsure, scan it again in a few days; antivirus engines often catch up on new files.
If you already installed 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.
Antivirus results
15 of 71 flagged
- Flagged 15
- No detection 56
- No result 4
- Code signing Unsigned
- Test run Completed
- First seen 1d ago
Chapter 02
Why we think so
5 points against it and 5 in its favour, checked against the scan evidence.
The reasoning behind this verdict
This installer is unsigned, first seen on Nov 9, 2026, and a dozen engines describe it as a generic .NET trojan, with the engine family behind BitDefender, Kaspersky and Microsoft among them. Against that, four sandbox runs produced no malicious verdict, no persistence, no dropped files and no contact with a known-bad host. The evidence points both ways, so it deserves caution rather than trust.
Fifteen of the 71 antivirus engines that checked it flag this 22 MB .NET installer, but the labels are generic: repeated variants of a "MSIL trojan" name, Microsoft's machine-learning Sabsik detection, a file-reputation hit and a low-confidence machine-learning score. After collapsing engines that license the same scan engine, eight independent votes remain, including four from high-quality engines, which is too many to dismiss as noise. The file is unsigned, first seen on Nov 9, 2026, submitted by only seven sources, and the antivirus analysis describes it as obfuscated .NET code with debugger-detection behaviour, so its internals are deliberately hidden. Balanced against that, the combined sandbox verdict was clean: nothing was written beyond a user profile folder, no persistence was set up, and no process injection target or hostile domain was recorded. The one mapped injection technique came without any target process, and the single network contact was the analysis machine's own background traffic. Earlier verdicts on files sharing the same build fingerprint are mixed, and because that fingerprint is shared across .NET installers it neither condemns nor clears this sample.
What We Detected
The file is a 22 MB .NET executable presented as an installer for a program called "Capri". It carries no digital signature, so nothing confirms who built or published it. Fifteen of the 71 antivirus engines that checked it flag it, and after accounting for engines that share the same underlying scan technology there are eight genuinely separate detections, four of them from well-regarded engines. The names used are generic — an obfuscated .NET trojan label repeated by several brands, Kaspersky's rule-based trojan name, Microsoft's machine-learning Sabsik family and a file-reputation hit from Avast and AVG.
The file is also new and thinly distributed: it was first seen on Nov 9, 2026 and only seven distinct sources have submitted it, which is exactly the profile that reputation-based detections react to. The engine analysis notes obfuscated .NET code and debugger-detection behaviour, and the code section is almost entirely high-entropy, so a large part of what the program does is obscured.
Threat Behavior
Four sandbox runs were completed and none of them ended in a malicious verdict. The program ran with install-style switches and wrote only to its own folder inside the user profile. No files were dropped, no startup entries, registry changes or program markers were created, and no process injection target was recorded. The behaviour mapping that mentions process injection came without any process actually being targeted, which is common for installers and packed .NET software and is not evidence of injection on its own.
The only domain contact recorded during the runs was the analysis machine's own data traffic, not the sample's. A reputation check on that single host found nothing malicious. No public malware-sample database lists this hash, no malware-specific community rules match it, and there are no entries in the known-good software reference set either.
What To Do Now
Because the detections and the observations from the test run disagree, treat the installer as untrusted until its origin is confirmed. Only run it if you obtained it directly from the vendor you expect and you can verify the download; do not install it from a link that arrived in a message, an advertisement or a third-party download portal.
If you have already run it, run a full scan with your existing security software kept fully enabled, review installed programs and startup items for anything you do not recognise, and check for new browser extensions or changed account settings. If the installer came from an unexpected source, deleting it costs nothing.
Where this verdict could be wrong3 caveats
- Several of the flags are machine-learning or file-reputation labels rather than named malware families, and those labels frequently fire on newly released, obfuscated installers that turn out to be harmless.
- Four sandbox runs produced no malicious verdict at all: no persistence, no dropped files, no process injection target and no hostile network contact, which is the opposite of what a working trojan usually shows.
- Past verdicts on files sharing this build fingerprint are mixed (two unfavourable, two borderline, one clean), so they reflect the .NET installer framework rather than this particular publisher.
These are the assessment's weak points. If you believe one applies to your file, report the verdict and we'll re-review it.
- Four sandbox runs completed without a malicious verdict and showed no persistence, no dropped files and no injected process.
- The only network contact recorded was the analysis machine's own background traffic; no known-malicious host appeared.
- The hash is not listed in public malware-sample databases and no malware-specific community detection rules match it.
- The antivirus analysis found no packer, and the behaviour seen during execution is consistent with a routine installer.
- The hostile engine labels are generic or reputation based rather than tied to a specific malware family.
- The installer is unsigned, so nothing identifies who compiled or published it.
- Fifteen of the 71 antivirus engines that checked it flag it, including four well-regarded engines using generic .NET trojan names.
- It is new and rarely seen: first seen on Nov 9, 2026, with only seven distinct sources submitting it.
- Its code is heavily obfuscated .NET with debugger-detection behaviour, which hides what it actually does.
- No trusted-software reference lists this exact file, so there is no independent confirmation that it is a legitimate product.
6 sources checked · all complete. See every source
Chapter 03
What it did in our test
It ran in 4 isolated tests; no test environment rated what it did as risky.
Test run summary
Capture complete- 4isolated sandbox runs
- 18sandbox rule tags
- 4spawned processes
- 0network contacts
- 1filesystem & 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: Unpacked hidden content while it ran.
Moderate concern: Checked whether it was running on a test computer.
Note: Listed the programs running on the test computer.
Note: Read basic details of the test computer, such as its Windows version.
Note: Looked through folders on the test computer (most installers do this).
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 setting up auto-start; no auto-start entry was recorded.
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 4: FileSeen in the test run
Capri-Setup.exe
dce48f406ab86b05e10ba381b913261f911be4e2d0716cc6d0fa2512b41734d8
Uploaded file
- 2
Processes
What ran
- Evidence 2 of 4: ProcessSeen in the test run
Capri-Setup.exe
"C:\Users\<USER>\Desktop\Capri-Setup.exe"
Test run - Evidence 3 of 4: ProcessSeen in the test run
Capri-Setup.exe
"C:\Users\user\Desktop\Capri-Setup.exe" -install
Test run - +1 more recorded observation
- 1
Files
Created or changed
- Evidence 4 of 4: Written fileSeen in the test run
Roaming
C:\Users\user\AppData\Roaming
Test run
4 facts from the test run. See the full activity list.
What this file did when executed
This file was detonated in 4 sandboxes and its runtime behaviour was observed.
Sandbox verdicts
1- VT: CLEANclean
Techniques observed in the sandbox
18MITRE 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
- T1036
- T1055· Process injection
- T1057· Lists programs
- T1082· System recon
- T1083· Scans your files
- T1112
- T1140· Deobfuscation
- T1222
- T1496
- T1497· Sandbox evasion
- T1497.001· Sandbox evasion
- T1518· Checks your AV
- T1547.009· Auto-start
- T1553
- T1553.002
Observed activity
Processes started
4Programs the file ran, with their command lines.
Capri-Setup.exe"C:\Users\<USER>\Desktop\Capri-Setup.exe"Capri-Setup.exe"C:\Users\user\Desktop\Capri-Setup.exe" -installCapri-Setup.exe"C:\Users\user\Desktop\Capri-Setup.exe" /installCapri-Setup.exe"C:\Users\user\Desktop\Capri-Setup.exe" /load
Files
1Files the file created, changed or deleted.
- Written
C:\Users\user\AppData\Roaming
Sandbox background — not the file
1The analysis machine's own processes and connections, recorded in every run.
- VM host
atm.teams.mira.tm.svc.cloud.microsoft
Chapter 04
Technical details
15 of the 71 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 15
- Avast (major engine)FileRepMalware [Misc]
- AVG (major engine)FileRepMalware [Misc]
- BitDefender (major engine)IL:Trojan.MSILZilla.270071
- Emsisoft (major engine)IL:Trojan.MSILZilla.270071 (B)
- GData (major engine)IL:Trojan.MSILZilla.270071
- Kaspersky (major engine)HEUR:Trojan.MSIL.Startun.gen
- Microsoft (major engine)Trojan:Win32/Sabsik.EN.A!ml
- ALYacIL:Trojan.MSILZilla.270071
File fingerprint
- Last analyzed
- Nov 10, 2026, 1:14 AM UTC
- SHA-256
dce48f406ab86b05e10ba381b913261f911be4e2d0716cc6d0fa2512b41734d8- SHA-1
728e0e4deaabe5c7d1ce58827a29c51505937dd2- MD5
9bd585de67cf65b15197852a19be8f26
About this file
Capri-Setup.exe says it is Capri, 22.5 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 · 22.5 MB
- Signer
- UnsignedNo code signature.
- First seen
- Nov 9, 2026On VirusTotal.
- Submitted by
- 7 distinct sourcesRarely seen: few people have submitted this exact file.
- Packer
- None detected
- Entropy
- 7.51 of 8
First scanned
Antivirus consensus
15 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 15 detections come from 8 independent scan engines: several vendors license the same engine, so their results are one vote.
- Tier-118 engines4flagged7 vendors sharing 4 engines
- Tier-236 engines2flagged5 vendors sharing 2 engines
- Low-trust17 engines3flagged
View all 75 engine results
- ALYacMalicious: IL:Trojan.MSILZilla.270071
- APEXMalicious: Malicious
- ArcabitMalicious: IL:Trojan.MSILZilla.D41EF7
- AvastMalicious: FileRepMalware [Misc]
- AVGMalicious: FileRepMalware [Misc]
- BitDefenderMalicious: IL:Trojan.MSILZilla.270071
- CTXMalicious: exe.trojan.msilzilla
- EmsisoftMalicious: IL:Trojan.MSILZilla.270071 (B)
- GDataMalicious: IL:Trojan.MSILZilla.270071
- KasperskyMalicious: HEUR:Trojan.MSIL.Startun.gen
- McAfeeDMalicious: ti!DCE48F406AB8
- MicrosoftMalicious: Trojan:Win32/Sabsik.EN.A!ml
- MicroWorld-eScanMalicious: IL:Trojan.MSILZilla.270071
- TrapmineMalicious: suspicious.low.ml.score
- VIPREMalicious: IL:Trojan.MSILZilla.270071
- AcronisClean
- AhnLab-V3Clean
- AlibabaClean
- alibabacloudClean
- Antiy-AVLClean
- Avast-MobileNo result
- AviraClean
- BitDefenderFalxNo result
- BkavClean
- CAT-QuickHealClean
- ClamAVClean
- CMCClean
- CrowdStrikeClean
- CylanceClean
- CynetClean
- DeepInstinctClean
- DrWebClean
- ElasticClean
- ESET-NOD32Clean
- F-SecureClean
- FortinetClean
- GoogleClean
- GridinsoftClean
- huorongClean
- IkarusClean
- JiangminClean
- K7AntiVirusClean
- K7GWClean
- KingsoftClean
- LionicClean
- MalwarebytesClean
- MaxSecureClean
- NANO-AntivirusClean
- PaloaltoClean
- PandaClean
- RisingClean
- SangforClean
- SentinelOneClean
- SkyhighClean
- SophosClean
- SUPERAntiSpywareClean
- SymantecClean
- SymantecMobileInsightNo result
- TACHYONClean
- tehtrisClean
- TencentClean
- TrellixENSClean
- TrendMicroClean
- TrendMicro-HouseCallClean
- TrustlookNo result
- VaristClean
- VBA32Clean
- VirITClean
- ViRobotClean
- WebrootClean
- XcitiumClean
- YandexClean
- ZillyaClean
- 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)
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
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 Capri-Setup.exe safe, or is it malware?
What is Capri-Setup.exe?
How many antivirus engines detected Capri-Setup.exe?
What should I do if I already installed 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.