Halil, I’d split this into proven execution paths versus capability claims we should not over-brief yet.
For The Gentlemen, the huntable piece is not the “21 techniques” headline by itself — it’s the execution pattern around it. Picus reports a Windows ransomware with self-propagation that can try up to 21 remote execution methods, plus .umc16h file extension and README-GENTLEMEN.txt ransom notes. Securelist also describes pre-encryption recon using SharpADWS, NetScan, Advanced IP Scanner, and netsh, with access via stolen/weak credentials, exposed VPNs/firewalls, or brokers. So this week I’d hunt for: recon-tool execution followed by remote fan-out, service/task/WMI-style lateral launches, rapid multi-host file rewrites, and the ransom-note/extension pair. But I would phrase “21 techniques” as reported capability, not proven worm autonomy unless we have execution traces showing which techniques fired successfully.
For JadePuffer, the behavior is narrower but nastier in a different way: reported Langflow exploitation via CVE-2025-3248, credential theft, pivot to MySQL/Nacos, use of CVE-2021-29441 to create rogue Nacos admin accounts, and encryption/replacement of 1,342 Nacos configuration items. Hunt exposed Langflow systems spawning shells or outbound tooling, credential access from Langflow hosts, new Nacos admin creation, and bulk config overwrites containing extortion text. I’d be careful with the “first fully LLM-agent-run ransomware” claim — operationally, defenders should brief it as agent-assisted intrusion and database extortion reported by researchers, not as proof that autonomous ransomware can universally run end-to-end in every environment.
For Cavern/Cav3rn and Gaslight, I don’t have enough sourced binary detail in front of me to validate the family naming or the claimed mechanics. If Cavern/Cav3rn is really abusing SysAid DLL side-loading, the immediate hunt is SysAid loading unexpected DLLs from writable or nonstandard paths, newly dropped DLLs adjacent to legitimate SysAid binaries, and child-process/network behavior from SysAid services that does not match admin tooling. For Gaslight, if the macOS stealer/backdoor claim holds, hunt LaunchAgent/LaunchDaemon persistence, browser/keychain access, suspicious AppleScript or shell execution, and outbound beacons from unsigned or recently dropped binaries. But the “prompt-injection-style analysis evasion” piece needs caution: unless we see the actual strings or logic gates, that may be analyst/tool deception, not runtime evasion.
My bottom line: brief The Gentlemen lateral fan-out, JadePuffer Langflow-to-Nacos extortion, and SysAid side-loading/macOS persistence hunts as actionable. Hold back on saying “worm,” “fully autonomous AI ransomware,” “modular C2,” or “AI-evasive malware” as proven until the execution traces or binary-level artifacts are on the table.