File scan report
Verdict Malicious
Is Bloodstrike XT _ [RGE]_. exe safe? No, we rate this exact file malicious.
A game-cheating executable that eight major antivirus engines, including Microsoft and TrendMicro, detect as the Kepavll trojan or as a game hack.
Read the whole reasonShow less
Strong evidence · Two or more major antivirus engines agree.
Do not run this executable, and delete it if it is already on disk. If it has been launched, run a full antivirus scan, check startup entries and change passwords for accounts used on that machine.
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
23 of 71 flagged
- Flagged 23
- No detection 48
- No result 4
- Code signing Unsigned
- Test run Completed
- First seen 4mo ago
Chapter 02
Why we think so
6 points against it and 3 in its favour, checked against the scan evidence.
The reasoning behind this verdict
23 of the 71 antivirus engines that checked it flag this unsigned 64-bit Windows program, eight of them major antivirus engines such as Microsoft, TrendMicro, Sophos and Symantec. Microsoft and TrendMicro both name the Kepavll family, while ESET and Fortinet describe it as a game-hack / potentially unsafe application. Game cheats are routinely bundled with loaders and stealers, so it should not be run.
The file is an unsigned 1.8 MB 64-bit Windows executable that was first seen on Jul 5, 2026 and has been submitted from 53 distinct sources. Twenty-three of the 71 antivirus engines that checked it detect it, with eight detections coming from major antivirus engines, including Microsoft's Trojan:Win32/Kepavll!rfn and TrendMicro's Trojan.Win64.KEPAVLL.USBLI926; additional engines return generic high-confidence malware verdicts (Symantec ML.Attribute.HighConfidence, Sophos Mal/Generic-S, Elastic malicious (high confidence)). ESET and Fortinet describe the same code as a game-hack / potentially unsafe application, which fits the naming in the executable and the process names the sandbox recorded. There is no signature, no publisher history and no reference-database or community-rule hit either way, and the host-reputation check was not available for this file. The combined sandbox verdict was clean with no injection targets, no contacted domains and no dropped files; that is a real counter-signal, but cheating tools typically only act once a game client is running, and it does not outweigh eight independent major detections. The balance of the evidence supports treating this as malicious cheat-related malware rather than a benign utility.
What We Detected
This is a 64-bit Windows executable of about 1.8 MB, unsigned and without any publisher history. Twenty-three of the 71 antivirus engines that checked it flagged it, and 21 of those detections remain after collapsing engines that share one scanning core. Eight belong to major antivirus engines: Microsoft reports Trojan:Win32/Kepavll!rfn, TrendMicro reports Trojan.Win64.KEPAVLL.USBLI926, and Sophos, Symantec, Trellix, Ikarus, ESET and Fortinet all return malware or unwanted-application verdicts. Several machine-learning engines (Elastic, DeepInstinct, CrowdStrike) add high-confidence malicious scores.
The executable is not packed and its code sections show ordinary entropy, so the detections are not simply reacting to a wrapper or protector. No engine label attributes it to a well-known stealer or ransomware family; the shared name across Microsoft, TrendMicro and two other vendors is Kepavll, which antivirus vendors use for game-cheating and cheat-loader programs.
Threat Behavior
Four sandbox runs were completed and their combined verdict was clean: no process injection targets, no contacted web domains, no files dropped and no persistence keys written. The only network address recorded is the analysis environment's own background traffic, not the sample's. This kind of tool is built to attach to a running game and will often sit dormant when no game client is present, so an uneventful sandbox run is expected and is not evidence of safety.
ESET and Fortinet describe the code as a game hack / potentially unsafe application, which matches how the file presents itself. Cheat and hack builds traded through game forums are a common delivery route for loaders, information stealers and remote-access tooling, because users are already primed to run an unsigned executable and to grant it the privileges it asks for. The executable's own tags also indicate user-input checks and spreading behaviour rather than a plain offline hack.
What To Do Now
Do not run this program on a machine you care about. If it has already been executed, run a full scan with your current antivirus protection, review recently installed startup entries, and change passwords for any account you signed into on that machine, particularly game, e-mail and payment accounts. Keep security software enabled — cheats frequently instruct users to add exclusions, which removes the only layer that was catching this file.
Where this verdict could be wrong3 caveats
- The combined sandbox verdict was clean, with no process injection targets, no contacted domains and no dropped files — the runtime environment did not observe hostile behaviour, which is common for game-cheating tools that only act once a game is present.
- The contacted-host reputation check was not completed for this file, so the absence of hostile network activity in the sandbox is not confirmed by host reputation data.
- Two engines (ESET, Fortinet) describe it as a potentially unsafe game-hack application rather than a general trojan, which would place it closer to unwanted game-cheating software than to a full backdoor.
These are the assessment's weak points. If you believe one applies to your file, report the verdict and we'll re-review it.
- Four sandbox runs completed with a clean combined verdict, no injection targets and no dropped files.
- The executable is not packed and shows no high-entropy code sections or known wrappers.
- No reference-database or community YARA rule matches were returned for this hash.
- Eight major antivirus engines detect the file, including Microsoft and TrendMicro, who both name the Kepavll family.
- The program is unsigned and has no publisher history, so its origin cannot be verified.
- Two engines describe it as a game-hack / potentially unsafe application, a category routinely used to deliver loaders and stealers.
- Cheat executables are usually run with elevated trust by the user and are a common route for information-stealing payloads.
- Host reputation data for the addresses it may contact was not available, so network behaviour is not fully characterised.
- The file has been redistributed across dozens of sources, which is typical of cheat builds repackaged by third parties.
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 4 isolated tests; no test environment rated what it did as risky.
Test run summary
Capture complete- 4isolated sandbox runs
- 13sandbox rule tags
- 2spawned processes
- 0network contacts
- 2filesystem & 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).
Note: Listed the programs running on the test computer.
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).
Note: Loaded extra code modules while running.
Note: Checked which security software was installed on the test computer.
Sandbox labels we could not confirm (common in safe files too)
Not confirmed: A sandbox rule tagged this run as recording keystrokes; no keylogging was confirmed.
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 5: FileSeen in the test run
Bloodstrike XT _[RGE]_.exe
908950335e40ce00dafb7f1a37313868156935b181fa43a1edbd942d3e048f44
Uploaded file
- 2
Processes
What ran
- Evidence 2 of 5: ProcessSeen in the test run
Bloodstrike EXT Jinx9__unknowncheats.me__.exe
"C:\Users\<USER>\Desktop\Bloodstrike EXT Jinx9__unknowncheats.me__.exe"
Test run - Evidence 3 of 5: ProcessSeen in the test run
Bloodstrike EXT Jinx9_[unknowncheats.me]_.exe
"C:\Users\user\Desktop\Bloodstrike EXT Jinx9_[unknowncheats.me]_.exe"
Test run - +1 more recorded observation
- 2
Files
Created or changed
- Evidence 4 of 5: Written fileSeen in the test run
ConDrv
\Device\ConDrv
Test run - Evidence 5 of 5: Written fileSeen in the test run
Connect
\Device\ConDrv\\Connect
Test run - +1 more recorded observation
5 facts from the test run. See the full activity list.
Includes the sandbox verdicts, 13 mapped techniques and every process, file, registry and network entry.
Show the technical evidenceChapter 04
Technical details
23 of the 71 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 23
- ESET-NOD32 (major engine)Win64/GameHack_AGen.BYZ potentially unsafe application
- Fortinet (major engine)Adware/GameHack_AGen
- Ikarus (major engine)Trojan.W64.MalwareX
- Microsoft (major engine)Trojan:Win32/Kepavll!rfn
- Sophos (major engine)Mal/Generic-S
- Symantec (major engine)ML.Attribute.HighConfidence
- TrellixENS (major engine)Artemis!61F529E2F489
- TrendMicro (major engine)Trojan.Win64.KEPAVLL.USBLI926
File fingerprint
- Last analyzed
- Nov 6, 2026, 7:24 PM UTC
- SHA-256
908950335e40ce00dafb7f1a37313868156935b181fa43a1edbd942d3e048f44- SHA-1
2c08a5d5c0c0fada6681341dfa4047d2779caae2- MD5
61f529e2f489dcab7ed36335b4facb0f
About this file
Bloodstrike XT _[RGE]_.exe is a Win32 EXE file of 1.8 MB.
- Type and size
- Win32 EXE · 1.8 MB
- Signer
- UnsignedNo code signature.
- First seen
- Jul 5, 2026On VirusTotal.
- Submitted by
- 53 distinct sources
- Packer
- None detected
- Entropy
- 6.41 of 8
First scanned
Includes every engine result (75), 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 Bloodstrike XT _[RGE]_.exe malware?
What is Bloodstrike XT _[RGE]_.exe?
How many antivirus engines detected Bloodstrike XT _[RGE]_.exe?
I already downloaded and ran Bloodstrike XT _[RGE]_.exe — what should I do?
How do I remove Bloodstrike XT _[RGE]_.exe?
What kind of malware is Bloodstrike XT _[RGE]_.exe?
What is the SHA-256 hash of Bloodstrike XT _[RGE]_.exe?
How up to date is this analysis of Bloodstrike XT _[RGE]_.exe?
Community
Member reviews and reports for this exact file hash.