Is newhv.exe safe?
Unsigned history, rare_new prevalence, and sandbox evidence of process injection plus LSASS access create mixed signals.
No antivirus engine flagged the file, yet the sample is only four days old, signed by an unknown publisher, and the sandbox recorded process-injection and LSASS-access activity. These runtime signals outweigh the clean engine results and justify a suspicious rating.
021f74327711787660…4d96dd79b25f10Recommended 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.
No antivirus engine flagged the file, yet the sample is only four days old, signed by an unknown publisher, and the sandbox recorded process-injection and LSASS-access activity. These runtime signals outweigh the clean engine results and justify a suspicious rating.
Zero detections across 75 engines removes the possibility of a tier-1 consensus, but the complete absence of prior signer history and the file’s rare_new status leave no benign track record to rely on. Sandbox telemetry shows T1055 process injection and direct targeting of lsass.exe, behaviours that legitimate utilities rarely exhibit. Direct-IP connections without domain names add another layer of concern. Because the evidence is split between clean static signals and suspicious runtime indicators, the file sits in the borderline-mixed-signals category.
What We Detected
75 engines returned zero malicious verdicts. The executable is signed by “VisoDyne,” but that signer has no prior samples in our database. Sandbox execution recorded MITRE T1055 (process injection) and direct reads against LSASS, triggering three heuristic rules.
Threat Behavior
The observed LSASS access and process-injection techniques are consistent with credential-dumping tooling. Six external IP addresses were contacted without domain names, a pattern that can appear in both legitimate updaters and covert C2 channels.
What To Do Now
Do not execute the file on production systems. Keep Windows Defender and other endpoint protection enabled. If the binary is required for a specific task, run it only in an isolated virtual machine and monitor for credential theft or lateral movement.
- 0/75 engines flagged the sample
- rare_new prevalence (2 submissions)
- unknown signer with no history
- sandbox T1055 process injection observed
- LSASS access flagged by heuristic
- direct-IP connections without domains
Treat the file as untrusted; block or sandbox it until a trusted publisher or additional benign history appears.
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
Partial6 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
- 9MITRE ATT&CK techniques
- 9spawned processes
- 6network contacts
- 0filesystem & 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: Communicated over a common application protocol; malware can use this for command-and-control.
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
newhv.exe
021f74327711787660f267ad5610813013f2095f80628f012a4d96dd79b25f10
01Uploaded file
Processes
Runtime execution
- ProcessObserved
Observed process
"C:\Users\<USER>\Desktop\VisoDyneBatteryMonitorSetup-win64.exe"
02Isolated runtime analysis - ProcessObserved
Observed process
C:\Windows\system32\services.exe
03Isolated runtime analysis - +1 more recorded observation in Analyst mode
Network
Hosts contacted
- Contacted hostObserved
172.67.142.41
Contact observed during runtime.
04Isolated runtime analysis - Contacted hostObserved
185.199.109.133
Contact observed during runtime.
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.
- 172.67.142.41
- 185.199.109.133
- 140.82.114.3
- 185.199.108.133
- 150.171.28.11
- 104.21.94.251
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 / 75engines flagged
- 2sources 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 hash has been submitted 2 times from 2 sources.
ProvenanceDerivedSourceSaved report factsObserved at - 04
Scanned file: newhv.exe — 021f74327711787660f267ad5610813013f2095f80628f012a4d96dd79b25f10
ProvenanceObservedSourceUploaded fileObserved at - 05
Observed process — "C:\Users\<USER>\Desktop\VisoDyneBatteryMonitorSetup-win64.exe"
ProvenanceObservedSourceIsolated runtime analysisObserved at - 06
Observed process — C:\Windows\system32\services.exe
ProvenanceObservedSourceIsolated runtime analysisObserved at - 07
Contacted host: 172.67.142.41 — Contact observed during runtime.
ProvenanceObservedSourceIsolated runtime analysisObserved at - 08
Contacted host: 185.199.109.133 — 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.
Evidence172.67.142.41 · 185.199.109.133 · 140.82.114.3
0 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. That limits reputation evidence, but rarity alone is not proof of malware.
Fingerprint and provenance
- File name
- newhv.exe
- Format
- Win32 EXE
- Code signing
- Signature not verified: VisoDyne
- Size
- 6.4 MB
- Last analyzed
- Aug 26, 2026, 2:36 PM UTC
021f74327711787660f267ad5610813013f2095f80628f012a4d96dd79b25f10Safety & 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 newhv.exe safe, or is it malware?
What is newhv.exe?
How many antivirus engines detected newhv.exe?
What should I do if I already ran newhv.exe?
How do I remove newhv.exe?
Is newhv.exe digitally signed?
What is the SHA-256 hash of newhv.exe?
How up to date is this analysis of newhv.exe?
Community
Member reviews and reports for this exact file hash.