Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Unable to work on Windows 11 due to detected trojan virus #48

Open
Nytra opened this issue Dec 17, 2023 · 6 comments
Open

Unable to work on Windows 11 due to detected trojan virus #48

Nytra opened this issue Dec 17, 2023 · 6 comments
Labels
blocked Blocked by another issue other Doesn't quite fit into other labels

Comments

@Nytra
Copy link

Nytra commented Dec 17, 2023

Screenshot 2023-12-17 021544 edit

Trojan:Script/Wacatac.B!ml

@Gawdl3y
Copy link
Owner

Gawdl3y commented Dec 17, 2023

It's not a Trojan. If I were to guess, Defender sometimes identifies it as such due to the self-updating functionality. What's more frustrating is that it only sometimes screams about it, not consistently. You may just need to whitelist it.
Hopefully, as more people download it and Microsoft picks up on its existence via the usual telemetry, this problem will go away. I'm also going to submit it as a false positive on Microsoft's site, although who knows how effective that will be!

This problem will likely come and go until MS and other vendors see Tauri apps more frequently. The only permanent fix in the meantime is probably to sign the executable using an EV code signing certificate... but that costs hundreds of dollars per year to maintain, which is not an investment I can feasibly make at the moment.

See tauri-apps/tauri#2486

@Gawdl3y
Copy link
Owner

Gawdl3y commented Dec 17, 2023

Funnily enough, it seems nothing improperly flags the MSI version of the installer with anything, according to a VirusTotal scan - so if you'd rather not whitelist anything, you can give that a shot.

Also on the subject of VirusTotal, according to the scan on the EXE installer, nothing is detected in behavioural analysis. It's purely some signature-based AV that is being tripped.

@Gawdl3y Gawdl3y added blocked Blocked by another issue other Doesn't quite fit into other labels labels Dec 17, 2023
@Gawdl3y
Copy link
Owner

Gawdl3y commented Dec 17, 2023

I just released v0.4.0 and scanned both the installer and the installed EXE manually with Defender, but it didn't report anything this time around. Dunno if it's just a fluke or if it's actually okay with this version, but I didn't make any relevant changes.

@Nytra
Copy link
Author

Nytra commented Dec 17, 2023

I tried the EXE installer for v0.4.1 and it worked and didn't warn me about a trojan. So maybe this issue can be closed? Although the problem may still crop up again in future releases.

@liny-fox
Copy link

liny-fox commented Jan 25, 2024

release 0.7.1 reported with this variant:
image
Interestingly, VT doesnt flag it on microsoft, but flags the installer on 2 other things, and the EXE on only one of them.

@XDelta
Copy link

XDelta commented Feb 25, 2024

Most recent 0.8.0 still appears to have this issue for some. According to VirusTotal, it is still being flagged by one vendor along with matching a yara rule on

"https://raw.githubusercontent.com/resonite-modding-group/resonite-mod-manifest/main/manifest.json";

aa7433c7ae

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
blocked Blocked by another issue other Doesn't quite fit into other labels
Projects
None yet
Development

No branches or pull requests

4 participants