File scan report
Verdict Safe
Is cardfight.
This validly signed Windows installer was flagged by none of the 60 antivirus engines that checked it, and its sandbox run showed ordinary installer activity with no high-risk…
Read the whole reasonShow less
Strong evidence · A verified publisher signature, and no engine flags it.
This installer appears safe to use if you obtained it from the developer's official source. Keep your security software enabled during installation.
Good practice2 tips
We found nothing harmful in this file.
Install it only if it came from the developer's own website or an official app store.
Keep your antivirus and Windows updates switched on.
No scanner can promise a file is 100% safe.
Reads the latest antivirus results for this file's hash. Nothing is uploaded.
Antivirus results
0 of 60 flagged
- Flagged 0
- No detection 60
- No result 14
- Code signing Adam Kruchkow
- Test run Completed
- First seen 3mo ago
Chapter 02
Why we think so
3 points against it and 4 in its favour, checked against the scan evidence.
The reasoning behind this verdict
It carries a valid signature from an individual developer with no prior history in our data. The sandbox run recorded only normal installer activity. It has been seen by 25 submitters over about three months.
No engine, including 17 major antivirus engines that returned results, detected anything in this Windows Installer package. The file carries a valid code signature from an individual developer. That developer has no reputation history in our data, so the signature confirms the file's integrity but not the author's track record. The sandbox runs recorded msiexec installing the package, with no injection targets, no persistence and no malicious verdict. One direct IP contact was recorded, but its reputation was not checked and on its own it is weak evidence. The engine results come from the first scan, so confidence is moderate rather than high.
What We Detected
None of the 60 antivirus engines that checked it flagged this Windows Installer package, and 17 major antivirus engines returned clean results. The package has a valid code signature from an individual developer who has no reputation history in our data. No public malware database or rule hits were recorded.
Threat Behavior
The sandbox runs show the standard Windows Installer service running the package. No processes were injected, no persistence was created and no high-risk techniques were recorded. One external IP address was contacted; no host reputation result is available for it.
What To Do Now
The evidence points to a clean installer. Download it only from the game's official source. Keep your antivirus enabled while you install it, and rescan it if you received it from an unofficial site.
Where this verdict could be wrong3 caveats
- The engine results date from the file's first scan 88 days ago and have not been refreshed, so later detections would not be reflected here.
- The signer is an individual with no track record in our data, and signed installers for small games are sometimes used as lures. Nothing in this file's evidence shows that, but the signature does not vouch for the author's reputation.
- Host reputation for the one external address the installer contacted was not checked.
These are the assessment's weak points. If you believe one applies to your file, report the verdict and we'll re-review it.
- None of the 60 antivirus engines that checked it flagged the file.
- The installer carries a valid, intact code signature.
- The sandbox run showed only normal installer activity, with no injection, persistence or malicious verdict.
- Seen by 25 independent submitters over roughly three months with no detections.
- The signer is an individual developer with no reputation history in our data.
- The antivirus results come from the file's first scan and have not been refreshed since.
- One direct IP contact was recorded without a completed host reputation check.
6 sources checked · 5 complete · 1 partial. 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- 7sandbox rule tags
- 2spawned processes
- 1network contact
- 9filesystem & mutex artifacts
What this file did when executed
This file was run in a sandbox and its runtime behaviour was observed.
Techniques observed in the sandbox
7MITRE ATT&CK techniques the sandbox mapped. Highlighted ones are rare in normal software; the others are common in legitimate programs too.
- T1033· Reads user info
- T1055· Process injection
- T1082· System recon
- T1091· USB spreading
- T1112
- T1120
- T1562.001· Disables security
Observed activity
Processes started
2Programs the file ran, with their command lines.
msiexec.exe"C:\Windows\system32\msiexec.exe" /I "C:\Users\<USER>\Desktop\build_139_windows.msi" /qb ACCEPTEULA=1 LicenseAccepted=1msiexec.exe"C:\Windows\System32\msiexec.exe" /i "C:\Users\user\Desktop\build_139_windows.msi"
Network contacts
11 host, listed as 1 address. Links show the host and path only.
- IP address
23.9.176.229
Files
7Files the file created, changed or deleted.
- Written
C:\Windows\ServiceProfiles\LocalService\AppData\Local\FontCache\Fonts\Download-1.tmp - Written
C:\Windows\System32\Tasks\Microsoft\Windows\Application Experience\Microsoft Compatibility Appraiser - Written
C:\MSIb6c00.tmp - Written
C:\ProgramData - Written
C:\ProgramData\Microsoft\Windows\Templates - Written
C:\Windows\Fonts
Show all 7 entries for files
- Deleted
C:\MSIb6c00.tmp
Mutexes
2Named locks a program uses so only one copy runs; malware families often reuse them.
Global\_MSIExecute\BaseNamedObjects\Local\SM0:7044:304:WilStaging_02
Sandbox background — not the file
11The 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 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 - VM process
svchost.exeC:\Windows\system32\svchost.exe -k LocalService -s W32Time
Show all 11 entries for sandbox background — not the file
- VM process
msiexec.exeC:\Windows\System32\msiexec.exe C:\Windows\system32\msiexec.exe /V - VM host
162.159.36.2 - VM host
8.8.8.8 - VM host
199.232.210.172 - VM host
204.79.197.203
Chapter 04
Technical details
None of the 60 antivirus engines that checked it flag it; signed by Adam Kruchkow.
Sources checked
Every check behind this verdict
6 sources checked · 5 complete · 1 partial. Complete means the check returned a usable result; it does not mean the file is safe.
File fingerprint
- Last analyzed
- Sep 2, 2026, 1:25 AM UTC
- SHA-256
195416c43f4386d50e974af65e5010d1d8f7425b2b5567471b99fbbf3bdf6352- SHA-1
cf88266f8b14a3d70984ba91e83dae87e9c13e76- MD5
e39538695e92dccf540ec1bdc9984a97
About this file
cardfight.msi is a Windows Installer file of 53.0 MB.
- Type and size
- Windows Installer · 53.0 MB
- Signer
- Adam KruchkowValid code signature.
- First seen
- Jul 23, 2026On VirusTotal.
- Submitted by
- 25 distinct sources
First scanned Updated
Verdict history
- Suspicious
- Safeafter a re-check of the saved evidence
Ratings change when antivirus engines, our checks or MalwareTips staff learn more about a file.
Antivirus consensus
0 of 60 engines flagged this file
14 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 engines0flagged
- Tier-232 engines0flagged
- Low-trust11 engines0flagged
View all 74 engine results
- AcronisClean
- AhnLab-V3Clean
- AlibabaNo result
- alibabacloudClean
- ALYacClean
- Antiy-AVLClean
- APEXNo result
- ArcabitClean
- AvastClean
- Avast-MobileNo result
- AVGClean
- AviraClean
- BitDefenderClean
- BitDefenderFalxNo result
- BkavClean
- CAT-QuickHealClean
- ClamAVClean
- CMCClean
- CrowdStrikeClean
- CTXClean
- CylanceNo result
- CynetClean
- DrWebClean
- ElasticNo result
- EmsisoftClean
- ESET-NOD32Clean
- F-SecureClean
- FortinetClean
- GDataClean
- GoogleClean
- GridinsoftClean
- huorongClean
- IkarusNo result
- JiangminClean
- K7AntiVirusClean
- K7GWClean
- KasperskyClean
- KingsoftClean
- LionicClean
- MalwarebytesClean
- MaxSecureClean
- McAfeeDClean
- MicrosoftClean
- MicroWorld-eScanClean
- NANO-AntivirusClean
- PaloaltoNo result
- PandaClean
- RisingClean
- SangforClean
- SentinelOneNo result
- SkyhighClean
- SophosClean
- SUPERAntiSpywareClean
- SymantecClean
- SymantecMobileInsightNo result
- TACHYONClean
- tehtrisNo result
- TencentClean
- TrapmineClean
- TrellixENSClean
- TrendMicroClean
- TrendMicro-HouseCallClean
- TrustlookNo result
- VaristClean
- VBA32No result
- VIPREClean
- VirITClean
- ViRobotClean
- WebrootNo result
- 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)
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 7 questions people ask most about this file.
Is cardfight.msi safe?
What is cardfight.msi?
How many antivirus engines detected cardfight.msi?
Is cardfight.msi digitally signed?
What is the SHA-256 hash of cardfight.msi?
Is it safe to install cardfight.msi?
How up to date is this analysis of cardfight.msi?
Community
Member reviews and reports for this exact file hash.