Router is my own and up to date.
that does not say its dns settings are as you set them. if you use a default or weak password for your routers config page, an attacker could change its setting from the outside via dns rebinding, then scanning your net, finding your router, trying passwords and when succesfull changing firewall rules or change dns settings to make your programs check the attackers repository proxies instead of their vendor ones.
dns rebind: https://www.packetlabs.net/posts/what-are-dns-rebinding-attacks/
so better check its dns settings, that it likely is pushing to dhcp clients, too.
Thanks to flatpak it also doesn’t have the ability to see anything else from my system. it at least seems to asks for seeing way more…
jdownloader could theoretically also got hacked by a site you were downloading from. maybe having a complete list of what you downloaded and check those again but using source provided (and signed?) hashes could reveal something fishy.
maybe (if thats possible there) make a memory/debug dump from the process in that condition and ask the vendor to look at it.
maybe check your downloaders binary hashes and compare it to the vendors signed ones.
Reject 2025