this post was submitted on 05 Aug 2023
425 points (96.9% liked)
Piracy: ꜱᴀɪʟ ᴛʜᴇ ʜɪɢʜ ꜱᴇᴀꜱ
54670 readers
409 users here now
⚓ Dedicated to the discussion of digital piracy, including ethical problems and legal advancements.
Rules • Full Version
1. Posts must be related to the discussion of digital piracy
2. Don't request invites, trade, sell, or self-promote
3. Don't request or link to specific pirated titles, including DMs
4. Don't submit low-quality posts, be entitled, or harass others
Loot, Pillage, & Plunder
📜 c/Piracy Wiki (Community Edition):
💰 Please help cover server costs.
 |
 |
|---|---|
| Ko-fi | Liberapay |
founded 1 year ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
I downloaded the RUNE release from TorrentLeech and Windows Defender found a trojan so yeah I'll believe it. I guess I'll wait for a FitGirls repack.
I've had false positives from cracks on TL before, several times. I respect your carefulness with a known problem with another release, though.
Torrent galaxy rune release. However not seeing any issues? Malwarebytes scans coming up clean. No integritycheck folder in app data. No hidden process running when game running. 🤷♂️?
From TL? Really? That's a surprise I didn't wanna hear! :/
Sadly even with private sites a lot of things are taken from a public source and you occasionally run into this problem. Like some people up their ratios on these sites by using their VPN to get the public torrent and then seeding it back to the private one.
As long as the first uploader didn't do it, then that won't cause other downloaders any issues. Torrents always verify the hash is correct and will discard bad data. And TorrentLeech has uploading torrents limited.
More than likely a false positive- they often show up as Trojans due to the payload. I saw a similar issue from the rune release off of my private tracker.
Now that's not something I'd have expected. I've never encountered anything like that in the nearly 15-20 years I've been using TL.
20? Interesting.
Just took a look at my profile, registered on 27 June 2006. So it's in my 15-20 year window that I mentioned