SAFETY ALERTS / CHECK BEFORE ALLOWINGRelease reference · v2.1.4

Is ReSkate Safe? Understand Trojan Alerts Before You Run It

ReSkate has triggered antivirus alerts in user reports. Project contributors have described some historical detections as false positives, but that does not verify every release or mod. Before allowing a flagged file, check the exact alert, affected file and release information.

Updated · Guidance reviewed Download & installation guide
START HERE

Is ReSkate safe? The short answer

An antivirus alert alone does not establish that ReSkate is malware. A project explanation alone does not certify your download as safe. ReSkate’s source is public under GPL-3.0, but the client, third-party mods and your account each raise different questions.

Start with the file named in your alert. Identify its version, review the report and compare it with the corresponding release asset. If the source is uncertain, a hash differs or the warning remains unexplained, leave the file blocked. For download locations and installation, use our full ReSkate download and install guide.

Is ReSkate a virus?

ReSkate itself is not a virus. It is a community client that modifies game memory and injects a DLL into the game process. Unsigned executables and these behaviors can trigger heuristic engines that assess activity rather than a confirmed malware signature.

Players searching for "is ReSkate a virus" and "ReSkate virus detected" are usually looking at the same false positive. That describes the historical false-positive reports discussed here, not a verdict on every file using the ReSkate name. An altered download or third-party mod still needs its own assessment. Follow How to check the file behind an antivirus alert before allowing a warning.

Why does my antivirus flag ReSkate as a Trojan?

The launcher source loads ReSkate’s DLL into the game using process injection. Microsoft monitors cross-process injection among other behaviors. That overlap is a possible explanation, not proof of what triggered your alert. The same alert is sometimes described as a virus rather than a Trojan — the wording depends on which engine flags it.

What players reported and how the project responded

These are historical reports, not a scan of the current release. The detection labels come from users; explanations are attributed to their authors. We have not independently reproduced or verified these detections.

Selected ReSkate antivirus reports and project responses
Report date / versionReported detectionResponse and evidence

v1.0.3
Trojan:Win32/Sabsik.EN.A!ml
Read the user report
zeex64 described this historical report as a false positive and suggested an exclusion.
Read the project response

Not specified in the detection comment
Behavior:Win32/DefenseEvasion.A!ml
Read the user report
User report. The exact label is recorded; the comment does not establish its cause.

v1.1.1 discussed in the response
Trojan:Win32/Wacatac.B!ml
Read the user report
Project contributor VexFlint described the historical alert as a false positive and explained the launcher’s injection behavior.
Read the project response

Not independently verified: a contributor’s false-positive assessment applies to the case discussed. It does not verify later releases, repackaged downloads or mods. An issue being closed is not a malware-safety certificate.

What does “!ml” mean in these reports?

Microsoft lists the Behavior:Win32/DefenseEvasion.*!ml pattern under behavior-based machine learning. Its general naming guide describes ! suffixes as internal indicators. The detection method does not tell you to ignore the warning.

Copy the entire label from your own alert. A player calling something a “Trojan” does not identify which file was checked or which detection you received. Do not assume your warning is the same as an older report.

Why do some tools call it a virus?

Vendors can label the same unsigned file Trojan, Virus or PUA; different names can refer to the same file rather than separate incidents. Compare file hashes before treating two reports as the same case.

How to check the file behind an antivirus alert

  1. Record the affected file. Distinguish the archive, ReSkateLauncher.exe, ReSkate.dll and a third-party mod. They are different files with different hashes.
  2. Check the source and version. Use the project’s release record, not a mirror, repackaged installer or a “fixed” DLL offered in a comment. A familiar filename is not proof of origin.
  3. Compare the correct asset’s SHA-256. Use the current version’s asset names and publisher checksums. For an older file, use its own release record.

For the client archive in our release reference, ReSkate-2.1.4.zip, run this PowerShell command from the folder containing that file:

Get-FileHash -Algorithm SHA256 -LiteralPath ".\ReSkate-2.1.4.zip"

Compare every character with the digest in the v2.1.4 asset listing; letter case does not matter. GitHub computes release asset digests at upload. The ZIP’s checksum cannot verify an extracted EXE or DLL.

A mismatch means stop. A match establishes consistency with the referenced asset, not that it is harmless. If the file is quarantined or its digest is unavailable, do not restore it solely to complete this check.

Public source and matching asset hashes are also different from proof that a binary was built from that source. Issue #32 requests CI builds and attestations; the request itself is not evidence that a particular release has those proofs.

What to do when ReSkate is blocked, quarantined or removed

Windows Defender quarantined or removed a file

Open Windows Security → Virus & threat protection → Protection history. Expand the relevant event and record the detection name, affected item and time. Microsoft’s Protection History guide explains the event types and available actions.

A quarantined file is blocked from running. A removed file is no longer present. Leave uncertain files quarantined. Restore puts a quarantined file back; it does not clear the safety concern, and Defender may detect it again. Only consider restoring after investigating the alert and deciding you trust that specific file.

The launcher disappeared or cannot read a file

Issue #71 reports the launcher disappearing after crashes. Issue #25 records Cannot open file for SHA-256. Neither report alone establishes that antivirus caused the failure.

Look for a matching security event before changing protection settings. A file that cannot be opened has not necessarily failed a hash comparison. If there is no matching event, report the exact launcher error instead of adding an exclusion as a general fix.

Your browser blocked the download

Players reported browser warnings in Brave (#27) and Opera (#59). Save the wording and identify whether the browser or antivirus produced it. Verify the destination against the project release record; do not switch to an unknown mirror or turn off browser protection to force the download.

Smart App Control blocked the launcher

Issue #180 reports an unknown-publisher block. Smart App Control is separate from Defender antivirus. Microsoft says it has no per-app bypass; a Defender file exclusion is not its equivalent. Ask the project about signing or wait for clarification rather than disabling a broader protection as an installation step.

When to consider a Windows Defender exclusion

An antivirus whitelist or exclusion changes protection; it is not a safety check. First establish the file’s source, compare the corresponding digest where available and investigate the exact alert. A matching hash alone is not a reason to allow it. If uncertainty remains, keep it blocked.

Add a specific file exclusion

If you trust the reviewed file and accept the remaining risk:

  1. Open Windows Security → Virus & threat protection → Manage settings.
  2. Under Exclusions, select Add or remove exclusions.
  3. Select Add an exclusion → File and choose the exact file you reviewed.

Follow Microsoft’s exclusion instructions. Avoid excluding your whole Steam library, Downloads folder, drive or every file with a particular extension. A folder exclusion covers its contents, including future changes. Do not disable Defender across the computer.

Allow on device is a different action

Protection History’s Allow on device permits a detected threat. Exclusions change what Defender checks. Neither action verifies the file; neither should be the default response to an unexplained warning.

Remove the exception and review it after updates

To undo a file exclusion, return to Add or remove exclusions, select it and choose Remove. To undo an allowed threat, open Virus & threat protection → Allowed threats, select it and choose Don’t allow.

A replaced file at an excluded path still needs review. Check the new release’s file and alert again. Defender settings do not control a separate antivirus product; use that vendor’s instructions if it issued the warning.

How to interpret ReSkate VirusTotal results

Issue #136 contains a user report for v1.1.8: the launcher was flagged by a small number of engines, and the DLL had a different detection. At our review date, the reply was another player’s reassurance, not a project contributor’s file-specific verification.

VirusTotal aggregates vendors’ results and does not produce its own verdict. One detection is not proof of malware or a false positive; zero detections are not a guarantee. Different files, versions and scan times cannot be treated as one result.

When reading a report, check its SHA-256, filename and scan date against the file in your alert. Read the individual detection details and any substantiated project response. A report for an older launcher does not assess today’s DLL or your installed mods.

What are the privacy and account risks?

Steam login and claims about keylogging

The project README documents Steam authentication when required game files need downloading, including Steam app scanning or credentials with Steam Guard. That explains why a login prompt can appear; it does not independently audit how a binary handles credentials.

The project says logs never contain your Steam password or login name. That is a statement about logs, not proof that every executable or mod is free of keylogging. Do not enter credentials on a download website, send Steam Guard codes to a helper, or trust an unknown launcher just because it shows a familiar login screen.

Crash reports and how to turn them off

When ReSkate crashes, it uploads a minidump and that session's log to the project's Backtrace account to help fix problems. Logs never contain your Steam password or login name. This is the project’s documented policy, not an independent binary audit.

To opt out, untick Send crash reports at Launcher Settings → ADVANCED, or set RESKATE_CRASH_REPORTING=0. Before posting a log or dump publicly, check it for information you do not want to share.

Mods, lobby rules and account bans

A malware scan does not settle account risk. EA’s terms still apply, and the project has a multiplayer ban list; neither provides immunity from bans. ReSkate is a fan project with no affiliation or endorsement from Electronic Arts or Full Circle.

Only install mods from authors you trust. Custom scripts can execute code, and a client checksum does not verify third-party packages. Check author requirements in our ReSkate mod catalogue; a listing is not a safety review.

Frequently asked questions

Does “!ml” mean the alert is a false positive?

No. Microsoft documents the reported DefenseEvasion !ml pattern under behavior-based machine learning. A detection method is not a safety verdict. Investigate the actual file and alert before deciding whether to allow it.

Read the detection-name explanation
Does a matching SHA-256 mean the file is safe?

It means the file matches the referenced release asset, provided the expected digest comes from a trusted source. It does not prove that the asset is harmless or that the released executable matches the public source code.

Read the file verification steps
Why does Defender flag ReSkate again after an update?

An update changes the files being checked. A previous scan or exclusion does not verify the replacement. Record the new detection name, check the affected file against its own release information, and review any existing exclusion.

Review exclusions after an update
Should I exclude my whole Steam library?

No. That would reduce protection for unrelated games, tools and future downloads. If you decide to make an exclusion after investigating the alert, keep its scope to the specific file you reviewed and remove it when no longer needed.

Check the scope of an exclusion
Can I trust a VirusTotal result with only one detection?

One detection is neither proof of malware nor proof of a false positive. VirusTotal aggregates vendor results. Check the exact file hash, scan date and detection details; a result for an older release does not verify your current file.

Read the VirusTotal guidance
What should I include when reporting an antivirus alert?

Include the ReSkate version, affected filename, full detection name, antivirus product, detection time, source link and a screenshot. Include a file hash if available. Never post passwords, Steam Guard codes, or logs and dumps you have not checked for sensitive information.

Open the project issue tracker
Is ReSkate a virus?

No. ReSkate is an unsigned community client, so some antivirus engines flag it heuristically. See "Is ReSkate a virus?" above for details, and check the file yourself with the steps on this page.

Sources and review notes

Security guidance and selected issue comments were reviewed on . The release reference comes from the v2.1.4 release, with asset data checked on . A newer release reference does not mean its safety has been independently verified.

We have not run or independently audited these binaries, reproduced the reported alerts, or confirmed a false positive ourselves. For a new report, include the details listed in the FAQ and use the project issue tracker. See our source policy and contact details.