So a couple of months ago, windows defender started flagging some jackett files as trojan, it's still flagging it for me. Devs told everyone to just ignore it. Do we have a consensus about it?

all 9 comments

sorted by: hot top controversial new old
[–] 17 points 4 months ago (3 children)

https://github.com/Jackett/Jackett/issues/16352

Seems to only affect windows and is a false positive which seems reasonable

I didnt even know they built it for windows

  • source
  • hideshow 3 child comments
  • [–] [S] 4 points 4 months ago* (1 child)

    All the responses in that and other github issues that are saying it's a false positive are from the developers of the project. I was wondering if someone else with expertise verified it.

  • source
  • parent
  • hideshow 1 child comment
  • [–] 4 points 4 months ago* (last edited 4 months ago)

    On VirusTotal only 2/67 Antivirus vendors flag it as anything

    https://www.virustotal.com/gui/file/07550782ba3349e895002dc8886ff266025e4b06efe4d6accdd56355879ee821/

    That's the usual sign of a false positive, a real malware/virus issue would show up in pretty much all the main scans.

    EDIT: Here's another scan, 0 antivirus vendors flagged in this one - Jotti is a much smaller site but you get the idea

    https://virusscan.jotti.org/en-US/filescanjob/ktpebjnvdw

  • source
  • parent
  • [–] 1 point 4 months ago* (last edited 4 months ago)

    I didnt even know they built it for windows

    The *arrs are (or were, at least - Jackett is part of that family) dependent on Microsoft's .NET framework. I clearly remember having to set up Mono to get Sonarr running in a Debian VM some years ago...

  • source
  • parent
  • [–] 14 points 4 months ago

    First I'm hearing of this, but I run it in docker on Linux.

  • source
  • [–] 6 points 4 months ago (1 child)

    Sound normal for Windows, back when I was using Windows I usually had to whitelist torrent clients in Windows Defender otherwise the torrent client .exe would disappear randomly during a virus scan. It was always some sort of false positive.

  • source
  • hideshow 1 child comment
  • [–] 5 points 4 months ago

    3rd party issue. No action needed by jackett.

  • source
  • [–] 2 points 4 months ago

    I did not know about this, I had it installed somewhere in the past. I will revise the codebase tomorrow just in case.

  • source