vendor binary

The JDownloader Installer Supply Chain Attack

Updated 5 Oct 2026 · Incident date 6 May 2026

The official JDownloader website served a malicious Windows Alternative Installer and Linux shell installer on 6 and 7 May 2026.

Attackers used an unpatched CMS flaw to change the download links. They did not change the real installer files.

What happened

Attackers changed the download links on the JDownloader website for about one day.

  • The first-stage Windows installer was unsigned. A user had to bypass the Windows SmartScreen warning.
  • A second-stage dropper unpacked five components from XOR-encrypted resources.
  • The components included a Python remote access bot, an r77 rootkit stager and a policy that blocks more than 50 security tools.
  • The bot found its command servers through public paste sites, with a Tor address and a domain generation algorithm as fallbacks.
  • The Linux installer put a SUID binary and a shell profile script on the machine.

Gen Digital reports that the site was compromised on 6 May 2026. The window closed on 7 May. Clean downloads returned by 9 May.

Affected versions

  • Windows: the "Download Alternative Installer" links on the official site, 6 to 7 May 2026.
  • Linux: the shell installer link, same window.
  • Not affected: in-app updates, macOS downloads, the Flatpak, Winget and Snap packages, and the main JAR package.

Indicators of compromise

  • Stage 1 Windows installer SHA-256: 5a6636ce490789d7f26aaa86e50bd65c7330f8e6a7c32418740c1d009fb12ef3.
  • Stage 2 dropper SHA-256: 77a60b5c443f011dc67ace877f5b2ad7773501f3d82481db7f4a5238cf895f80.
  • Linux payload SHA-256: 6550672cac21e036882921dd934ee06552dc74d3b0a9e1ddc26f952855e11371.
  • Command servers: parkspringshotel[.]com and auraguest[.]lk. Staging server: checkinnhotels[.]com.
  • Windows registry: HKCU\SOFTWARE\Python\*, HKLM\SOFTWARE\$77stager, $77dll32, $77dll64, $77svc.
  • Windows mutex: Global\0C3C1D37. Policy file: %WINDIR%\System32\CodeIntegrity\SIPolicy.p7b.
  • Linux: /usr/bin/systemd-exec (SUID) and /etc/profile.d/systemd.sh.
  • Publisher names on the fake files: "Zipline LLC" and "The Water Team". The real installers carry an "AppWork GmbH" signature.

How to check

On Linux, test for the persistence files.

ls -l /usr/bin/systemd-exec /etc/profile.d/systemd.sh

On Windows, compare the installer hash with the list above and test for the policy file. Use the name of your file.

Get-FileHash .\JDownloader2Setup.exe -Algorithm SHA256; Test-Path "$env:WINDIR\System32\CodeIntegrity\SIPolicy.p7b"

What to do now

  1. Determine whether anyone downloaded the Windows Alternative Installer or the Linux shell installer on 6 or 7 May 2026.
  2. Install the operating system again on each machine that ran one. The rootkit makes partial cleanup unreliable.
  3. Change passwords for sensitive accounts from a clean device.
  4. Block the command domains above.

Frequently asked questions

Did the in-app updater carry the malware?

No. Gen Digital and Security Affairs report that in-app updates were not affected.

Who signs the real installers?

AppWork GmbH. The malicious Windows files were unsigned or showed other publisher names.

Sources

  1. gendigital.com/blog/insights/research/inside-the-jdownloader-supply-chain-attack
  2. securityaffairs.com/191920/malware/official-jdownloader-site-served-malware-to-windows-and-linux-users.html

Send this page to the person who looks after AI at your company.

Email it

More supply chain attacks

All 172 attacks in the library · What is a supply chain attack? · How to prevent supply chain attacks

Check the next update before you install it

Vigilance compares the version you trust with the new one. It names the one file that gained a power the old version did not have.

Start the free 14-day trialBrowse the attack library