Loading story…
Praetorian publicly released Swarmer, a Windows persistence tool that enables low-privilege attackers to establish startup execution while evading EDR visibility by avoiding standard registry-write APIs. The technique abuses mandatory user profiles by creating a NTUSER.MAN hive (derived from NTUSER.DAT) that overrides the normal per-user registry hive at next logon; because the modified hive is not loaded until the user signs in again, EDR products that rely on monitoring live registry modifications (e.g., hooks on RegSetValue* and related telemetry) may not observe the persistence being set.
Swarmer achieves this by using Microsoft’s Offline Registry Library (offreg.dll) to build and modify registry hives “offline” (e.g., via functions such as OROpenHive, ORCreateKey, ORSetValue, and ORSaveHive) rather than calling the typical Reg* APIs that many EDRs instrument. Reported operator workflow includes exporting HKCU, adding a startup entry (commonly under HKCU\SOFTWARE\Microsoft\Windows\CurrentVersion\Run), generating a modified NTUSER.MAN, and placing it in %USERPROFILE% so the persistence activates on the next login; the Reddit post links to the same research/tool release and reiterates the core evasion premise (no observable registry writes at the time persistence is staged).
Mallory correlates global threat intelligence with your attack surface — know if you’re exposed before adversaries strike.
3 events from the most recent confirmed update back to the earliest known activity.
Praetorian publicly released Swarmer and described how it uses mandatory user profiles (NTUSER.MAN) and Microsoft's Offline Registry API in Offreg.dll to modify a copied user registry hive without relying on standard Reg* APIs commonly monitored by EDR tools. The disclosure also outlined limitations and possible detection opportunities, including monitoring for unexpected NTUSER.MAN creation and unusual Offreg.dll usage.
Praetorian said its Windows persistence tool and technique, dubbed Swarmer, had been used operationally since February 2025. The method abuses mandatory user profiles and offline registry hive editing to establish HKCU Run-key persistence that activates at the next user logon.
A blog post published a proof of concept, RegREeper.exe, showing how to establish HKCU Run-key persistence by saving a registry hive, modifying it offline, and restoring it with RegRestoreKeyW after enabling SeRestorePrivilege. The research also reported that Sysmon did not log the save-and-restore workflow and attributed this to gaps in the REG_NOTIFY_CLASS operations it monitors.
Vulnerabilities, threat actors, malware, products, organizations, and breaches Mallory has linked to this story.
3 references tracked. Mallory keeps watching after this page renders.
cybersecuritynews.com
Open sourcereddit.com
Open sourcetccontre.blogspot.com
Open sourceMap indicators from this story to your assets and identify affected systems in minutes.
Every observed campaign, victim, and pivot linked to actors named in this story.
Malware, exploits, and IOCs connected to the activity described here.
YARA, Sigma, and Snort rules deployed to your SIEM as soon as they’re published.
Get matching new stories delivered to your team as they break — not the next morning.
Ask questions about this story and take action on the answers.
Other stories Mallory is tracking that overlap on entities, sources, or topic labels.
Security researcher **NightmareEclipse/Chaotic Eclipse** publicly released a proof-of-concept exploit for a Windows local elevation-of-privilege zero-day dubbed **LegacyHive**, targeting the **Windows User Profile Service** (`ProfSvc`). The flaw abuses arbitrary registry hive loading to let a standard user mount another user’s registry hive—particularly `usrclass.dat`—under their own registry classes root, potentially exposing sensitive registry data and enabling privileged read-write access that could support further escalation. Reports said the public PoC was intentionally limited and may require additional user credentials, while the researcher claimed the original technique could load arbitrary hives without that restriction. The disclosure said the issue affects fully patched supported Windows desktop and server versions, including systems updated through **July 2026**, and no **CVE**, Microsoft advisory, or official patch had been identified at the time of publication. Researchers and defenders warned that, although the released PoC does not by itself guarantee full system compromise, it provides a strong **post-compromise primitive** that skilled attackers could weaponize quickly, especially given prior rapid criminal adoption of the researcher’s earlier Microsoft disclosures. Background documentation on Windows registry hives shows that user profile hives store application settings, desktop configuration, environment data, network connections, and other per-user information, underscoring the sensitivity of unauthorized hive access.
Jul 20, 2026
Two separate Windows-focused research writeups describe practical **evasion techniques against Microsoft Defender/EDR**. One demonstrates bypassing Defender’s signature-based detections by constructing suspicious strings (e.g., `Invoke-Mimikatz`) at runtime using PowerShell character encoding/concatenation (`[char]NN`), reporting reliable evasion in a fully updated Windows 10/11 environment with real-time protection and script scanning enabled. A second report covers **EDRStartupHinder**, a newly released tool by researcher **TwoSevenOneT** that aims to prevent antivirus/EDR services from starting cleanly on boot (demonstrated against Defender on Windows 11 25H2). The technique uses a higher-priority Windows service and **Bindlink** redirection of a selected `System32` DLL to a tampered (“corrupted”) copy so the protected EDR process (e.g., `MsMpEng.exe`, running as **PPL**) fails to load required dependencies and crashes at startup; the article notes operator requirements such as choosing a DLL not in `KnownDLLs` and identifying service group order via `HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\ServiceGroupOrder` and tooling like Process Monitor/Process Explorer boot logs.
Jun 29, 2026
Threat actors are increasingly leveraging built-in Windows features to establish persistence and evade detection on compromised systems. Common persistence mechanisms include the abuse of registry keys, scheduled tasks, and Windows Management Instrumentation (WMI), which allow malware to survive reboots and maintain long-term access. These techniques often exploit legitimate system administration tools, making it challenging for defenders to distinguish malicious activity from normal operations. Security teams are advised to proactively hunt for indicators of compromise (IOCs) associated with these persistence methods, as even fileless malware can leave traces in system configurations or memory. Fileless malware represents a significant evolution in attack methodology by operating entirely in memory and utilizing trusted Windows binaries such as PowerShell, MSHTA, and rundll32. This approach enables attackers to bypass traditional signature-based antivirus solutions, as no malicious files are written to disk. Persistence for fileless malware can be achieved by embedding encoded scripts or commands within the Windows Registry, WMI, or Task Scheduler, allowing the malware to re-execute at startup without leaving conventional artifacts. Defenders must adapt detection strategies to monitor for unusual use of native tools and changes in system persistence mechanisms to effectively counter these threats.
Jun 29, 2026