Is cardfight.msi safe?
Signed MSI installer shows sandbox process-injection and LSASS activity with zero AV detections.
Zero of 74 engines flagged the file, yet sandbox evidence shows process injection (T1055) and LSASS access (T1562.001). The signer has no prior history and contacted-host reputation data is missing.
195416c43f4386d50e…99fbbf3bdf6352Recommended next actions
Before installing
Do not install it until the source and publisher can be verified independently.
If you already installed it
Stop using it, scan the device, and watch for unexpected behavior or security alerts. Download a fresh installer from the developer's official site or an official app store.
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.
Zero of 74 engines flagged the file, yet sandbox evidence shows process injection (T1055) and LSASS access (T1562.001). The signer has no prior history and contacted-host reputation data is missing.
The complete absence of engine detections across 74 scanners is a strong clean signal, but the sandbox recorded two offensive MITRE techniques that legitimate installers rarely exhibit. The signer certificate is verified yet unknown to our history, and the contacted-hosts check was never completed. These conflicting signals place the file in mixed-signals territory rather than a definitive safe or malicious classification.
What We Detected
74 engines scanned the MSI; none returned a malicious or suspicious result. The file is signed by Adam Kruchkow and the signature verified. Sandbox execution recorded process-injection activity (T1055) and LSASS memory access (T1562.001), plus direct-IP connections to four external addresses.
Threat Behavior
The observed techniques are consistent with credential-dumping or defense-evasion tooling, yet no AV engine classified the sample as malware. No dropped malicious children or known-bad contacted hosts were recorded, but the host-reputation check itself was not performed.
What To Do Now
Run the installer only in an isolated test environment. Keep endpoint protection enabled. If the software is required, request the publisher to provide additional provenance or a code-signing history before trusting it on production systems.
Where this verdict could be wrong2 caveats
- signerStats.found=false and trustedPublisher.matched=false — no established publisher history.
- contactedHosts=null — host-reputation cross-check not completed.
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/74 engines flagged the file
- Signature verified
- Medium prevalence (25 submitters)
- Sandbox observed T1055 process injection
- Sandbox observed LSASS access (T1562.001)
- Signer has no prior sample history
- Contacted-host reputation check incomplete
Treat as untrusted until the publisher supplies verifiable history or the file receives broader clean consensus; do not run on production systems without additional validation.
Coverage & freshness
Complete means the check returned a usable result. It does not mean the file is safe.
Antivirus
Complete0 of 74 engines flagged the file.
Sandbox
Complete1 isolated runtime environment contributed observations.
Network
Partial5 runtime contacts were observed without a completed reputation cross-check.
YARA
Complete3 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
- 7MITRE ATT&CK techniques
- 9spawned processes
- 5network contacts
- 9filesystem & mutex artifacts
What this file does
Observed actions and their security significance
High concern: Injected code into another process, a technique that can conceal execution.
High concern: Used removable-media replication behaviour that can spread files between devices.
High concern: Attempted to impair or bypass security controls.
Note: Reads your Windows user-account details.
Note: Collects details about your system.
Note: Connected to 5 servers during sandbox analysis.
These are observed capabilities from an isolated analysis. A technique does not prove malicious intent on its own, and the file never ran on your device.
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
cardfight.msi
195416c43f4386d50e974af65e5010d1d8f7425b2b5567471b99fbbf3bdf6352
01Uploaded file
Processes
Runtime execution
- ProcessObserved
Observed process
"C:\Windows\system32\msiexec.exe" /I "C:\Users\<USER>\Desktop\build_139_windows.msi" /qb ACCEPTEULA=1 LicenseAccepted=1
02Isolated runtime analysis - ProcessObserved
Observed process
C:\Windows\system32\services.exe
03Isolated runtime analysis - +1 more recorded observation in Analyst mode
Files
Created or changed
- Written fileObserved
Download-1.tmp
C:\Windows\ServiceProfiles\LocalService\AppData\Local\FontCache\Fonts\Download-1.tmp
04Isolated runtime analysis - Written fileObserved
Microsoft Compatibility Appraiser
C:\Windows\System32\Tasks\Microsoft\Windows\Application Experience\Microsoft Compatibility Appraiser
05Isolated runtime analysis - +1 more recorded observation in Analyst mode
Network
Hosts contacted
- Contacted hostObserved
162.159.36.2
Contact observed during runtime.
06Isolated runtime analysis - Contacted hostObserved
8.8.8.8
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.
- 162.159.36.2
- 8.8.8.8
- 199.232.210.172
- 204.79.197.203
- 23.9.176.229
- C:\Windows\ServiceProfiles\LocalService\AppData\Local\FontCache\Fonts\Download-1.tmp
- C:\Windows\System32\Tasks\Microsoft\Windows\Application Experience\Microsoft Compatibility Appraiser
- C:\MSIb6c00.tmp
- C:\ProgramData
- C:\ProgramData\Microsoft\Windows\Templates
- C:\MSIb6c00.tmp
- Global\_MSIExecute
- \BaseNamedObjects\Local\SM0:7044:304:WilStaging_02
Detection & Forensics
Consensus, attribution, signatures, code structure, prevalence, and identity.
Evidence integrity
Chain of custody for the facts preserved in this report.
- 3rule hits recorded
- 0 / 74engines flagged
- 25sources in submission history
Why these facts are shown
Each statement identifies whether it was directly recorded or derived from saved scan facts.
- 01
1 high-confidence signature or behavior rule matched this file.
Verdict inputView chapterProvenanceDerivedSourceSignature and behavior rulesObserved at - 02
0 of 74 antivirus engines flagged the file.
ProvenanceObservedSourceAntivirus analysisObserved at - 03
The file has a valid code signature from Adam Kruchkow.
ProvenanceObservedSourceCode-signing metadataObserved at - 04
Scanned file: cardfight.msi — 195416c43f4386d50e974af65e5010d1d8f7425b2b5567471b99fbbf3bdf6352
ProvenanceObservedSourceUploaded fileObserved at - 05
Observed process — "C:\Windows\system32\msiexec.exe" /I "C:\Users\<USER>\Desktop\build_139_windows.msi" /qb ACCEPTEULA=1 LicenseAccepted=1
ProvenanceObservedSourceIsolated runtime analysisObserved at - 06
Observed process — C:\Windows\system32\services.exe
ProvenanceObservedSourceIsolated runtime analysisObserved at - 07
File written: Download-1.tmp — C:\Windows\ServiceProfiles\LocalService\AppData\Local\FontCache\Fonts\Download-1.tmp
ProvenanceObservedSourceIsolated runtime analysisObserved at - 08
File written: Microsoft Compatibility Appraiser — C:\Windows\System32\Tasks\Microsoft\Windows\Application Experience\Microsoft Compatibility Appraiser
ProvenanceObservedSourceIsolated runtime analysisObserved at - 09
Contacted host: 162.159.36.2 — Contact observed during runtime.
ProvenanceObservedSourceIsolated runtime analysisObserved at - 10
Contacted host: 8.8.8.8 — Contact observed during runtime.
ProvenanceObservedSourceIsolated runtime analysisObserved at
Detection sources at a glance
The available sources did not agree on a named threat category.
MalwareBazaar, YARAify, and CIRCL hashlookup completed and returned no entries for 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.
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 NetworkService -pSandbox observed process activity targeting LSASS (Windows credential store). Legitimate software has no business reading LSASS memory — this is Mimikatz-shape behaviour.
EvidenceC:\Windows\system32\lsass.exeThe 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.
Evidence162.159.36.2 · 199.232.210.172 · 204.79.197.203
0 of 74 engines flagged this file
View all 74 engine results
PE structure
Not applicablePE structure analysis applies to Windows executable formats, not this file type.
How widely this file has been seen
Moderate prevalence — neither rare nor common. No strong prior applies.
Fingerprint and provenance
- File name
- cardfight.msi
- Format
- Windows Installer
- Code signing
- Signature valid: Adam Kruchkow
- Size
- 50.5 MB
- Last analyzed
- Sep 2, 2026, 1:25 AM UTC
195416c43f4386d50e974af65e5010d1d8f7425b2b5567471b99fbbf3bdf6352Safety & FAQ
Complete recovery guidance and answers for the next decision.
What to do now
We couldn't fully clear this file. Treat it with caution.
- Recovery step 01
Don't install it unless you're certain it came from a source you trust.
- Recovery step 02
Check where you got it — an unexpected attachment or a random download link is a red flag.
- Recovery step 03
If its origin cannot be confirmed, delete this file and use a fresh copy from a trusted source. Download a fresh installer from the developer's official site or an official app store.
- Recovery step 04
If you're still unsure, scan it again in a day or two — detections often catch up on newer files.
Safety FAQ
Direct answers grounded in the saved verdict and evidence in this report.
Is cardfight.msi safe, or is it malware?
What is cardfight.msi?
How many antivirus engines detected cardfight.msi?
I already downloaded and installed cardfight.msi — what should I do?
How do I remove cardfight.msi?
Is cardfight.msi digitally signed?
What is the SHA-256 hash of cardfight.msi?
How up to date is this analysis of cardfight.msi?
Community
Member reviews and reports for this exact file hash.