File scan report
Verdict Suspicious
Is artcraft- launcher- 0. 4. 1- windows- x64. msi safe? Treat it as suspicious.
No antivirus engine detected a threat, but an unexplained mapping and repeated unusual behavior among same-signer installers warrant caution.
Read the whole reasonShow less
Why Suspicious? Data from the test run mapped possible process injection, but did not identify the target process or exact method.
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 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.
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.
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 15
- Code signing Learning Machines Inc
- Test run Completed
- First seen 12d 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
None of the 60 antivirus engines that checked it flagged this signed MSI, and its only sandbox run returned clean. However, the test run mapped possible process injection, while four related installers from the same little-established signer previously showed similarly unusual behavior, so the package should be verified before installation.
The antivirus result is reassuring: none of the 60 antivirus engines that checked it flagged the file, and no malware family was identified. The MSI is authentically signed by Learning Machines Inc, but only four samples are available for that publisher, so the certificate does not yet establish a reliable clean history. The test run mapped T1055, which can indicate process injection, although it recorded neither an injected target nor the exact method. The only sandbox verdict was clean, and no malicious child or malware-specific research rule corroborates the mapping. Four same-signer installers previously received cautionary assessments for comparable unusual behavior, making this recurring signal worth treating carefully despite the substantial false-positive possibility.
What We Detected
None of the 60 antivirus engines that checked it flagged the MSI, including the reporting major antivirus engines. No named malware family, malicious file it created, brand mismatch, or malware-specific research-rule match was found. The package has a verified signature from Learning Machines Inc, but the publisher history covers only four samples and is not yet established.
Threat Behavior
The completed sandbox run returned clean, but its data mapped activity to MITRE T1055, associated with process injection. No target process appears in the injected-process record, so this mapping supports only possible injection and does not prove a malicious method or intent. Four related installers signed by the same publisher previously received cautionary assessments for unusual behavior in the test run. No complete contacted-host reputation result is available, although this run recorded no sample network contacts to cross-check.
What To Do Now
Verify that the installer came directly from the publisher's official release channel and confirm its signature before running it. If its origin cannot be established, postpone installation or test it in an isolated environment while keeping security software enabled.
Where this verdict could be wrong3 caveats
- None of the 60 antivirus engines that checked it flagged the installer, including the reporting major antivirus engines.
- The only completed sandbox run returned clean, and no injected target process was recorded.
- The installer carries a verified signature, although the publisher has only four historical samples and no established clean track record.
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 installer.
- The package has a valid digital signature from Learning Machines Inc.
- The sole completed sandbox run returned clean and recorded no injected target process.
- No malicious dropped files, brand conflict, or malware-specific research-rule matches were found.
- Data from the test run mapped possible process injection, but did not identify the target process or exact method.
- The signing publisher has only four historical samples, which is too little to establish a dependable clean track record.
- Four related installers carrying the same publisher signature previously showed similarly unusual evidence from the test run.
- The file was first observed on Oct 13, 2026, limiting long-term reputation evidence.
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- 7sandbox rule tags
- 2spawned processes
- 0network contacts
- 5filesystem & mutex artifacts
What the test run showed
What the file did on a test computer
Confirmed in the test run
Note: Read the user name of the test computer.
Note: Read basic details of the test computer, such as its Windows version.
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 spreading through USB drives; nothing confirms it.
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
artcraft-launcher-0.4.1-windows-x64.msi
8d6c55481c9c065c41789c10ebf3a80dc329c11f47c38725c418b41732555f03
Uploaded file
- 2
Processes
What ran
- Evidence 2 of 5: ProcessSeen in the test run
msiexec.exe
"C:\Windows\system32\msiexec.exe" /I "C:\Users\<USER>\Desktop\artcraft-launcher-0.4.1-windows-x64.msi" /qb ACCEPTEULA=1 LicenseAccepted=1
Test run - Evidence 3 of 5: ProcessSeen in the test run
msiexec.exe
"C:\Windows\System32\msiexec.exe" /i "C:\Users\user\Desktop\artcraft-launcher-0.4.1-windows-x64.msi"
Test run - +1 more recorded observation
- 2
Files
Created or changed
- Evidence 4 of 5: Written fileSeen in the test run
MSI3a583.tmp
C:\MSI3a583.tmp
Test run - Evidence 5 of 5: Written fileSeen in the test run
Fonts
C:\Windows\Fonts
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
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
- T1574· Execution hijack
Observed activity
Processes started
2Programs the file ran, with their command lines.
msiexec.exe"C:\Windows\system32\msiexec.exe" /I "C:\Users\<USER>\Desktop\artcraft-launcher-0.4.1-windows-x64.msi" /qb ACCEPTEULA=1 LicenseAccepted=1msiexec.exe"C:\Windows\System32\msiexec.exe" /i "C:\Users\user\Desktop\artcraft-launcher-0.4.1-windows-x64.msi"
Files
3Files the file created, changed or deleted.
- Written
C:\MSI3a583.tmp - Written
C:\Windows\Fonts - Deleted
C:\MSI3a583.tmp
Registry and auto-start
2Settings the file changed, including ways to start again after a restart.
- Set
F40042E2E5F7E8EF8189FED15519AECE42C3BFA2\Blob - Set
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\SystemCertificates\AuthRoot\Certificates\F40042E2E5F7E8EF8189FED15519AECE42C3BFA2\Blob
Mutexes
2Named locks a program uses so only one copy runs; malware families often reuse them.
Global\_MSIExecute\BaseNamedObjects\Local\SM0:5296:304:WilStaging_02
Sandbox background — not the file
6The 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 LocalService -s W32Time - VM process
lsass.exeC:\Windows\system32\lsass.exe - VM process
msiexec.exeC:\Windows\System32\msiexec.exe C:\Windows\system32\msiexec.exe /V
Chapter 04
Technical details
None of the 60 antivirus engines that checked it flag it; signed by Learning Machines Inc.
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.
File fingerprint
- Last analyzed
- Oct 15, 2026, 9:34 AM UTC
- SHA-256
8d6c55481c9c065c41789c10ebf3a80dc329c11f47c38725c418b41732555f03- SHA-1
27bf805aca53f3f10ed3af47a328327f2f5d377c- MD5
2be94f4f6d2df95709258a407cc15639
About this file
artcraft-launcher-0.4.1-windows-x64.msi is a Windows Installer file of 9.2 MB.
- Type and size
- Windows Installer · 9.2 MB
- Signer
- Learning Machines IncValid code signature.
- First seen
- Oct 13, 2026On VirusTotal.
- Submitted by
- 36 distinct sources
First scanned
Antivirus consensus
0 of 60 engines flagged this file
15 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.
- Tier-117 engines0flagged
- Tier-231 engines0flagged
- Low-trust12 engines0flagged
View all 75 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
- DeepInstinctNo result
- DrWebClean
- ElasticNo result
- EmsisoftClean
- ESET-NOD32No result
- F-SecureClean
- FortinetClean
- GDataClean
- GoogleNo result
- GridinsoftClean
- huorongClean
- IkarusClean
- JiangminClean
- K7AntiVirusClean
- K7GWClean
- KasperskyClean
- KingsoftClean
- LionicClean
- MalwarebytesClean
- MaxSecureClean
- McAfeeDClean
- MicrosoftClean
- MicroWorld-eScanClean
- NANO-AntivirusClean
- PaloaltoNo result
- PandaClean
- RisingClean
- SangforClean
- SentinelOneClean
- SkyhighClean
- SophosClean
- SUPERAntiSpywareClean
- SymantecClean
- SymantecMobileInsightNo result
- TACHYONClean
- tehtrisNo result
- TencentClean
- TrapmineClean
- TrellixENSClean
- TrendMicroClean
- TrendMicro-HouseCallClean
- TrustlookNo result
- VaristNo result
- VBA32Clean
- 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 artcraft-launcher-0.4.1-windows-x64.msi safe, or is it malware?
What is artcraft-launcher-0.4.1-windows-x64.msi?
How many antivirus engines detected artcraft-launcher-0.4.1-windows-x64.msi?
I already downloaded and installed artcraft-launcher-0.4.1-windows-x64.msi — what should I do?
Is artcraft-launcher-0.4.1-windows-x64.msi digitally signed?
What is the SHA-256 hash of artcraft-launcher-0.4.1-windows-x64.msi?
How up to date is this analysis of artcraft-launcher-0.4.1-windows-x64.msi?
Community
Member reviews and reports for this exact file hash.