File scan report
Verdict Malicious
Is Zsrekgoixr. exe safe? No, we rate this exact file malicious.
48 of the 68 antivirus engines that checked it flag this Windows program as a malware downloader.
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.
Reads the latest antivirus results for this file's hash. Nothing is uploaded.
Antivirus results
48 of 68 flagged
- Flagged 48
- No detection 20
- No result 6
- Code signing Unsigned
- Test run Completed
- First seen 3mo ago
Chapter 02
Why we think so
5 points against it and 3 in its favour, checked against the scan evidence.
The reasoning behind this verdict
This file is a confirmed dropper malware. Four major antivirus engines (Avast, AVG, Avira, DrWeb) converge on the MalwareX family, and 16 of 17 major antivirus engines flag it malicious. The combination of packing, unsigned status, and offensive MITRE techniques forms a classic dropper profile.
The evidence overwhelmingly indicates malware. The major family consensus on MalwareX is decisive: four major antivirus engines independently named the same family, and 16 of 17 major antivirus engines flagged the sample malicious. The file is unsigned and rare (9 days old, 3 submitters), eliminating any legitimate-publisher defence. The triggered rules (four of our behaviour rules) form a coherent dropper/stager attack chain. The absence of external YARA/CIRCL corroboration does not override major consensus; antivirus engines are authoritative. This is malware.
What We Detected
Four major antivirus engines (Avast, AVG, Avira, DrWeb) converge on the MalwareX family. The file is unsigned, packed (high-entropy .text section), and rare (first seen on Jul 2, 2026).
Threat Behavior
(3) Direct-IP a control server (T1620) — the malware contacts external IP 1.1.1.1 directly, bypassing DNS reputation systems and domain-based blocklists. (4) Packing + Unsigned — the combination of high-entropy code and unsigned status is a classic malware-dropper pattern: packing obfuscates the payload until runtime, and lack of signing eliminates publisher accountability.
What To Do Now
Do not execute this file. Remove it immediately if present on your system. If execution occurred, assume credential compromise and change passwords for all accounts used on that machine. Scan the system with a full antivirus sweep and monitor for lateral movement or data exfiltration. Check network logs for outbound connections to 1.1.1.1 or other suspicious IPs.
Where this verdict could be wrong3 caveats
- No dropped file is known to be malicious — none of the 6 files it created have been rated malicious yet; however, this reflects incomplete analysis of child hashes, not evidence of benign behaviour. The dropper pattern itself is malicious regardless of child verdicts.
- similarHashes shows 5 prior 'suspicious' verdicts on files built with the same import table — but these are framework-collision matches (same packer, different payloads/signers). Matches on the import table alone do not override major consensus on the current sample.
- externalIntel (CIRCL, MalwareBazaar, YARAify) returned no hits — absence of external corroboration is not evidence of safety; major antivirus engines are themselves authoritative and sufficient.
These are the assessment's weak points. If you believe one applies to your file, report the verdict and we'll re-review it.
- No malicious files it created confirmed (6 inspected, verdicts pending)
- No contacted domains — only direct IP (suggests a control server hardcoding, not dynamic DNS)
- No persistence indicators detected in sandbox (no registry keys, no scheduled tasks created)
- Major family consensus (MalwareX) across 4 major antivirus engines
- Direct-IP control-server communication bypassing DNS reputation
- Packed, unsigned executable with high-entropy code
- Rare file (9 days old, 3 submitters) — no established legitimacy
- Coherent dropper/stager attack chain (inject → steal → beacon)
6 sources checked · 5 complete · 1 not needed or not applicable. 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- 16sandbox rule tags
- 6spawned processes
- 0network contacts
- 19filesystem & 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: Unpacked hidden content while it ran.
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: Read basic details of the test computer, such as its Windows version.
Note: Looked through folders on the test computer (most installers do this).
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.
Not confirmed: A sandbox rule tagged this run as changing how Windows loads code; nothing confirms it.
Not confirmed: A sandbox rule tagged this run as loading code in memory; 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 downloaders work
This file is a delivery vehicle. On its own it can look small and harmless, but its job is to fetch and install the real payload, often a password stealer, ransomware or a bot, from a server the attacker controls.
Bottom line:Because the dangerous part arrives later, early scans can look cleaner than the threat really is.
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 5: FileSeen in the test run
Zsrekgoixr.exe
2b8e3ad0512cbadeb82a581dea4b35a05dd46fa5af0447fd25f69d8144865bce
Uploaded file
- 2
Processes
What ran
- Evidence 2 of 5: ProcessSeen in the test run
executable.exe
"C:\Users\<USER>\Desktop\executable.exe"
Test run - Evidence 3 of 5: ProcessSeen in the test run
taskhostw.exe
%WINDIR%\system32\taskhostw.exe
Test run - +1 more recorded observation
- 2
Files
Created or changed
- Evidence 4 of 5: Written fileSeen in the test run
executable.exe.log
C:\Users\<USER>\AppData\Local\Microsoft\CLR_v4.0_32\UsageLogs\executable.exe.log
Test run - Evidence 5 of 5: Written fileSeen in the test run
.exe
%LOCALAPPDATA%\rhtsu\.exe
Test run - +1 more recorded observation
5 facts from the test run. See the full activity list.
Includes 16 mapped techniques, every process, file, registry and network entry and 5 dropped files.
Show the technical evidenceChapter 04
Technical details
48 of the 68 antivirus engines that checked it flag it; no publisher signature.
Sources checked
Every check behind this verdict
6 sources checked · 5 complete · 1 not needed or not applicable. Complete means the check returned a usable result; it does not mean the file is safe.
Engines that flagged it 48
- Avast (major engine)Win32:MalwareX-gen [Drp]
- AVG (major engine)Win32:MalwareX-gen [Drp]
- Avira (major engine)DR/W32.MalwareX
- BitDefender (major engine)Gen:Heur.MSIL.Benin.5
- DrWeb (major engine)Trojan.MulDrop38.49420
- Emsisoft (major engine)Gen:Heur.MSIL.Benin.5 (B)
- ESET-NOD32 (major engine)MSIL/Kryptik.APRJ trojan
- F-Secure (major engine)Dropper.DR/W32.MalwareX
File fingerprint
- Last analyzed
- Jul 11, 2026, 5:20 PM UTC
- SHA-256
2b8e3ad0512cbadeb82a581dea4b35a05dd46fa5af0447fd25f69d8144865bce- SHA-1
9539efa1877cf8d4b355bb7f2670a5a190e83609- MD5
b8648e3534d1c5a86a15ae017d735c09
About this file
Zsrekgoixr.exe is a Win32 EXE file of 660.5 kB.
- Type and size
- Win32 EXE · 660.5 kB
- Signer
- UnsignedNo code signature.
- First seen
- Jul 2, 2026On VirusTotal.
- Submitted by
- 3 distinct sourcesRarely seen: few people have submitted this exact file.
- Packer
- None detected
- Entropy
- 7.20 of 8
First scanned
Includes every engine result (74), 1 matched signature rule, PE section entropy and packers and how widely the file has been seen.
Show the technical evidenceChapter 05
Questions & answers
Short answers to the 8 questions people ask most about this file.
Is Zsrekgoixr.exe malware?
What is Zsrekgoixr.exe?
How many antivirus engines detected Zsrekgoixr.exe?
I already downloaded and ran Zsrekgoixr.exe — what should I do?
How do I remove Zsrekgoixr.exe?
What kind of malware is Zsrekgoixr.exe?
What is the SHA-256 hash of Zsrekgoixr.exe?
How up to date is this analysis of Zsrekgoixr.exe?
Community
Member reviews and reports for this exact file hash.