DFIR Research Exposes Stealthy Persistence and Remote Access Tradecraft Across Windows, Linux, and AWS
Attack Tradecraft · 11 sources · Updated 4mo ago · First seen Jun 4, 2026

A series of DFIR case studies documented how attackers are increasingly relying on living-off-the-land techniques, uncommon runtimes, and legitimate administration tools to maintain access while evading detection. On Windows, investigators dissected a PHP backdoor that used php-win.exe, a scheduled task named ClockLauncher, and a ClockSystemService service to fetch and execute second-stage code invisibly; a separate intrusion used mailbombing and Microsoft Teams vishing to deliver a modular Deno-based RAT and proxy that persisted via the HKCU\Run key and communicated over WebSocket infrastructure hosted behind CloudFront. Another investigation traced a malicious .lnk file to a WebDAV-hosted Remcos payload cached under TfsStore\Tfs_DAV, while repeated compromises of a vulnerable Kentico CMS server led to webshell deployment, SEO spam, PowerShell-based payload retrieval, and installation of a malicious IIS module, HTTPCacheLog, that accepted commands through HTTP cookies.
On Linux and cloud infrastructure, researchers showed how attackers abused both commodity malware and stealthier post-exploitation tooling. TeamTNT-linked activity used tmate as a covert backdoor on Linux servers, often without normal login traces, while analysis of the REPTILE 2.0 rootkit loader showed it bypassing insmod by decrypting an embedded kernel module and loading it directly with the init_module syscall. A separate Sysrv botnet infection established cron persistence, masqueraded as kthreaddk, and included exploitation and brute-force features for propagation. In AWS, an extortion actor deleted S3 buckets and supplied a fake Linux “recovery” binary that merely simulated restoration rather than recovering cloud data. Across the investigations, defenders were urged to hunt for recurring artifacts such as scheduled tasks, Run keys, suspicious services, unusual binaries in user-writable paths, outbound SSH or WebSocket traffic, and syscall-level module loading, using telemetry and tools including Velociraptor, AutoRuns, Sysmon, and CloudTrail.


