The evolution of the Kuiper ransomware

Kuiper is a Go-based ransomware marketed as an easy-to-use, cross-platform kit by RobinHood, with a plan to offer operational help for a commission and a planned double-extortion leak site. Researchers uncovered that the sales hype overstated capabilities, and a leaked copy of the server, source code, and decryption keys provided concrete exposure of the project’s flaws and evolution across Windows, Linux, and MacOS variants.

Keypoints

  • Kuiper is advertised as ready-to-use ransomware with ongoing updates; a leak blog surfaced the server and keys.
  • Encryption uses AES-CFB with a per-network key/IV, later adding ChaCha20 and tiered encryption for large files.
  • Updates expanded platform support (MacOS, FreeBSD) and introduced features like wallpaper changes and faster encryption.
  • Despite claims of AV/EDR evasion, analyzed samples show little obfuscation and reveal notable operational gaps.
  • The malware spreads laterally by scanning local IPs, copying itself to remote machines, and using WMIC and SMB shares to propagate.
  • Backups are deleted, Defender is disabled, and memory keys are cleaned; a ransom note and self-removal steps complete the kill chain.

MITRE Techniques

  • [T1021.002] Remote Services: SMB/Windows Admin Shares – Brief description of how it was used. Quote: “Example command: – “wmic /node: process call create””
  • [T1057] Process Discovery – Brief description of how it was used. Quote: “Uses “taskkill” to loop and terminate targeted processes”
  • [T1059.001] Command and Scripting Interpreter: PowerShell – Brief description of how it was used. Quote: “Example command: – Starts with “powershell.exe -ep bypass -w hidden -enc” followed by a space and the encoded command”
  • [T1059.003] Command and Scripting Interpreter: Windows Command Shell – Brief description of how it was used. Quote: “Example command: – Starts with “cmd.exe /c” followed by a space and the command to execute (i.e. “shutdown /r /t 8”)
  • [T1059.004] Command and Scripting Interpreter: Unix Shell – Brief description of how it was used. Quote: “Example command: – Starts with “/bin/bash -c” followed by a space and the command to execute (i.e. “reboot”)”
  • [T1046] Network Service Scanning – Brief description of how it was used. Quote: “Active Scanning: Scanning IP Blocks” / “Iterates over the last octet of the current IP to see if the SMB share is open and writable, allowing the malware to spread itself”
  • [T1016.001] System Network Configuration Discovery – Brief description of how it was used. Quote: “Gets the current IP address from the list of network interfaces from the machine, using a minor blocklist to avoid selecting the wrong address”
  • [T1106] Native API – Brief description of how it was used. Quote: “Native API” / “WDEnable” (PowerShell bypass and Defender interaction)
  • [T1486] Data Encrypted for Impact – Brief description of how it was used. Quote: “Data Encrypted for Impact”
  • [T1562.001] Disable or Modify Tools: Defender – Brief description of how it was used. Quote: “The commands to disable Defender in Kuiper version A are hex encoded” / “Version B’s approach differs, as it creates several loops.”
  • [T1497] Virtualization/Sandbox Evasion – Brief description of how it was used. Quote: “Tries to bypass using: – Iterating over an empty loop – Trying to read ‘C:WindowsSystem32cmd.exe’”
  • [T1547.001] Boot or Logon Autostart: Registry Run Keys / Startup Folder – Brief description of how it was used. Quote: “reg add “HKEY_LOCAL_MACHINE…Winlogon” /t REG_SZ /v Shell …”
  • [T1070.004] Indicator Removal on Host: File Deletion – Brief description of how it was used. Quote: “removal of the backups” / “delete logs and files”
  • [T1003] Valid Accounts – Not explicitly listed with a quote; included for context of credential use if present in variants. (Note: no direct quote from the article for this technique.)

Indicators of Compromise

  • [URL] context – https://qtox.github.io, https://tox.chat/download.html
  • [Email] context – [email protected]
  • [MD5] context – 84820f3eb491a2fde1f52435cd29646c; 0608c64c57dcc09246be00f0b2767e6e
  • [SHA-1] context – 8c6e135495fcf8898de62e6793e3cd06d3025461; 02642663BFC7BE0C06051F4B01C9861102C71850
  • [SHA-256] context – df430ab9f5084a3e62a6c97c6c6279f2461618f038832305057c51b441c648d9; 0162641163a30a2edff787eeecc733ab1de46f03e213743dc768d39eb3075985
  • [File] context – safemode.exe, safemode.bat, setup.bat

Read more: https://www.trellix.com/about/newsroom/stories/research/the-evolution-of-the-kuiper-ransomware/