Is vpnus-setup.exe safe?
Only 1 of 75 engines detected the unsigned installer, but observed T1055 activity and three reputation-unchecked IP connections justify caution.
The antivirus result is weak: DeepInstinct alone flagged the file, while no tier-1 engine identified malware or a family. However, the unsigned installer produced a T1055 process-injection mapping and contacted three IP addresses whose reputations were not checked, so execution should be deferred until the source and network destinations are verified.
da6ee86ea45f3990dc…fb568ffa6bbd5bRecommended 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.
The antivirus result is weak: DeepInstinct alone flagged the file, while no tier-1 engine identified malware or a family. However, the unsigned installer produced a T1055 process-injection mapping and contacted three IP addresses whose reputations were not checked, so execution should be deferred until the source and network destinations are verified.
DeepInstinct was the only detector among 75 engines, and none of the tier-1 engines identified a threat family. The executable is unsigned and has no established publisher history, which reduces confidence in its claimed installer role. One completed sandbox run mapped activity to MITRE T1055 and observed direct communication with three IP addresses, although it did not issue a malicious runtime finding. No complete host-reputation result is available for those addresses, so the no complete contacted-host reputation result was available. Four dropped files produced no malicious child finding, and researcher intelligence supplied no corroborating family match. Prior OfferCore-related files share the imphash, but their different signers make those matches weak framework-level leads rather than attribution evidence.
What We Detected
DeepInstinct was the only engine to flag the sample out of 75, while tier-1 engines such as BitDefender, ESET-NOD32, Kaspersky, and Fortinet did not detect it. No engine consensus or reliable family identification was present. The executable is unsigned and lacks an established signer history.
Threat Behavior
One completed sandbox run mapped activity to MITRE T1055 and recorded connections to 5.129.240.234, 34.160.81.0, and 162.159.36.2. No complete reputation check was saved for these destinations, so their risk remains unresolved. The sandbox did not return a malicious verdict, and none of the four inspected dropped files was identified as malicious. Similar files associated with OfferCore share this imphash, but all use different signers, making a common installer framework a plausible explanation.
What To Do Now
Do not run the installer on a production system until its download source and publisher can be independently verified. Keep endpoint protection enabled, and if testing is necessary, use an isolated environment with network monitoring and validate the three contacted IP addresses first.
Where this verdict could be wrong4 caveats
- Sixteen tier-1 engines reported no detection, including Avast, BitDefender, ESET-NOD32, Kaspersky, and Fortinet.
- behaviour.hasMaliciousSandboxVerdict=false, and droppedChildren.hasMaliciousChild=false across four inspected children.
- externalIntel.malwareBazaar.hit=false and externalIntel.yaraify.ruleCount=0 provide no independent malware-family corroboration.
- The imphash history points toward OfferCore, but all five matches lack signer co-matching and may reflect a shared installer framework rather than shared payload code.
These are the assessment's weak points. If you believe one applies to your file, report the verdict and we'll re-review it.
- Only 1 of 75 engines detected the file
- engines.tier1Malicious=0 and no tier-1 family consensus
- behaviour.hasMaliciousSandboxVerdict=false
- droppedChildren.hasMaliciousChild=false across four inspected files
- No MalwareBazaar or YARAify corroboration
- Unsigned Windows executable with no verified publisher history
- MITRE T1055 process-injection mapping in completed runtime evidence
- Direct connections to three IP addresses without complete reputation coverage
- Only two days since first submission
- OfferCore-related imphash history, although signer co-matching is absent
Avoid installing it until the publisher and official distribution source are verified. Keep security protection enabled and use an isolated test environment if further examination is required.
Coverage & freshness
Complete means the check returned a usable result. It does not mean the file is safe.
Antivirus
Complete1 of 75 engines flagged the file.
Sandbox
Complete1 isolated runtime environment contributed observations.
Network
Partial3 runtime contacts were observed without a completed reputation cross-check.
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
- 15MITRE ATT&CK techniques
- 6spawned processes
- 3network contacts
- 7filesystem & 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: Attempted to impair or bypass security controls.
Moderate concern: Contained obfuscated or packed code that makes inspection harder.
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: Checked the environment for virtualisation or analysis tools.
Note: Reads your Windows user-account details.
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
vpnus-setup.exe
da6ee86ea45f3990dc39afe071e38f16efade26690a52eb985fb568ffa6bbd5b
01Uploaded file
Processes
Runtime execution
- ProcessObserved
Observed process
"C:\Users\<USER>\Desktop\vpnus-setup.exe"
02Isolated runtime analysis - ProcessObserved
Observed process
"C:\Users\<USER>\AppData\Local\Temp\is-3D9MYK9YIT.tmp\vpnus-setup.tmp" /SL5="$1A006E,31280549,986624,C:\Users\<USER>\Desktop\vpnus-setup.exe"
03Isolated runtime analysis - +1 more recorded observation in Analyst mode
Files
Created or changed
- Written fileObserved
vpnus-setup.tmp
C:\Users\<USER>\AppData\Local\Temp\is-3D9MYK9YIT.tmp\vpnus-setup.tmp
04Isolated runtime analysis - Written fileObserved
gui.log
C:\ProgramData\VPNUS\gui.log
05Isolated runtime analysis - +1 more recorded observation in Analyst mode
Network
Hosts contacted
- Contacted hostObserved
5.129.240.234
Contact observed during runtime.
06Isolated runtime analysis - Contacted hostObserved
34.160.81.0
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.
- 5.129.240.234
- 34.160.81.0
- 162.159.36.2
- C:\Users\<USER>\AppData\Local\Temp\is-3D9MYK9YIT.tmp\vpnus-setup.tmp
- C:\ProgramData\VPNUS\gui.log
- \Device\ConDrv\Connect
- C:\Users\<USER>\AppData\Roaming\VPNUS\VPNUS\shared_preferences.json
- C:\Users\<USER>\AppData\Roaming\VPNUS\VPNUS\flutter_secure_storage.dat
Files this sample writes at runtime
This file drops 4 children at runtime. None are currently flagged malicious in our cache.
- a785ca9d7f6b61ea2386…72b233Never scannednever seen before
- 09ae2a32e306f677d3cb…56d053Never scannednever seen before
- 9a473be2530b2c803f19…4b60dcNever scannednever seen before
- c1c0252374195c33a511…ed67a3Never 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
- 1 / 75engines flagged
- 18sources 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
1 of 75 antivirus engines flagged the file, including DeepInstinct.
Verdict inputView chapterProvenanceObservedSourceAntivirus analysisObserved at - 03
The hash has been submitted 21 times from 18 sources.
ProvenanceDerivedSourceSaved report factsObserved at - 04
Scanned file: vpnus-setup.exe — da6ee86ea45f3990dc39afe071e38f16efade26690a52eb985fb568ffa6bbd5b
ProvenanceObservedSourceUploaded fileObserved at - 05
Observed process — "C:\Users\<USER>\Desktop\vpnus-setup.exe"
ProvenanceObservedSourceIsolated runtime analysisObserved at - 06
Observed process — "C:\Users\<USER>\AppData\Local\Temp\is-3D9MYK9YIT.tmp\vpnus-setup.tmp" /SL5="$1A006E,31280549,986624,C:\Users\<USER>\Desktop\vpnus-setup.exe"
ProvenanceObservedSourceIsolated runtime analysisObserved at - 07
File written: vpnus-setup.tmp — C:\Users\<USER>\AppData\Local\Temp\is-3D9MYK9YIT.tmp\vpnus-setup.tmp
ProvenanceObservedSourceIsolated runtime analysisObserved at - 08
File written: gui.log — C:\ProgramData\VPNUS\gui.log
ProvenanceObservedSourceIsolated runtime analysisObserved at - 09
Contacted host: 5.129.240.234 — Contact observed during runtime.
ProvenanceObservedSourceIsolated runtime analysisObserved at - 10
Contacted host: 34.160.81.0 — 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.
Evidence"C:\Users\<USER>\Desktop\vpnus-setup.exe"The 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.
Evidence5.129.240.234 · 34.160.81.0 · 162.159.36.2
1 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
Moderate prevalence — neither rare nor common. No strong prior applies.
Fingerprint and provenance
- File name
- vpnus-setup.exe
- Format
- Win32 EXE
- Code signing
- No verified publisher
- Size
- 31.1 MB
- Last analyzed
- Sep 10, 2026, 6:41 AM UTC
da6ee86ea45f3990dc39afe071e38f16efade26690a52eb985fb568ffa6bbd5bSafety & 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 vpnus-setup.exe safe, or is it malware?
What is vpnus-setup.exe?
How many antivirus engines detected vpnus-setup.exe?
I already downloaded and installed vpnus-setup.exe — what should I do?
How do I remove vpnus-setup.exe?
What is the SHA-256 hash of vpnus-setup.exe?
How up to date is this analysis of vpnus-setup.exe?
Community
Member reviews and reports for this exact file hash.