Is LabelPrinter-Windows-Driver-Latest_Ver1.1.3.5.exe safe?
Rare, recently submitted installer signed by an unknown publisher that exhibits process-injection and LSASS-access behaviour.
Four of 75 engines flagged the file, one of them tier-1. The binary is signed but the publisher has no prior history, and sandbox evidence shows process injection plus LSASS access. Prevalence is rare_new and one similar imphash was previously rated suspicious.
228f408f32aa5261ee…ec0f6b0cda77cfRecommended next actions
Before running
Do not run it until the source and publisher can be verified independently.
If you already ran it
Stop using it, scan the device, and watch for unexpected behavior or security alerts. Get a fresh copy 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.
Four of 75 engines flagged the file, one of them tier-1. The binary is signed but the publisher has no prior history, and sandbox evidence shows process injection plus LSASS access. Prevalence is rare_new and one similar imphash was previously rated suspicious.
The single tier-1 detection is a generic PUA label rather than a named family, so it does not trigger a malicious consensus. However, the combination of an unsigned-publisher history, offensive MITRE techniques, and a prior suspicious imphash match outweighs the clean majority. No external-intel corroboration or malicious children exist, leaving the file in mixed-signals territory.
What We Detected
4 of 75 engines reported the sample; Sophos (tier-1) labelled it Generic ML PUA while CrowdStrike, Elastic and Cylance added lower-tier detections. The executable is signed by 'Xiamen Print Future Technology Co.' but that signer has no historical samples in our records. Sandbox execution recorded T1055 process injection and T1134 token manipulation plus direct LSASS access.
Threat Behavior
The observed techniques are commonly associated with credential-dumping or privilege-escalation tooling. No C2 domains, dropped malicious children, or external-intel hits were recorded. The file is two days old and has been submitted by only three sources.
What To Do Now
Do not run the installer on production systems. Keep endpoint protection enabled and consider obtaining the driver package from the device manufacturer’s official site instead.
Where this verdict could be wrong2 caveats
- contactedHosts=null — no complete host-reputation cross-check available
- droppedChildren.hasMaliciousChild=false and externalIntel.yaraify.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.
- majority engines (71/75) did not flag
- no malicious dropped children
- no external-intel hits
- rare_new prevalence
- unknown signer with zero history
- sandbox observed T1055 and LSASS access
Treat as potentially unwanted; obtain the driver from the hardware vendor’s verified distribution channel and keep security software active.
Coverage & freshness
Complete means the check returned a usable result. It does not mean the file is safe.
Antivirus
Complete4 of 75 engines flagged the file.
Sandbox
Complete1 isolated runtime environment contributed observations.
Network
Not runNo contacted-host reputation check is recorded.
No timestamp recordedYARA
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
- 15MITRE ATT&CK techniques
- 11spawned processes
- 0network contacts
- 12filesystem & 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.
Moderate concern: Contained obfuscated or packed code that makes inspection harder.
Moderate concern: Runs hidden system commands (script or shell).
Moderate concern: Communicated over a common application protocol; malware can use this for command-and-control.
Moderate concern: Scans through your files and folders.
Note: Reads your Windows user-account details.
Note: Collects details about your system.
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
LabelPrinter-Windows-Driver-Latest_Ver1.1.3.5.exe
228f408f32aa5261ee35b4052e2d7cfe0a86663445e5159b98ec0f6b0cda77cf
01Uploaded file
Processes
Runtime execution
- ProcessObserved
Observed process
"C:\Users\<USER>\Desktop\LabelPrinter-Windows-Driver-Latest_Ver1.1.3.5.exe"
02Isolated runtime analysis - ProcessObserved
Observed process
"C:\Users\<USER>\AppData\Local\Temp\is-FE3M2.tmp\LabelPrinter-Windows-Driver-Latest_Ver1.1.3.5.tmp" /SL5="$F0068,1601996,721408,C:\Users\<USER>\Desktop\LabelPrinter-Windows-Driver-Latest_Ver1.1.3.5.exe"
03Isolated runtime analysis - +1 more recorded observation in Analyst mode
Files
Created or changed
- Written fileObserved
LabelPrinter-Windows-Driver-Latest_Ver1.1.3.5.tmp
C:\Users\<USER>\AppData\Local\Temp\is-FE3M2.tmp\LabelPrinter-Windows-Driver-Latest_Ver1.1.3.5.tmp
04Isolated runtime analysis - Written fileObserved
LabelPrinter-Windows-Driver-Latest_Ver1.1.3.5.tmp
C:\Users\<USER>\AppData\Local\Temp\is-853O9.tmp\LabelPrinter-Windows-Driver-Latest_Ver1.1.3.5.tmp
05Isolated runtime analysis - +1 more recorded observation in Analyst mode
5 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.
- C:\Users\<USER>\AppData\Local\Temp\is-FE3M2.tmp\LabelPrinter-Windows-Driver-Latest_Ver1.1.3.5.tmp
- C:\Users\<USER>\AppData\Local\Temp\is-853O9.tmp\LabelPrinter-Windows-Driver-Latest_Ver1.1.3.5.tmp
- C:\Users\<USER>\AppData\Local\Temp\is-JTT1E.tmp\_isetup\_setup64.tmp
- C:\Users\user\AppData\Local\Programs
- C:\Users\user\AppData\Local\Programs\Common
- \Sessions\1\BaseNamedObjects\Local\RstrMgr3887CAB8-533F-4C85-B0DC-3E5639F8D511
- \Sessions\1\BaseNamedObjects\Local\RstrMgr-3887CAB8-533F-4C85-B0DC-3E5639F8D511-Session0000
Files this sample writes at runtime
This file drops 2 children at runtime. None are currently flagged malicious in our cache.
- 1a93f3e99afae583e7ad…7f9b4cNever scannednever seen before
- 388a796580234efc95f3…136f95Never scannednever seen before
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
- 4 / 75engines flagged
- 3sources 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
4 of 75 antivirus engines flagged the file, including CrowdStrike and Cylance.
Verdict inputView chapterProvenanceObservedSourceAntivirus analysisObserved at - 03
The file has a valid code signature from Xiamen Print Future Technology Co..
ProvenanceObservedSourceCode-signing metadataObserved at - 04
Scanned file: LabelPrinter-Windows-Driver-Latest_Ver1.1.3.5.exe — 228f408f32aa5261ee35b4052e2d7cfe0a86663445e5159b98ec0f6b0cda77cf
ProvenanceObservedSourceUploaded fileObserved at - 05
Observed process — "C:\Users\<USER>\Desktop\LabelPrinter-Windows-Driver-Latest_Ver1.1.3.5.exe"
ProvenanceObservedSourceIsolated runtime analysisObserved at - 06
Observed process — "C:\Users\<USER>\AppData\Local\Temp\is-FE3M2.tmp\LabelPrinter-Windows-Driver-Latest_Ver1.1.3.5.tmp" /SL5="$F0068,1601996,721408,C:\Users\<USER>\Desktop\LabelPrinter-Windows-Driver-Latest_Ver1.1.3.5.exe"
ProvenanceObservedSourceIsolated runtime analysisObserved at - 07
File written: LabelPrinter-Windows-Driver-Latest_Ver1.1.3.5.tmp — C:\Users\<USER>\AppData\Local\Temp\is-FE3M2.tmp\LabelPrinter-Windows-Driver-Latest_Ver1.1.3.5.tmp
ProvenanceObservedSourceIsolated runtime analysisObserved at - 08
File written: LabelPrinter-Windows-Driver-Latest_Ver1.1.3.5.tmp — C:\Users\<USER>\AppData\Local\Temp\is-853O9.tmp\LabelPrinter-Windows-Driver-Latest_Ver1.1.3.5.tmp
ProvenanceObservedSourceIsolated runtime analysisObserved at
Detection sources at a glance
Category: pua
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
4 of 75 engines flagged this file
View all 75 engine results
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.
How widely this file has been seen
Barely seen in the wild and first surfaced recently. 4 antivirus detections make that low prevalence materially relevant, but rarity alone is not proof of malware.
Fingerprint and provenance
- File name
- LabelPrinter-Windows-Driver-Latest_Ver1.1.3.5.exe
- Format
- Win32 EXE
- Code signing
- Signature valid: Xiamen Print Future Technology Co.
- Size
- 2.2 MB
- Last analyzed
- Aug 8, 2026, 1:49 AM UTC
228f408f32aa5261ee35b4052e2d7cfe0a86663445e5159b98ec0f6b0cda77cfSafety & 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 run 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. Get a fresh copy 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 LabelPrinter-Windows-Driver-Latest_Ver1.1.3.5.exe safe, or is it malware?
What is LabelPrinter-Windows-Driver-Latest_Ver1.1.3.5.exe?
How many antivirus engines detected LabelPrinter-Windows-Driver-Latest_Ver1.1.3.5.exe?
What should I do if I already ran LabelPrinter-Windows-Driver-Latest_Ver1.1.3.5.exe?
How do I remove LabelPrinter-Windows-Driver-Latest_Ver1.1.3.5.exe?
What kind of malware is LabelPrinter-Windows-Driver-Latest_Ver1.1.3.5.exe?
Is LabelPrinter-Windows-Driver-Latest_Ver1.1.3.5.exe digitally signed?
What is the SHA-256 hash of LabelPrinter-Windows-Driver-Latest_Ver1.1.3.5.exe?
How up to date is this analysis of LabelPrinter-Windows-Driver-Latest_Ver1.1.3.5.exe?
Community
Member reviews and reports for this exact file hash.