Is printcraft-0.2.1-windows-x64.msi safe?
The signed installer has no antivirus detections, but runtime evidence involving process injection and LSASS warrants caution until its publisher and behavior are independently verified.
None of 75 antivirus engines detected this MSI, and its signature verifies as Learning Machines Inc. However, one runtime record mapped activity to process injection and LSASS access, while the publisher lacks established signer history and network reputation coverage was incomplete.
35408d34f23fbb1224…953f4d46fcc6cfRecommended 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.
None of 75 antivirus engines detected this MSI, and its signature verifies as Learning Machines Inc. However, one runtime record mapped activity to process injection and LSASS access, while the publisher lacks established signer history and network reputation coverage was incomplete.
The installer received no detections from 75 antivirus engines, including 17 tier-1 engines, which weighs strongly against a known malware family. Its Learning Machines Inc signature is valid, but the publisher is not on the curated trusted list and has no historical sample record. One completed runtime analysis did not issue a malicious conclusion, yet it recorded T1055 and activity involving LSASS, both unusual for an ordinary printing installer. The related signer match received a cautious prior assessment under similarly mixed evidence. Because only the contacted domain was reputation-checked while five IP contacts were also observed, the network evidence is incomplete.
What We Detected
The MSI was not flagged by any of 75 antivirus engines, and all 17 reporting tier-1 engines left it undetected. The file carries a verified signature from Learning Machines Inc, but that signer is not on the curated trusted-publisher list and has no established sample history.
Threat Behavior
One completed runtime analysis did not produce a malicious sandbox conclusion, but the saved evidence mapped activity to T1055 process injection and showed activity involving LSASS. It also recorded T1543.003 service-related behavior. Those observations are unusual enough to outweigh an immediate benign interpretation, although the process listing alone may have caused an overly broad behavioral mapping. The single contacted domain was checked without a reputation hit, but five contacted IPs were not covered by that saved host check, so no complete network-reputation conclusion is available.
What To Do Now
Obtain the installer from the publisher's official release channel and verify its SHA-256 and certificate details before running it. Keep endpoint protection enabled, and avoid deploying it broadly until the publisher confirms the hash or further runtime testing explains the LSASS and injection indicators.
Where this verdict could be wrong4 caveats
- The sample had 0/75 antivirus detections, including no tier-1 detections.
- The sole completed sandbox labeled its run clean and behaviour.hasMaliciousSandboxVerdict=false.
- The MSI has a verified 'Learning Machines Inc' signature, although that publisher has no stored signer history.
- No malicious child was identified, and YARAify returned ruleCount=0.
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/75 antivirus engines detected the installer.
- All 17 reporting tier-1 engines left the file undetected.
- The Learning Machines Inc digital signature verifies.
- The completed sandbox did not issue a malicious conclusion.
- No malicious dropped child or YARAify rule match was found.
- Runtime evidence maps activity to T1055 process injection.
- The CredentialDumper heuristic associates observed activity with LSASS.
- T1543.003 service-related activity was recorded.
- The verified signer has no established historical sample record.
- Host-reputation coverage did not include all observed IP contacts.
- A prior file matching the same signer received a cautious assessment.
Verify the hash through Learning Machines Inc's official distribution channel and seek publisher confirmation before installation. Keep endpoint protection enabled and test only in an isolated environment if verification is unavailable.
Coverage & freshness
Complete means the check returned a usable result. It does not mean the file is safe.
Antivirus
Complete0 of 75 engines flagged the file.
Sandbox
Complete1 isolated runtime environment contributed observations.
Network
Partial1 of 6 contacted hosts were cross-checked; coverage is incomplete.
YARA
Complete2 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
- 8MITRE ATT&CK techniques
- 9spawned processes
- 6network contacts
- 13filesystem & 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: Created or modified a system service, which can keep code running.
Note: Reads your Windows user-account details.
Note: Collects details about your system.
Note: Connected to 6 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
printcraft-0.2.1-windows-x64.msi
35408d34f23fbb1224251a95d04a4a7c3472f24faa6609ba8c953f4d46fcc6cf
01Uploaded file
Processes
Runtime execution
- ProcessObserved
Observed process
"C:\Windows\system32\msiexec.exe" /I "C:\Users\<USER>\Desktop\printcraft-0.2.1-windows-x64.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
printcraft-cli.exe
C:\Program Files\PrintCraft\printcraft-cli.exe
05Isolated runtime analysis - +1 more recorded observation in Analyst mode
Network
Hosts contacted
- Contacted hostObserved
a1672.dscr.akamai.net
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.
- a1672.dscr.akamai.net
- 8.8.8.8
- 199.232.210.172
- 204.79.197.203
- 23.35.30.73
- 162.159.36.2
- F40042E2E5F7E8EF8189FED15519AECE42C3BFA2\Blob
- Software\Microsoft\Windows\CurrentVersion\Explorer\GlobalAssocChangedCounter
- HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Installer\InProgress\(Default)
- HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\App Paths\printcraft.exe\(Default)
- HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\{01FD4CEA-7B74-47A6-B4C3-7176431F9203}\InstallSource
- HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\{01FD4CEA-7B74-47A6-B4C3-7176431F9203}\Publisher
- C:\Windows\ServiceProfiles\LocalService\AppData\Local\FontCache\Fonts\Download-1.tmp
- C:\Program Files\PrintCraft\printcraft-cli.exe
- C:\Program Files\PrintCraft\printcraft.exe
- C:\ProgramData\Microsoft\Windows\Start Menu\Programs\PrintCraft.lnk
- C:\MSI784c6.tmp
- C:\MSI784c6.tmp
- Global\_MSIExecute
- \Sessions\1\BaseNamedObjects\Global\_MSIExecute
- \BaseNamedObjects\Local\SM0:2184:304:WilStaging_02
- \BaseNamedObjects\Local\SM0:2184:120:WilError_03
Detection & Forensics
Consensus, attribution, signatures, code structure, prevalence, and identity.
Evidence integrity
Chain of custody for the facts preserved in this report.
- 2rule hits recorded
- 0 / 75engines flagged
- 220sources 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 75 antivirus engines flagged the file.
ProvenanceObservedSourceAntivirus analysisObserved at - 03
The file has a valid code signature from Learning Machines Inc.
ProvenanceObservedSourceCode-signing metadataObserved at - 04
Scanned file: printcraft-0.2.1-windows-x64.msi — 35408d34f23fbb1224251a95d04a4a7c3472f24faa6609ba8c953f4d46fcc6cf
ProvenanceObservedSourceUploaded fileObserved at - 05
Observed process — "C:\Windows\system32\msiexec.exe" /I "C:\Users\<USER>\Desktop\printcraft-0.2.1-windows-x64.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: printcraft-cli.exe — C:\Program Files\PrintCraft\printcraft-cli.exe
ProvenanceObservedSourceIsolated runtime analysisObserved at - 09
Contacted host: a1672.dscr.akamai.net — 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.exe
0 of 75 engines flagged this file
View all 75 engine results
PE structure
Not applicablePE structure analysis applies to Windows executable formats, not this file type.
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.
Fingerprint and provenance
- File name
- printcraft-0.2.1-windows-x64.msi
- Format
- Windows Installer
- Code signing
- Signature valid: Learning Machines Inc
- Size
- 32.8 MB
- Last analyzed
- Oct 8, 2026, 11:32 AM UTC
35408d34f23fbb1224251a95d04a4a7c3472f24faa6609ba8c953f4d46fcc6cfSafety & 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 printcraft-0.2.1-windows-x64.msi safe, or is it malware?
What is printcraft-0.2.1-windows-x64.msi?
How many antivirus engines detected printcraft-0.2.1-windows-x64.msi?
I already downloaded and installed printcraft-0.2.1-windows-x64.msi — what should I do?
How do I remove printcraft-0.2.1-windows-x64.msi?
Is printcraft-0.2.1-windows-x64.msi digitally signed?
What is the SHA-256 hash of printcraft-0.2.1-windows-x64.msi?
How up to date is this analysis of printcraft-0.2.1-windows-x64.msi?
Community
Member reviews and reports for this exact file hash.