File scan report
Verdict Malicious
Is Solara V3. exe safe? No, we rate this exact file malicious.
Forty of the 71 antivirus engines that checked it flagged this executable, with a confirmed major hacking tool label, malware-specific YARA matches, and concerning runtime…
Read the whole reasonShow less
Strong evidence · Two or more major antivirus engines agree.
If you already ran it, follow the steps below.
What to do now4 steps
This file is harmful. Don't run it, and remove it.
If you haven't run it
Don't run this file. Delete it, then empty the Recycle Bin.
If you already ran it
Disconnect the device from the internet, then run a full antivirus scan. Microsoft Defender Offline (Windows Security > Virus & threat protection > Scan options) also finds malware that hides while Windows runs.
If you typed passwords on the device after running it, change them from another device you trust.
If the scan keeps finding it, or the device still acts strangely, scan again with a second-opinion scanner from another company; if that doesn't fix it, back up your personal files and reinstall Windows.
If you already ran it, do these in order.
If you opened or installed it
Avoid banking and sign-ins on that device until it is clean. These free MalwareTips guides walk you through it.
- Trojan removal guideClear steps for Windows, Mac and Android. (opens malwaretips.com in a new tab)
- Remove malware from WindowsStep-by-step cleanup with free tools. (opens malwaretips.com in a new tab)
- Ask for free help on the MalwareTips forumWindows malware removal help, answered by volunteers. (opens malwaretips.com in a new tab)
Paste this report's link in your topic so helpers can see what was found.
Antivirus results
40 of 71 flagged
- Flagged 40
- No detection 31
- No result 4
- Code signing CMD Softworks LLC
- Test run Completed
- First seen 1mo ago
Chapter 02
Why we think so
5 points against it and 5 in its favour, checked against the scan evidence.
The reasoning behind this verdict
The evidence strongly indicates an offensive or harmful executable: 40 of the 71 antivirus engines that checked it flagged it, and Ikarus supplied the major label PUA.Hacktools.CMDSoftWorks. Eleven malware-specific YARA rules, three offensive MITRE mappings, and four malicious signer-matched historical files provide substantial independent corroboration despite one clean sandbox run.
The detection volume is substantial, with 40 of the 71 antivirus engines that checked it flagging the sample and 31 independent engine votes after vendor relationships are collapsed. Ikarus identifies it as Hacktools.CMDSoftWorks, satisfying the confirmed-hacktool condition, while TrendMicro and several other engines identify trojan or Sbadur-related activity. The test run mapped possible process injection, data destruction, and impairment of defenses through T1055, T1485, and T1562.001, although no injected target process was recorded. Eleven malware-specific YARA rules add strong researcher-rule corroboration. The verified signature does not provide reassurance because all four historical samples from CMD Softworks LLC were malicious, matching four prior signer-linked decisions. A clean sandbox result and unrevealing host-reputation check are meaningful counterpoints, but they are outweighed by the combined engine, YARA, behavior, and signer-history evidence.
What We Detected
Forty of the 71 antivirus engines that checked it flagged the executable. The confirmed hacking tool label is reinforced by broad detection across 31 independent engine votes.
Threat Behavior
T1055 does not identify a target here because no injected process was recorded, but the three offensive mappings remain concerning in context. YARAify also matched 11 malware-specific rules, including grakate_stealer_nov_2021 and Rustyloader_mem_loose.
Trust and Counter-Evidence
The file carries a verified CMD Softworks LLC signature, but the available signer history contains four malicious samples and no benign ones. Four signer-matched historical files also received malicious decisions. One sandbox run returned clean, and all three observed network hosts were checked without known-malicious or suspicious reputation hits; neither result is sufficient to offset the broader corroboration.
What To Do Now
Do not run or distribute the executable.
Where this verdict could be wrong4 caveats
- The completed sandbox run returned clean, although a single run may not exercise conditional or user-triggered functionality.
- All three observed contacted hosts were inspected without a known-malicious or suspicious reputation match.
- The executable has a verified CMD Softworks LLC signature, but that signer has 4/4 malicious historical samples in the available record.
- The file is widely submitted and its code sections are not assessed as packed or unusually high-entropy.
These are the assessment's weak points. If you believe one applies to your file, report the verdict and we'll re-review it.
- The executable has a cryptographically verified code signature.
- One completed sandbox run did not issue a malicious verdict.
- The reputation check found no known-malicious or suspicious entries among all three observed contacted hosts.
- No confirmed malicious file it created was found, although ten dropped files lack saved verdicts.
- The executable is widely submitted and shows no indication of packed or unusually high-entropy code.
- Forty of the 71 antivirus engines that checked it reported a detection, including nine major antivirus engines.
- A major antivirus engine identified the program as a hacking tool associated with CMD Softworks.
- Eleven malware-specific researcher rules matched the file.
- All four historical samples signed by the same publisher were associated with harmful files.
- Four closely related, signer-matched files previously received malicious assessments.
6 sources checked · all complete. 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- 19sandbox rule tags
- 7spawned processes
- 3network contacts
- 37filesystem & 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: Ran commands or a script on the test computer.
Moderate concern: Checked whether it was running on a test computer.
Note: Read the user name of the test computer.
Note: Listed the programs running on the test computer.
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 recording keystrokes; no keylogging was confirmed.
Not confirmed: A sandbox rule tagged this run as weakening security settings; no setting change was recorded.
Not confirmed: A sandbox rule tagged this run as changing how Windows loads code; nothing confirms it.
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.
Threat context
How trojans work
A trojan pretends to be something useful or harmless so that you run it. Once open, it does its real job in the background, from stealing data to opening a back door or downloading more malware.
Bottom line:The disguise is the whole trick, so a trustworthy-looking name or icon means nothing.
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
SolaraV3.exe
4f0effff09207036720527d8d17fc0c3c630729f2acb6d510fdbe213fc48515d
Uploaded file
- 2
Processes
What ran
- Evidence 2 of 7: ProcessSeen in the test run
SolaraV3.exe
"C:\Users\<USER>\Desktop\SolaraV3.exe"
Test run - Evidence 3 of 7: ProcessSeen in the test run
msedgewebview2.exe
"C:\Program Files (x86)\Microsoft\EdgeWebView\Application\122.0.2365.92\msedgewebview2.exe" --embedded-browser-webview=1 --webview-exe-name=SolaraV3.exe --webview-exe-version=0.1.0 --user-data-dir="C:\Users\<USER>\AppData\Local\com.solara.v3\EBWebView" --noerrdialogs --embedded-browser-webview-dpi-awareness=2 --edge-webview-custom-scheme --autoplay-policy=no-user-gesture-required --disable-features=msWebOOUI,msPdfOOUI,msSmartScreenProtection --enable-features=MojoIpcz --lang=en-US --accept-lang=en-US --mojo-named-platform-channel-pipe=3064.3396.17639595820945998188
Test run - +1 more recorded observation
- 2
Files
Created or changed
- Evidence 4 of 7: Written fileSeen in the test run
UIDEBUG.txt
C:\Users\<USER>\Desktop\bin\UIDEBUG.txt
Test run - Evidence 5 of 7: Written fileSeen in the test run
.cookies
C:\Users\<USER>\AppData\Local\com.solara.v3\.cookies
Test run - +1 more recorded observation
- 2
Network
Hosts contacted
- Evidence 6 of 7: Contacted hostSeen in the test run
ocsps.ssl.com
Contacted during the test run.
Test run - Evidence 7 of 7: Contacted hostSeen in the test run
150.171.28.11
Contacted during the test run.
Test run - +1 more recorded observation
7 facts from the test run. See the full activity list.
Includes the sandbox verdicts, 19 mapped techniques, every process, file, registry and network entry and 5 dropped files.
Show the technical evidenceChapter 04
Technical details
40 of the 71 antivirus engines that checked it flag it; signed by CMD Softworks LLC.
Sources checked
Every check behind this verdict
6 sources checked · all complete. Complete means the check returned a usable result; it does not mean the file is safe.
Engines that flagged it 40
- Avast (major engine)Win64:MalwareX-gen [Misc]
- AVG (major engine)Win64:MalwareX-gen [Misc]
- Avira (major engine)TR/W64.Agent
- BitDefender (major engine)QD:Trojan.GenericKDQ.FB88E93FD2
- Emsisoft (major engine)QD:Trojan.GenericKDQ.FB88E93FD2 (B)
- ESET-NOD32 (major engine)Generik.IDUEZYD potentially unwanted application
- F-Secure (major engine)Trojan.TR/W64.Agent
- Fortinet (major engine)Riskware/Application
File fingerprint
- Last analyzed
- Oct 9, 2026, 7:59 PM UTC
- SHA-256
4f0effff09207036720527d8d17fc0c3c630729f2acb6d510fdbe213fc48515d- SHA-1
21a966098c142a1ae269b5ff585c708d890d0f04- MD5
084ba607d5cf148e3d0a85a028bab4ba
About this file
SolaraV3.exe is a Win32 EXE file of 19.7 MB.
- Type and size
- Win32 EXE · 19.7 MB
- Signer
- CMD Softworks LLCValid code signature.
- First seen
- Sep 16, 2026On VirusTotal.
- Submitted by
- 1,614 distinct sources
- Packer
- None detected
- Entropy
- 6.20 of 8
First scanned
Includes every engine result (75), 26 matched signature rules, PE section entropy and packers and how widely the file has been seen.
Show the technical evidenceChapter 05
Questions & answers
Short answers to the 9 questions people ask most about this file.
Is SolaraV3.exe malware?
What is SolaraV3.exe?
How many antivirus engines detected SolaraV3.exe?
I already downloaded and ran SolaraV3.exe — what should I do?
How do I remove SolaraV3.exe?
What kind of malware is SolaraV3.exe?
Is SolaraV3.exe digitally signed?
What is the SHA-256 hash of SolaraV3.exe?
How up to date is this analysis of SolaraV3.exe?
Community
Member reviews and reports for this exact file hash.