When Your 'Linux ISOs' Turn Out to Be .exe Files: Anatomy of an Indexer Poisoning Attack

When Your 'Linux ISOs' Turn Out to Be .exe Files: Anatomy of an Indexer Poisoning Attack
Photo by Markus Spiske / Unsplash

Waking up to a download queue filled with 1 GB Windows executables masquerading as open-source distributions and community media is a homelabber's worst nightmare. Here is how indexer poisoning works, why automation pipelines fall for it, and how to bulletproof your stack against malware droppers.


The Morning Audit: The Mystery of the 1 GB Executables

Like many self-hosters running an automated media and homelab engine, my Unraid setup operates quietly in the background. It manages automated feeds, queries indexers via Prowlarr, dispatches tasks to qBittorrent, and neatly sorts incoming community media-strictly 100% legal Linux ISOs, open-source documentation archives, and the occasional fan-subbed generic anime release, of course.

Usually, this pipeline runs like a Swiss watch. But during a routine sweep of qBittorrent's completed downloads, something caught my eye that made my inner sysadmin pause in disbelief.

Sitting in the completed queue were over a dozen downloads-totaling nearly 13 gigabytes of storage-where every single file ended with an unmistakable extension:

Ubuntu.LTS.2026.Update.1080p.WEB.H264-MeGusta.exe
Debian.Bookworm.Community.Release.S04E06.1080p.WEB.H264-playWEB.exe
Fedora.Silverblue.Special.Edition.S38E08.1080p.WEB.H264-SYNCOPY.exe
Generic.Anime.Chronicles.S02E10.1080p.WEB.H264-ViETNAM.exe

Over in the automation dashboard, the queue was in a state of suspended animation, displaying amber warning badges across the board:

Caution: Found executable file with extension: '.exe'

Is this an elaborate hacker joke? A sophisticated malware campaign? And how on earth did automated tools get tricked into downloading over a dozen raw Windows binaries?


Joke or Virus? The Anatomy of an Indexer Poisoning Campaign

Make no mistake: this is not a joke. It is an active malware delivery campaign.

For years, bad actors have exploited public torrent ecosystems using a technique known as indexer poisoning. Here is the play-by-play of how it works:

  1. The Malicious Payload: The attackers take a commodity infostealer (like RedLine, Lumma, or Vidar) or a remote access trojan (RAT) wrapped in a dropper.
  2. Byte Padding (Null-Stuffing): A typical malware executable is only a few megabytes. If a user or an automated bot saw a 5 MB file labeled as a 1080p video or an OS install disk, it would be flagged immediately. To bypass primitive size checks, the attackers pad the executable with hundreds of megabytes of binary null bytes (zeros) until the file weighs in between 800 MB and 1.2 GB.
  3. Scene Naming Mimicry: They append legitimate-sounding scene tags (-MeGusta, -playWEB, -SYNCOPY) to mimic established encoding groups.
  4. Future Baiting: Attackers frequently target release schedules. They will craft releases for seasons that haven't even gone into production yet (e.g. Season 4 of a show that just finished Season 2) or target episodes scheduled to air a few days into the future. They know that eager automated RSS scrapers have those keywords monitored and ready to trigger the microsecond a torrent hits the tracker.
  5. The Trap: The objective is simple. If a non-technical user navigates to their completed shared downloads folder on a Windows machine, sees a file labeled after their favorite series or ISO, and double-clicks it expecting VLC to launch, Windows obediently executes the binary. Game over.

Fortunately, Sonarr and Radarr have built-in file verification guards: because the files weren't valid video containers (.mkv, .mp4), the automation stack refused to import them into Jellyfin/Plex. They were safely quarantined in the staging directory. But having live malware binaries sitting on server storage is unacceptable.


The Root Cause: How Did It Bypass the Indexer Filters?

Digging into the API logs revealed the exact breach point. All 13 poisoned torrents were grabbed within a 30-second window on a single afternoon. And every single one came from the exact same indexer: Nyaa.si via Prowlarr.

Nyaa is revered as the de facto repository for community anime and East Asian media. So why was it serving up fake western TV episodes and rogue binaries?

Two configuration oversights caused the leak:

  1. Broad Category Syncing: In Prowlarr, the Nyaa indexer had its category filter set to 0 (All Categories). In turn, Sonarr was configured to query Nyaa under category 5000 (Standard TV).
  2. Unmoderated Tracker Sections: While Nyaa's core anime categories are well-maintained, public torrent sites often have "Live Action", "Non-English", or "Software" sections that botnets aggressively target with automated spam uploads. Because Sonarr was asking Nyaa for standard TV shows, it happily ingested these poisoned uploads during an RSS sync cycle.

The Remediation: Sweeping and Sanitizing

Cleaning up the mess required an atomic sweep across both the download client and the automation controller:

  1. Storage Verification: A direct scan of qBittorrent verified that zero executables or non-media files remained across all active tasks.

Queue Purge with Blocklisting: Rather than just hitting "Delete" in qBittorrent, we sent a deletion command directly through the Sonarr API:

DELETE /api/v3/queue/{id}?removeFromClient=true&blocklist=true

This instructed qBittorrent to remove the torrent, purged the .exe files from the filesystem, and permanently added the torrent info-hashes to Sonarr's blocklist so they can never be re-downloaded.


Defense-in-Depth: How to Prevent This Forever

Relying on a single line of defense is a recipe for eventual compromise. To ensure this never happens again, we implemented three layers of hardening:

Layer 1: Lock Down Indexer Scope (Prowlarr & Sonarr)

An anime indexer should never be queried for mainstream non-anime content. In Prowlarr and Sonarr:

  • Strip TV Category 5000: In Sonarr's indexer configuration for Nyaa, remove 5000 (TV) from categories and restrict it exclusively to 5070 (Anime).
  • Restrict Categories in Prowlarr: Set Nyaa's category filter to Anime Only (cat-id = 1).
  • Enforce Trusted Uploaders: Set Nyaa's filter mode to Trusted only (filter-id = 2). This filters out anonymous, newly created accounts and only returns releases uploaded by verified community groups.

Layer 2: Native File Filtering in qBittorrent

Many users don't know that qBittorrent has native, client-side file exclusion rules built right in. You can configure qBittorrent to automatically reject and refuse to download executable extensions regardless of what a torrent claims to contain.

Through the WebUI preferences (or via the /api/v2/app/setPreferences API), enable:

{
  "excluded_file_names_enabled": true,
  "excluded_file_names": "*.exe\n*.scr\n*.bat\n*.cmd\n*.vbs\n*.msi\n*.pif\n*.lnk\n*.com"
}

With this enabled, even if an untrusted torrent slips through the automation pipeline, qBittorrent marks any matching binary with a "Do Not Download" priority, preventing the malware payload from ever touching server disks.

Layer 3: Automation Hygiene & Release Profiles

  • Custom Formats & Release Profiles: In Sonarr and Radarr, configure custom formats to require known, reputable release groups and assign negative scores to unknown or suspiciously generic naming conventions.
  • Monitor State Awareness: Be cautious about mass-monitoring unannounced future seasons. Attackers intentionally name poisoned files after future seasons (e.g. Season 4 when Season 3 hasn't finished) because they know unattended scrapers will pick them up.

Final Thoughts

Automation in the homelab is incredible, but handing unattended fetch privileges to internet indexers comes with real responsibilities. When automation handles the download pipeline, public trackers will eventually test your boundaries.

By enforcing trusted-only indexer scopes, enabling client-side extension blacklisting, and letting your management tools automatically quarantine and blocklist anomalies, you can sit back and let your Linux ISOs download in peace-without having to dodge rogue executables.

Fahim

Fahim

Engineer, husband, dad, and photography enthusiast documenting technology, creativity, and the occasional rabbit hole.
Ottawa, ON