⚡ Weekly Recap: Linux Rootkit, macOS Crypto Stealer, WebSocket Skimmers and More

Threat Visual

⚠️ THREAT ALERT: ⚡ Weekly Recap: Linux Rootkit, macOS Crypto Stealer, WebSocket Skimmers and More

The reported Linux rootkit leverages a double‑stage loadable kernel module (LKM) that first injects a malicious ELF payload via a compromised package manager repository (APT/Yum) and then escalates privileges by exploiting CVE‑2023‑2630, a use‑after‑free in the netfilter core that permits arbitrary kernel memory writes. The initial stage drops a user‑space daemon disguised as a systemd service which communicates over a hidden UNIX domain socket, awaiting a trigger command from the attacker’s C2. Once triggered, the LKM patches the sys_call_table to hijack execve and ptrace calls, allowing the rootkit to stealthily hide its processes, files, and network sockets while exfiltrating credentials and cryptographic material. The macOS crypto‑stealer component shares code reuse with the “OSX/CoinMiner” family and abuses the Apple System Integrity Protection (SIP) bypass discovered in CVE‑2024‑22527, allowing the malware to load a signed kernel extension that intercepts CoreCrypto APIs and redirects mined payloads to attacker‑controlled wallets.

The WebSocket skimmer operation is delivered through compromised JavaScript bundles on popular e‑commerce sites, where an obfuscated payload establishes a persistent WebSocket connection to a malicious endpoint. By instrumenting the browser’s WebSocket API via a prototype pollution vulnerability (CVE‑2024‑4068) in the Chromium networking stack, the skimmer siphons form fields, authentication tokens, and payment data in real time without triggering SameSite or CSP defenses. The payload also employs a timing‑channel evasion technique, transmitting data in low‑bandwidth bursts that blend with legitimate heartbeat frames, making detection via typical network anomaly tools difficult. The broader campaign ties these vectors together under a single C2 infrastructure, using domain fronting and DNS tunneling to obscure command traffic, and rotates encryption keys daily via a Diffie‑Hellman exchange embedded in the rootkit’s kernel module, complicating forensic timeline reconstruction.

Mitigation requires a multi‑layered response: immediately audit and purge all third‑party package repositories, enforce signed package verification, and apply kernel patches for CVE‑2023‑2630 and CVE‑2024‑22527 via the latest distro kernels (e.g., Linux 6.8.5+ and macOS 14.5+). Deploy Kernel Address Space Layout Randomization (KASLR) hardening and enable eBPF lockdown to prevent unauthorized syscalls. On macOS, re‑enable SIP and block unsigned kernel extensions through the “System Extensions” policy. For the WebSocket skimmer, update Chromium‑based browsers to versions patched against CVE‑2024‑4068, enforce strict Content Security Policy with “script-src 'self'” and disable insecure WebSocket origins via browser hardening profiles. Network defenders should implement TLS‑inspection with anomaly detection for low‑rate WebSocket traffic, enforce DNSSEC, and isolate critical assets in zero‑trust segments, while threat‑hunters should monitor for anomalous LKM loading events, hidden UNIX sockets, and unexpected WebSocket handshake patterns.

🛡️ CRITICAL SECURITY SCAN REQUIRED

Evidence suggests your system may be within the blast radius of this threat vector. Use the ZeroDay Radar scanner to verify your integrity immediately.

>> LAUNCH ZERO-DAY THREAT SCANNER <<

Source Intelligence: Full Technical Breakdown

Post a Comment

0 Comments