File scan report
Verdict Suspicious
Is vpnus- setup. exe safe? Treat it as suspicious.
Only 1 of the 69 antivirus engines that checked it detected the unsigned installer, but observed activity and three reputation-unchecked IP connections justify caution.
Read the whole reasonShow less
Why Suspicious? One antivirus engine (Deep Instinct) flags it; nothing else confirms it.
Limited evidence · One sign points to a problem; nothing else confirms it.
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.
What to do now4 steps
Some signs point to a problem, but nothing confirms it is harmful. Treat it with caution.
What to do
Don't install it unless you're sure where it came from.
Check where you got it: an unexpected attachment, a link someone sent you or a re-upload is a red flag.
If you can't confirm where it came from, delete it. If you need the program, download it again from the publisher's own website.
If you already installed it
Stop using it, run a full scan with your antivirus and watch for unexpected behavior or security alerts.
Not sure what to do?
Ask the MalwareTips community before you run it. If you already ran it, follow the cleanup guide.
- Ask for free help on the MalwareTips forumWindows malware removal help, answered by volunteers. (opens malwaretips.com in a new tab)
- Remove malware from WindowsStep-by-step cleanup with free tools. (opens malwaretips.com in a new tab)
Paste this report's link in your topic so helpers can see what was found.
Reads the latest antivirus results for this file's hash. Nothing is uploaded.
Antivirus results
1 of 69 flagged
- Flagged 1
- No detection 68
- No result 6
- Code signing Unsigned
- Test run Completed
- First seen 1mo ago
Chapter 02
Why we think so
4 points against it and 5 in its favour, checked against the scan evidence.
The reasoning behind this verdict
The antivirus result is weak: DeepInstinct alone flagged the file, while no major antivirus engines identified malware or a family.
DeepInstinct was the only detector among 75 engines, and none of the major antivirus 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 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. 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 import-table fingerprint, 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 major antivirus 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 import-table fingerprint, 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 security software 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 major antivirus engines reported no detection, including Avast, BitDefender, ESET-NOD32, Kaspersky, and Fortinet.
- No sandbox returned a malicious verdict, and no dropped file is known to be malicious across four inspected children.
- The absence of a MalwareBazaar listing and the absence of community YARA matches provide no independent malware-family corroboration.
- The import-table fingerprint history points toward OfferCore, but all five matches lack a matching signer 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 the 69 antivirus engines that checked it detected the file
- No major antivirus engines flagged it and no major family consensus
- No sandbox returned a malicious verdict
- No dropped file is known to be malicious across four inspected files
- No MalwareBazaar or YARAify corroboration
- Unsigned Windows executable with no verified publisher history
- Direct connections to three IP addresses without complete reputation coverage
- Only two days since first submission
- OfferCore-related import-table fingerprint history, although a matching signer is absent
6 sources checked · 5 complete · 1 partial. See every source
Chapter 03
What it did in our test
It ran in our isolated test environment; no test environment rated what it did as risky.
Test run summary
Capture complete- 15sandbox rule tags
- 6spawned processes
- 2network contacts
- 7filesystem & mutex artifacts
What the test run showed
What the file did on a test computer
Confirmed in the test run
Moderate concern: Contains packed or scrambled code that is harder to inspect (common in installers too).
Moderate concern: Checked whether it was running on a test computer.
Moderate concern: Hid files or windows on the test computer.
Note: Read the user name of the test computer.
Note: Deleted files or logs during the test run (installers often clean up after themselves).
Note: Talked to servers over the internet during the test run.
Note: Read basic details of the test computer, such as its Windows version.
Sandbox labels we could not confirm (common in safe files too)
Not confirmed: A sandbox rule tagged this run as code injection, but no injected program was recorded.
Not confirmed: A sandbox rule tagged this run as weakening security settings; no setting change was recorded.
This file was run on a test computer (a sandbox), not on yours. Labels we could not confirm are listed so you can see them, but they are not treated as evidence against the file.
Recorded behavior
What happened in the test
Grouped by step. The order is not a timeline.
- 1
Input file
The submitted object
- Evidence 1 of 7: FileSeen in the test run
vpnus-setup.exe
da6ee86ea45f3990dc39afe071e38f16efade26690a52eb985fb568ffa6bbd5b
Uploaded file
- 2
Processes
What ran
- Evidence 2 of 7: ProcessSeen in the test run
vpnus-setup.exe
"C:\Users\<USER>\Desktop\vpnus-setup.exe"
Test run - Evidence 3 of 7: ProcessSeen in the test run
vpnus-setup.tmp
"C:\Users\<USER>\AppData\Local\Temp\is-3D9MYK9YIT.tmp\vpnus-setup.tmp" /SL5="$1A006E,31280549,986624,C:\Users\<USER>\Desktop\vpnus-setup.exe"
Test run - +1 more recorded observation
- 2
Files
Created or changed
- Evidence 4 of 7: Written fileSeen in the test run
vpnus-setup.tmp
C:\Users\<USER>\AppData\Local\Temp\is-3D9MYK9YIT.tmp\vpnus-setup.tmp
Test run - Evidence 5 of 7: Written fileSeen in the test run
gui.log
C:\ProgramData\VPNUS\gui.log
Test run - +1 more recorded observation
- 2
Network
Hosts contacted
- Evidence 6 of 7: Contacted hostSeen in the test run
5.129.240.234
Contacted during the test run.
Test run - Evidence 7 of 7: Contacted hostSeen in the test run
34.160.81.0
Contacted during the test run.
Test run - +1 more recorded observation
7 facts from the test run. See the full activity list.
What this file did when executed
This file was run in a sandbox and its runtime behaviour was observed.
Techniques observed in the sandbox
15MITRE ATT&CK techniques the sandbox mapped. Highlighted ones are rare in normal software; the others are common in legitimate programs too.
- T1012
- T1027· Obfuscated code
- T1027.002· Obfuscated code
- T1033· Reads user info
- T1047
- T1055· Process injection
- T1070· Covers its tracks
- T1071· Application protocol
- T1082· System recon
- T1129· Loads modules
- T1202
- T1497· Sandbox evasion
- T1562· Disables security
- T1564· Hides artifacts
- T1564.003· Hides artifacts
Observed activity
Processes started
6Programs the file ran, with their command lines.
vpnus-setup.exe"C:\Users\<USER>\Desktop\vpnus-setup.exe"vpnus-setup.tmp"C:\Users\<USER>\AppData\Local\Temp\is-3D9MYK9YIT.tmp\vpnus-setup.tmp" /SL5="$1A006E,31280549,986624,C:\Users\<USER>\Desktop\vpnus-setup.exe"vpnus.exe"C:\Program Files\VPNUS\vpnus.exe"wmicwmic ComputerSystem get TotalPhysicalMemory /VALUEvpnus-setup.exe"C:\Users\user\Desktop\vpnus-setup.exe"vpnus-setup.tmp"C:\Users\user\AppData\Local\Temp\is-59OXS7RADT.tmp\vpnus-setup.tmp" /SL5="$103DE,31280549,986624,C:\Users\user\Desktop\vpnus-setup.exe"
Network contacts
22 hosts, listed as 2 addresses. Links show the host and path only.
- IP address
5.129.240.234 - IP address
34.160.81.0
Files
7Files the file created, changed or deleted.
- Written
C:\Users\<USER>\AppData\Local\Temp\is-3D9MYK9YIT.tmp\vpnus-setup.tmp - Written
C:\ProgramData\VPNUS\gui.log - Written
\Device\ConDrv\Connect - Written
C:\Users\<USER>\AppData\Roaming\VPNUS\VPNUS\shared_preferences.json - Written
C:\Users\<USER>\AppData\Roaming\VPNUS\VPNUS\flutter_secure_storage.dat - Written
C:\Users\user\AppData\Local\Temp\is-59OXS7RADT.tmp
Show all 7 entries for files
- Written
C:\Users\user\AppData\Local\Temp\is-59OXS7RADT.tmp\vpnus-setup.tmp
Sandbox background — not the file
1The analysis machine's own processes and connections, recorded in every run.
- VM host
162.159.36.2
Files this sample writes at runtime
This file drops 4 children at runtime. None are currently flagged malicious in our cache. 4 have no saved verdict and were not checked; that is missing coverage, not a finding.
- a785ca9d7f6b61ea2386…72b233Not checkedno saved verdict
- 09ae2a32e306f677d3cb…56d053Not checkedno saved verdict
- 9a473be2530b2c803f19…4b60dcNot checkedno saved verdict
- c1c0252374195c33a511…ed67a3Not checkedno saved verdict
Chapter 04
Technical details
1 of the 69 antivirus engines that checked it flags it; no publisher signature.
Sources checked
Every check behind this verdict
6 sources checked · 5 complete · 1 partial. Complete means the check returned a usable result; it does not mean the file is safe.
Engines that flagged it 1
- DeepInstinctMALICIOUS
File fingerprint
- Last analyzed
- Sep 10, 2026, 6:41 AM UTC
- SHA-256
da6ee86ea45f3990dc39afe071e38f16efade26690a52eb985fb568ffa6bbd5b- SHA-1
fae83ab3a55128e5bb322b0c2dbb00eb18fdb45b- MD5
2ce55315dc0d8b3b91e73da65ddc5dff
About this file
vpnus-setup.exe is a Win32 EXE file of 32.6 MB.
- Type and size
- Win32 EXE · 32.6 MB
- Signer
- UnsignedNo code signature.
- First seen
- Sep 8, 2026On VirusTotal.
- Submitted by
- 18 distinct sources
- Packer
- None detected
- Entropy
- 8.00 of 8
First scanned
Antivirus consensus
1 of 69 engines flagged this file
6 of the 75 engines returned no result for this file (file type not supported, or the scan did not finish), so they did not check it.
- Tier-117 engines0flagged
- Tier-235 engines1flagged
- Low-trust17 engines0flagged
View all 75 engine results
- DeepInstinctMalicious: MALICIOUS
- AcronisClean
- AhnLab-V3Clean
- AlibabaClean
- alibabacloudClean
- ALYacClean
- Antiy-AVLClean
- APEXClean
- ArcabitClean
- AvastClean
- Avast-MobileNo result
- AVGClean
- AviraClean
- BitDefenderClean
- BitDefenderFalxNo result
- BkavClean
- CAT-QuickHealClean
- ClamAVClean
- CMCClean
- CrowdStrikeClean
- CTXClean
- CylanceClean
- CynetClean
- DrWebClean
- ElasticClean
- EmsisoftClean
- ESET-NOD32Clean
- F-SecureClean
- FortinetClean
- GDataClean
- GoogleClean
- GridinsoftClean
- huorongClean
- IkarusNo result
- JiangminClean
- K7AntiVirusClean
- K7GWClean
- KasperskyClean
- KingsoftClean
- LionicClean
- MalwarebytesClean
- MaxSecureClean
- McAfeeDClean
- MicrosoftClean
- MicroWorld-eScanClean
- NANO-AntivirusClean
- PaloaltoClean
- PandaClean
- RisingClean
- SangforClean
- SentinelOneClean
- SkyhighNo result
- SophosClean
- SUPERAntiSpywareClean
- SymantecClean
- SymantecMobileInsightNo result
- TACHYONClean
- tehtrisClean
- TencentClean
- TrapmineClean
- TrellixENSClean
- TrendMicroClean
- TrendMicro-HouseCallClean
- TrustlookNo result
- VaristClean
- VBA32Clean
- VIPREClean
- VirITClean
- ViRobotClean
- WebrootClean
- XcitiumClean
- YandexClean
- ZillyaClean
- ZoneAlarmClean
- ZonerClean
Signatures and behavior heuristics
Low-severity pattern matches — worth noting but not on their own cause for alarm.
VirusTotal's sandbox summary maps this run to MITRE T1055 (Process Injection), but no injected process of the sample's own was recorded (the analysis VM's own WMI adapter, crash handlers and Chrome updater are not counted). VirusTotal maps T1055 on about half of all files no engine flags, so the mapping alone is not evidence of injection.
EvidenceT1055 (sandbox MITRE mapping)
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.
Chapter 05
Questions & answers
Short answers to the 6 questions people ask most about this file.
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?
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.