Is Zsrekgoixr.exe safe?
Malicious file assessment
2 high-confidence signature or behavior rules matched this file.
2b8e3ad0512cbadeb8…f69d8144865bceRecommended next actions
Before running
Do not run it. Delete this file from the device, then empty the Recycle Bin or Trash.
If you already ran it
Disconnect from the internet, start a full or offline antivirus scan, then secure important accounts from a clean device.
Intelligence
The saved assessment, checked against the scan evidence and recorded coverage.
No saved analyst narrative
This report keeps the verified scan facts available below without inventing an analysis that was not saved with the scan.
Coverage & freshness
Complete means the check returned a usable result. It does not mean the file is safe.
Antivirus
Complete48 of 74 engines flagged the file.
Sandbox
Complete1 isolated runtime environment contributed observations.
Network
Partial1 runtime contact was observed without a completed reputation cross-check.
YARA
Complete5 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
- 16MITRE ATT&CK techniques
- 15spawned processes
- 1network contacts
- 19filesystem & 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.
High concern: Manipulated how the operating system loads code, which can redirect execution.
High concern: Loaded code directly into memory instead of from a normal file.
Moderate concern: Contained obfuscated or packed code that makes inspection harder.
Moderate concern: Runs hidden system commands (script or shell).
Moderate concern: Removed execution artefacts or logs, which can conceal activity.
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.
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 quietly pull down and install the REAL payload — often a stealer, ransomware, or 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.
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
Zsrekgoixr.exe
2b8e3ad0512cbadeb82a581dea4b35a05dd46fa5af0447fd25f69d8144865bce
01Uploaded file
Processes
Runtime execution
- ProcessObserved
Observed process
"C:\Users\<USER>\Desktop\executable.exe"
02Isolated runtime analysis - ProcessObserved
Observed process
C:\Windows\system32\services.exe
03Isolated runtime analysis - +1 more recorded observation in Analyst mode
Files
Created or changed
- Written fileObserved
executable.exe.log
C:\Users\<USER>\AppData\Local\Microsoft\CLR_v4.0_32\UsageLogs\executable.exe.log
04Isolated runtime analysis - Written fileObserved
.exe
%LOCALAPPDATA%\rhtsu\.exe
05Isolated runtime analysis - +1 more recorded observation in Analyst mode
Network
Hosts contacted
- Contacted hostObserved
1.1.1.1
Contact observed during runtime.
06Isolated runtime analysis
6 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.
- 1.1.1.1
- C:\Users\<USER>\AppData\Local\Microsoft\CLR_v4.0_32\UsageLogs\executable.exe.log
- %LOCALAPPDATA%\rhtsu\.exe
- %LOCALAPPDATA%\microsoft\clr_v4.0_32\usagelogs\kfagitaa.exe.log
- %TEMP%\121cfa60cfcc465fbb99bffde12e26b8.xml
- %WINDIR%\system32\tasks\{0d7e4a0e-6770-495a-921b-8dc6ef4ab8b7}
- %TEMP%\121cfa60cfcc465fbb99bffde12e26b8.xml
- C:\Users\Administrator\AppData\Local\Temp\b38addfe16f048ffbead62583e8212db.xml
- C:\Users\Administrator\AppData\Local\Temp\1926e096c5584b4a9d61a903ac413152.xml
- b07a471d77cfe06cdec2d3542b45b8ea
- Global\OneSettingQueryMutex+compat+encapsulation
- \Sessions\1\BaseNamedObjects\b07a471d77cfe06cdec2d3542b45b8ea
Files this sample writes at runtime
This file drops 6 children at runtime. None are currently flagged malicious in our cache.
- d7a5b6d946ca6ba653ad…f22874Never scannednever seen before
- b10a9f2baf223d3dc2fb…43f96aNever scannednever seen before
- 2b8e3ad0512cbadeb82a…865bceNever scannednever seen before
- 7bcae8abc905e7629e95…4e8c2fNever scannednever seen before
- f951aa9b987258a81301…beeac5Never scannednever seen before
- 40119b5a200e7bfd8688…8977f9Never 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.
- 5rule hits recorded
- 48 / 74engines flagged
- 3sources in submission history
Why these facts are shown
Each statement identifies whether it was directly recorded or derived from saved scan facts.
- 01
2 high-confidence signature or behavior rules matched this file.
Verdict inputView chapterProvenanceDerivedSourceSignature and behavior rulesObserved at - 02
48 of 74 antivirus engines flagged the file, including Alibaba and alibabacloud.
Verdict inputView chapterProvenanceObservedSourceAntivirus analysisObserved at - 03
The hash has been submitted 3 times from 3 sources.
ProvenanceDerivedSourceSaved report factsObserved at - 04
Scanned file: Zsrekgoixr.exe — 2b8e3ad0512cbadeb82a581dea4b35a05dd46fa5af0447fd25f69d8144865bce
ProvenanceObservedSourceUploaded fileObserved at - 05
Observed process — "C:\Users\<USER>\Desktop\executable.exe"
ProvenanceObservedSourceIsolated runtime analysisObserved at - 06
Observed process — C:\Windows\system32\services.exe
ProvenanceObservedSourceIsolated runtime analysisObserved at - 07
File written: executable.exe.log — C:\Users\<USER>\AppData\Local\Microsoft\CLR_v4.0_32\UsageLogs\executable.exe.log
ProvenanceObservedSourceIsolated runtime analysisObserved at - 08
File written: .exe — %LOCALAPPDATA%\rhtsu\.exe
ProvenanceObservedSourceIsolated runtime analysisObserved at - 09
Contacted host: 1.1.1.1 — Contact observed during runtime.
ProvenanceObservedSourceIsolated runtime analysisObserved at
Detection sources at a glance
Category: downloader
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.
MITRE T1055 (Process Injection) observed — CreateRemoteThread / APC / reflective-DLL injection. The payload is being smuggled into a legitimate process to bypass AV hooks.
EvidenceC:\Windows\System32\svchost.exe -k NetworkService -pPE is packed (high-entropy code or known packer) AND unsigned AND at least one engine flagged it. Packing alone is common in legit software; packing + unsigned + signal is the malware-dropper pattern.
Evidencehigh-entropy code sectionSandbox 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.
Evidence1.1.1.1Unsigned, packed PE with sandbox-observed network activity. The packing step hides the payload until execution; the network call fetches / reports for the next stage. Classic dropper / stager behaviour.
Evidence1.1.1.1
48 of 74 engines flagged this file
View all 74 engine results
Section entropy & packers
Executable sections have high entropy (7.2+) — the code is compressed or encrypted and only decrypted at runtime. Classic packing behaviour.
How widely this file has been seen
Barely seen in the wild and first surfaced recently. 48 antivirus detections make that low prevalence materially relevant, but rarity alone is not proof of malware.
Fingerprint and provenance
- File name
- Zsrekgoixr.exe
- Format
- Win32 EXE
- Code signing
- No verified publisher
- Size
- 645.0 KB
- Last analyzed
- Jul 11, 2026, 5:20 PM UTC
2b8e3ad0512cbadeb82a581dea4b35a05dd46fa5af0447fd25f69d8144865bceSafety & FAQ
Complete recovery guidance and answers for the next decision.
What to do now
This file is dangerous. Treat it as harmful and remove it.
- Recovery step 01
Don't run this file. Delete this file from the device, then empty the Recycle Bin or Trash.
- Recovery step 02
If you already ran it, disconnect from the internet and start with a full antivirus scan or Microsoft Defender Offline scan. If compromise is suspected or the problem persists, use a reputable second-opinion scanner and follow incident-recovery or clean-reinstall guidance.
- Recovery step 03
If you typed any passwords while it was open, change them from a device you trust.
- Recovery step 04
Get a fresh copy from the developer's official site or an official app store.
Safety FAQ
Direct answers grounded in the saved verdict and evidence in this report.
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.