MalwareTips
Threat LensFile scan report

Is Resident Evil 3 v1.0-v20220613 Plus 20 Trainer.exe safe?

Verdict
Malicious

Thirty of 74 engines flagged this unsigned game trainer, with three independent tier-1 engines strongly agreeing on the GameHack family.

Thirty of 74 engines detected the executable, including five tier-1 detections and strong three-engine agreement on GameHack. Runtime analysis also recorded token manipulation, persistence, and defense-impairment techniques, so the file should not be run despite its established prevalence and lack of a sandbox malware verdict.

Do not run this file

Quarantine or delete the file and keep endpoint protection enabled. If it has already executed, run a full system scan and inspect persistence locations and recently written files.

Read the full analysis
Saved file evidenceAntivirus consensus
30of 74 flagged
Flagged 30No detection 44
Digital specimenResident Evil 3 v1.0-v20220613 Plus 20 Trainer.exe88a7ce087dc7f012fd…dd3384cadf1fdf
Size1.2 MB
Code signingUnsigned
SandboxRuntime complete
First seen4y ago
Evidence3 priority signals
30 of 74 antivirus engines flagged the file, including Antiy-AVL and Bkav.

Recommended next actions

01

Before running

Do not run it. Delete this file from the device, then empty the Recycle Bin or Trash.

02

If you already ran it

Disconnect from the internet, start a full or offline antivirus scan, then secure important accounts from a clean device.

Chapter 02

Intelligence

The saved assessment, checked against the scan evidence and recorded coverage.

MT AI Engine · Verdict analysis

The reasoning behind this verdict

This section explains the evidence supporting the verdict and keeps conflicting or missing signals visible.

92%Confidence
Very high
Analyst conclusion

Thirty of 74 engines detected the executable, including five tier-1 detections and strong three-engine agreement on GameHack. Runtime analysis also recorded token manipulation, persistence, and defense-impairment techniques, so the file should not be run despite its established prevalence and lack of a sandbox malware verdict.

Where this verdict could be wrong4 caveats
  • The sample is established rather than newly observed: prevalence records 485 sources and 577 submissions since 2022-06-22.
  • behaviour.hasMaliciousSandboxVerdict=false, and droppedChildren.hasMaliciousChild=false; however, all six children have unknown status.
  • externalIntel.yaraify.ruleCount=0, externalIntel.malwareBazaar.hit=false, and externalIntel.circl.hit=false.
  • contactedHosts.inspected=1 found no cached malicious or suspicious host, but this covers only one host despite numerous observed IP addresses and URLs.

These are the assessment's weak points. If you believe one applies to your file, report the verdict and we'll re-review it.

Recommended action

Quarantine or delete the file and keep endpoint protection enabled. If it has already executed, run a full system scan and inspect persistence locations and recently written files.

Scan transparency

Coverage & freshness

4 of 5 complete

Complete means the check returned a usable result. It does not mean the file is safe.

  • Antivirus

    Complete

    30 of 74 engines flagged the file.

  • Sandbox

    Complete

    1 isolated runtime environment contributed observations.

  • Network

    Partial

    1 of 21 contacted hosts were cross-checked; coverage is incomplete.

  • YARA

    Complete

    1 signature or behavior rule matched.

  • External intel

    Complete

    3 of 3 independent reference sources completed.

Chapter 03

Behavior

Plain-English impact first, then the observed runtime evidence.

Runtime flight recorder

Capture complete
  • 1isolated sandbox run
  • 19MITRE ATT&CK techniques
  • 9spawned processes
  • 24network contacts
  • 27filesystem & mutex artifacts

What this file does

Observed actions and their security significance

  • High concern: Changed an auto-start location that can make code run after sign-in or restart.

  • High concern: Attempted to impair or bypass security controls.

  • High concern: Manipulated how the operating system loads code, which can redirect execution.

  • Moderate concern: Contained obfuscated or packed code that makes inspection harder.

  • Moderate concern: Communicated over a common application protocol; malware can use this for command-and-control.

  • Moderate concern: Scans through your files and folders.

  • Moderate concern: Communicates over the network in a non-standard way.

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 bundlers & adware work

This is a bundler — a real-looking installer that hides extra software inside. When you run it, it quietly installs things you never asked for: ad injectors, browser toolbars, fake 'PC cleaner' apps, or even more bundlers. The people behind it get paid for every unwanted app they sneak on.

Bottom line:It's not usually built to destroy files, but it slows your PC, floods it with ads, and can be a real pain to fully remove.

Recorded behavior

Attack story

Runtime observations grouped by analysis stage. Arrows organize the stages; they do not claim chronology or causality.

ObservedDerived

7 recorded facts from one runtime window. Every fact remains independently traceable in Analyst mode.

Chapter 04

Detection & Forensics

Consensus, attribution, signatures, code structure, prevalence, and identity.

Chapter 05

Safety & 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.

  1. Recovery step 01

    Don't run this file. Delete this file from the device, then empty the Recycle Bin or Trash.

  2. 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.

  3. Recovery step 03

    If you typed any passwords while it was open, change them from a device you trust.

  4. 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.

8 evidence-based answers
Is Resident Evil 3 v1.0-v20220613 Plus 20 Trainer.exe a virus?
Evidence-based answer
Yes — Resident Evil 3 v1.0-v20220613 Plus 20 Trainer.exe is malicious. Do not run it. Delete this file from the device, then empty the Recycle Bin or Trash. 30 of 74 antivirus engines flag it (family: GameHack). It behaves as adware or a potentially unwanted program (PUA) — not always destructive, but it bundles ads, trackers, or unwanted changes you didn't ask for. If you've already run it, see the removal and recovery steps below.
What is Resident Evil 3 v1.0-v20220613 Plus 20 Trainer.exe?
Evidence-based answer
Resident Evil 3 v1.0-v20220613 Plus 20 Trainer.exe is a Windows executable program, about 1.2 MB. Our analysis identifies it as malicious (family: GameHack) — adware or a potentially unwanted program (PUA) — not always destructive, but it bundles ads, trackers, or unwanted changes you didn't ask for. Because a file's name and icon can be faked, the safest way to identify it is by its cryptographic hash (below), not its filename.
How many antivirus engines detected Resident Evil 3 v1.0-v20220613 Plus 20 Trainer.exe?
Evidence-based answer
30 of 74 antivirus engines flagged Resident Evil 3 v1.0-v20220613 Plus 20 Trainer.exe, 30 of them as outright malicious. The raw count alone does not establish safety or danger; we also weigh which engines flagged it and corroborating behavior, identity, reputation, and rule evidence. The malicious verdict comes from the complete saved evidence, not from this antivirus count by itself.
What should I do if I already ran Resident Evil 3 v1.0-v20220613 Plus 20 Trainer.exe?
Evidence-based answer
Act quickly. 1) Disconnect the device from the internet to stop the malware communicating or spreading. 2) Run a full scan with reputable anti-malware software (such as Malwarebytes) and quarantine everything it finds. 3) Change your important passwords from a DIFFERENT, clean device — many threats log keystrokes or steal saved credentials. 4) If you bank or shop on this device, watch closely for fraud and alert your bank. 5) For a confirmed infection, the most reliable fix is to back up your personal files and reinstall the operating system for a clean start.
How do I remove Resident Evil 3 v1.0-v20220613 Plus 20 Trainer.exe?
Evidence-based answer
To remove Resident Evil 3 v1.0-v20220613 Plus 20 Trainer.exe: 1) restart into Safe Mode (Safe Mode with Networking if you need to download a tool) so the malware doesn't auto-start. 2) Run a full scan with reputable anti-malware software and let it quarantine or delete the detections. 3) Delete this file from the device, then empty the Recycle Bin or Trash. 4) Check your browser extensions, startup items, and scheduled tasks for anything unfamiliar. 5) Reboot and scan again to confirm it's gone. If detections keep coming back, a clean operating-system reinstall is the most dependable cure.
What kind of malware is Resident Evil 3 v1.0-v20220613 Plus 20 Trainer.exe?
Evidence-based answer
Resident Evil 3 v1.0-v20220613 Plus 20 Trainer.exe is classified as adware or a potentially unwanted program (PUA) — not always destructive, but it bundles ads, trackers, or unwanted changes you didn't ask for. Engines attribute it to the GameHack family. Knowing the family matters because it tells you the likely impact — data theft, remote control, file encryption, or unwanted ads — and guides the cleanup.
What is the SHA-256 hash of Resident Evil 3 v1.0-v20220613 Plus 20 Trainer.exe?
Evidence-based answer
The SHA-256 hash of Resident Evil 3 v1.0-v20220613 Plus 20 Trainer.exe is 88a7ce087dc7f012fd1c9ff9f9713463161e91f1505afd82dedd3384cadf1fdf, and its MD5 is 87ff89ecb0eec5e8857eec6a3ce8b6ab. This hash is the file's unique fingerprint — two files with the same SHA-256 are identical. Use it to confirm you're looking at exactly this file (not just one with the same name) when comparing against antivirus databases or a download's published checksum.
How up to date is this analysis of Resident Evil 3 v1.0-v20220613 Plus 20 Trainer.exe?
Evidence-based answer
This report reflects the scan run on September 19, 2026. Because a file's hash never changes, the identity of Resident Evil 3 v1.0-v20220613 Plus 20 Trainer.exe is fixed — but antivirus coverage improves over time, so a file that looks clean today can pick up detections later (and vice-versa). If you need the latest picture, MalwareTips staff can re-run the analysis from scratch.
Chapter 06

Community

Member reviews and reports for this exact file hash.

Scan another
Check a different file
URL instead?
Check if a link is safe
The raw file is processed temporarily and is not retained after processing. Its hash and report are public and permanent, so the next person who checks the same file gets an instant answer. Unknown files may be submitted to VirusTotal for analysis. If you ran this file on your computer and are worried, scan your system with an up-to-date antivirus and change critical passwords from a different device.