Alternatively, if there's a way to have qbit itself mark the download as "Failed" when it detects and refuses to download an executable, that would work too. I don't use qbit personally so I don't know if that's a thing it can be configured to do.
Just get into a decent general tracker and you'll literally never have this issue again (along with getting torrents with more seeders and better tagged content so your "4k" download will never be 480p again)
If you are too old for trackers, then just sign up for usenet. You will have to pay for it though.
TBF this isn’t a revival of some arch 90s thing, this is just how private trackers have been. What was the same in the aughts, for instance.
Why lol? Still better value than paying the IP holder what they want. And maintaining well curated torrent platforms costs money.
In practice, it's just adding an API key, setting a rule in the app to remove after x and then you can go back to ignoring it.
This can get stupid sometimes like when they're expecting everybody to keep over 1.0 when there are people with 10.0; but usually when they're doing that it's because it's a scammy tracker (all private trackers that you have to pay to join are scammy no exceptions) and they're trying to extort people who fall below 1.0 to give them money.
But expecting people to upload is part of the deal. That's not about being old, that's about being selfish. Non-scammy private trackers make it very easy, and some just concentrate on gatekeeping and don't worry about ratios at all.
Your basic point is very true, though. The way many private trackers have lasted is to stop letting people in almost entirely. To get into a non-scammy tracker you have to know somebody irl who is on and active, and they still might not be able to get you in. Or they will pretend like they can't - inviters sometimes get punished for the quality of the people they invite, and you think sharing back is something children do.
The whole sticky notes next to monitor is not a joke. I bet you could grab some crypto recovery keys this way
I find it funny that great minds think alike because I was just thinking of analysing these EXE files this week and doing a quick writeup at medium:
https://lazherrera.medium.com/analyzing-that-exe-file-youre-...
But usually I'm downloading TV on Linux not windows
And also, stop posting claudeslop. We know it’s claudeslop. You tried really hard to modify it and conceal it, but you can’t fool a sloprunner. So please, just write your own fucking article. It’s like 4 paragraphs long.
> you let it download
Sounds like a terrible strategy to me
No, that's to exhaust sandboxing without being able to trust sleep() or time API calls by the only way you can: generating heat.
I’m as upset as OP, get a job skid.
Scammers always have a new trick up their sleeve.
This is literally one of the advice points at the end of the article. Did you get that far?
Using settings on the indexer isn't great since with Prowlarr the user doesn't actually interact with the indexer portion of Sonarr.
Doing it in release profiles by bumping down their score is a cute workaround but then the torrents will just stop saying ".exe" in their title.
Really it's a thing Sonarr have to do, as evidenced by the multiple PRs they have to try and finally do it.
let's all join a private tracker!
that'll fix the problem, the bad actors won't chase the crowd, and it definitely wont end in a burning of the library of alexandria loss-of-history what.cd style event again and again if the public can't archive it.
/s
how about we just create an exe/bat/com exclusion on our dumb-as-dick media downloaders like sensible people have been doing for 30+ years?
I don’t agree with that framing.
All metadata has been preserved and published, and the sucessor sites to what.CD have long outgrown it; and their successors will again. Anything you find missing, you can request and typically it will be filled within less than 24 hours.
And i also truly cannot understand what your point is. Trackers are not really legal, they come and go. I don't think a few hundred or even a few thousand HN users joining across the ecosystem is going to suddenly cause them all to get raided
The ability to change it, dude. Have you never written a malware before?
Often a primary concern is the security response, so you want redundancy for the ability to work around enforcement action, such as website takedowns.
Hardcoding a scapegoat into the malware itself also buys you time, so that the first enforcement action is less likely to spend your backups right away.
> And to whoever made this: you probably spent weeks or shit ton of tokens on ChaCha20, AES-CTR, runtime API hashing, anti sandbox scoring, Chrome app bound encryption bypasses, just to make a shitty skid malware.
People have been making infostealers that support hundreds or thousands of different apps and corners of your computer for decades. Plenty of vendors pride themselves on it.
Meanwhile you used LLM to write a bunch of your article, and seemingly to do the RE too...
Now you need 9 different pieces of software that end in *arr, all of which implement parts of the solution that you want and parts that you don't, and none of them is even a torrent client!
And they don't even work with torrent sites reliably, so people then spend money on a Usenet subscription like it's 1990 again.
You can also automate 99% of it with the *arr stack and completely forget about it.
What is the issue? There is more choice now?
Any all-in-one solution is going to be considered illegal at face value if it is obviously designed to circumvent copyright.
But if you split all the pieces of the solution up into separate pieces of software that can't do much illegal by themselves, you can always claim plausible deniability as the maintainer.
After all, you aren't going to be downloading torrents with Sonarr, you aren't going to be looking up information about shows with Jackett, and you aren't going to be automating your downloads with qBittorrent. If you link them all together with APIs, though, they do everything automatically.
As for the issue demonstrated here, it's just a long-standing problem in Sonarr and Radarr that even when it detects that a torrent is bad, it just sits there holding onto a virus until you override it with a working torrent, instead of just dumping the bad data and trying again.