Is lapack.exe safe?
No antivirus engine detected the file, but one sandbox recorded possible process injection, LSASS-related activity, and unverified direct-IP communications requiring caution.
All 74 antivirus engines were silent, including 17 tier-1 engines, and no external intelligence source identified a malware family. However, one sandbox recorded T1055, LSASS-related activity, and direct-IP traffic whose destinations were not reputation-checked, so execution should be deferred pending deeper review.
cd447e41945d48bd06…67ce7160cfe82aRecommended 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.
All 74 antivirus engines were silent, including 17 tier-1 engines, and no external intelligence source identified a malware family. However, one sandbox recorded T1055, LSASS-related activity, and direct-IP traffic whose destinations were not reputation-checked, so execution should be deferred pending deeper review.
The static detection picture is strongly favorable: 0 of 74 engines flagged the executable, with all 17 reporting tier-1 engines silent. One completed sandbox nevertheless mapped activity to T1055 and recorded interaction involving lsass.exe, both of which merit investigation. The same run contacted several external IP addresses, but no complete host-reputation result is available because the contacted-host check was not saved. Neither the sandbox nor the two inspected child files produced a confirmed malicious result, although both child verdicts remain unknown. The file is unsigned, and no trusted publisher, family consensus, research rule, or similar-file history resolves the conflict. These mixed signals support containment and further analysis rather than routine execution.
What We Detected
None of 74 antivirus engines flagged the executable, including all 17 reporting tier-1 engines. The file has also been known since 2013 and is not packed, but it is unsigned and has no publisher history to establish provenance.
Threat Behavior
One completed sandbox run mapped activity to MITRE T1055, indicating possible process injection, and recorded process activity involving Windows LSASS. It also observed direct connections to external IP addresses. These behavioral indicators are concerning, but the sandbox did not issue a malicious verdict, and no complete reputation check is available for the contacted hosts. Two dropped files were inspected without a confirmed malicious child, though both individual outcomes remain unknown.
What To Do Now
Do not run the executable on a production system until its origin and purpose are verified. Keep endpoint protection enabled, quarantine the file if it arrived unexpectedly, and use an isolated analysis environment for any necessary testing.
Where this verdict could be wrong4 caveats
- The complete 0/74 engine result, including 17 tier-1 engines, weighs strongly against known malware.
- behaviour.hasMaliciousSandboxVerdict=false, so the completed sandbox did not assign a malicious runtime verdict.
- The executable is unsigned (signing.signed=false), leaving no publisher identity or signer history to support legitimacy.
- externalIntel.yaraify.ruleCount=0 and externalIntel.circl.hit=false provide no research-based corroboration, though absence of a hit does not rule out a threat.
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 of 74 antivirus engines detected the file.
- All 17 reporting tier-1 engines were undetected.
- behaviour.hasMaliciousSandboxVerdict=false.
- No malicious dropped child was confirmed among 2 inspected hashes.
- YARAify, CIRCL, and MalwareBazaar supplied no corroborating hit.
- One sandbox mapped runtime activity to MITRE T1055 process injection.
- Sandbox process evidence involved lsass.exe, which can indicate credential-access behavior.
- External IP communications were observed without a completed host-reputation cross-check.
- The executable is unsigned and has no established signer history.
- Both dropped-child verdicts remain unknown.
Keep endpoint protection enabled and avoid production execution until the file's source is verified and the observed LSASS, injection, and network activity is reviewed in isolation.
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
Partial7 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
- 16MITRE ATT&CK techniques
- 11spawned processes
- 7network contacts
- 33filesystem & 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: Manipulated how the operating system loads code, which can redirect execution.
Moderate concern: Contained obfuscated or packed code that makes inspection harder.
Moderate concern: Runs hidden system commands (script or shell).
Moderate concern: Removed execution artefacts or logs, which can conceal activity.
Moderate concern: Communicated over a common application protocol; malware can use this for command-and-control.
Moderate concern: Scans through your files and folders.
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
lapack.exe
cd447e41945d48bd06e8afee9eafa536304296f3ee5b24f4ac67ce7160cfe82a
01Uploaded file
Processes
Runtime execution
- ProcessObserved
Observed process
"C:\Users\<USER>\Desktop\program.exe"
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
udhisapi.dll
C:\Windows\ServiceProfiles\LocalService\AppData\Roaming\Microsoft\UPnP Device Host\upnphost\udhisapi.dll
04Isolated runtime analysis - Written fileObserved
WER736F.tmp
C:\ProgramData\Microsoft\Windows\WER\Temp\WER736F.tmp
05Isolated runtime analysis - +1 more recorded observation in Analyst mode
Network
Hosts contacted
- Contacted hostObserved
a83f:8110:9001:0:883:ed9c:9001:0
Contact observed during runtime.
06Isolated runtime analysis - Contacted hostObserved
192.168.0.1
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.
- a83f:8110:9001:0:883:ed9c:9001:0
- 192.168.0.1
- 192.229.211.108
- 23.40.197.40
- 20.99.133.109
- a83f:8110:0:0:0:0:2002:0
- 20.22.113.133
- C:\Windows\ServiceProfiles\LocalService\AppData\Roaming\Microsoft\UPnP Device Host\upnphost\udhisapi.dll
- C:\ProgramData\Microsoft\Windows\WER\Temp\WER736F.tmp
- C:\ProgramData\Microsoft\Windows\WER\Temp\WER736F.tmp.dmp
- C:\ProgramData\Microsoft\Windows\WER\Temp\WER762F.tmp
- C:\ProgramData\Microsoft\Windows\WER\Temp\WER762F.tmp.WERInternalMetadata.xml
- C:\ProgramData\Microsoft\Windows\WER\Temp\WEREF71.tmp.WERInternalMetadata.xml
- C:\ProgramData\Microsoft\Windows\WER\Temp\WEREF82.tmp.csv
- C:\ProgramData\Microsoft\Windows\WER\Temp\WEREF83.tmp.txt
- C:\Windows\System32\spp\store\2.0\cache\cache.dat
- C:\ProgramData\Microsoft\Windows\WER\Temp\WER3515.tmp.WERInternalMetadata.xml
- Local\Shell.CMruPidlList
- Global\OneSettingQueryMutex+compat+encapsulation
- CTF.LBES.MutexDefaultS-1-5-21-1482476501-1645522239-1417001333-500
- CTF.Compart.MutexDefaultS-1-5-21-1482476501-1645522239-1417001333-500
- CTF.Asm.MutexDefaultS-1-5-21-1482476501-1645522239-1417001333-500
Files this sample writes at runtime
This file drops 2 children at runtime. None are currently flagged malicious in our cache.
- 439869eb57bfb052bb35…87c889Never scannednever seen before
- a39516f1c3ec257ffcf2…63ae3dNever 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.
- 3rule hits recorded
- 0 / 74engines flagged
- 35sources 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 hash has been submitted 43 times from 35 sources.
ProvenanceDerivedSourceSaved report factsObserved at - 04
Scanned file: lapack.exe — cd447e41945d48bd06e8afee9eafa536304296f3ee5b24f4ac67ce7160cfe82a
ProvenanceObservedSourceUploaded fileObserved at - 05
Observed process — "C:\Users\<USER>\Desktop\program.exe"
ProvenanceObservedSourceIsolated runtime analysisObserved at - 06
Observed process — C:\Windows\system32\services.exe
ProvenanceObservedSourceIsolated runtime analysisObserved at - 07
File written: udhisapi.dll — C:\Windows\ServiceProfiles\LocalService\AppData\Roaming\Microsoft\UPnP Device Host\upnphost\udhisapi.dll
ProvenanceObservedSourceIsolated runtime analysisObserved at - 08
File written: WER736F.tmp — C:\ProgramData\Microsoft\Windows\WER\Temp\WER736F.tmp
ProvenanceObservedSourceIsolated runtime analysisObserved at - 09
Contacted host: a83f:8110:9001:0:883:ed9c:9001:0 — Contact observed during runtime.
ProvenanceObservedSourceIsolated runtime analysisObserved at - 10
Contacted host: 192.168.0.1 — 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.
Evidencea83f:8110:9001:0:883:ed9c:9001:0 · 192.229.211.108 · 23.40.197.40
0 of 74 engines flagged this file
View all 74 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
Moderate prevalence — neither rare nor common. No strong prior applies.
Fingerprint and provenance
- File name
- lapack.exe
- Format
- Win32 EXE
- Code signing
- No verified publisher
- Size
- 852.0 KB
- Last analyzed
- Sep 22, 2026, 12:22 PM UTC
cd447e41945d48bd06e8afee9eafa536304296f3ee5b24f4ac67ce7160cfe82aSafety & 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 lapack.exe safe, or is it malware?
What is lapack.exe?
How many antivirus engines detected lapack.exe?
What should I do if I already ran lapack.exe?
How do I remove lapack.exe?
What is the SHA-256 hash of lapack.exe?
How up to date is this analysis of lapack.exe?
Community
Member reviews and reports for this exact file hash.