DoubleZero is a destructive .NET wiper written in C# and used in attacks against Ukrainian organizations during the early phase of Russia’s full-scale invasion of Ukraine. It has been tracked by CERT-UA as UAC-0088 and is widely documented as one of several wiper families deployed against Ukrainian targets in 2022.
The malware is heavily obfuscated and is designed to corrupt files, damage registry data, and render Windows systems unbootable. Its core wiping behavior relies on the NTFS FSCTL_SET_ZERO_DATA control path via NtFsControlFile to overwrite targeted content with null bytes. A commonly noted characteristic is that it can corrupt files by zeroing only the first 4096 bytes, a speed-optimized destructive technique sufficient to make many files unusable. It also includes a secondary file-wiping routine using standard .NET file operations. Beyond user data, DoubleZero targets boot-related components and registry structures associated with Windows startup, including boot configuration data, so that affected hosts may fail to boot after restart.
DoubleZero enumerates logical drives, traverses volumes for files matching targeted patterns, and interacts with file permissions and ownership to maximize destructive reach. Reported behavior includes attempts to obtain elevated privileges such as backup, restore, take-ownership, and shutdown rights, modification of access controls on targeted files and registry keys, recursive deletion of registry subkeys, and termination of the LSASS process before shutdown or reboot. Some reporting also notes logic to avoid execution on domain controllers or to alter behavior depending on privilege level, with reduced impact when administrative rights are unavailable.
The malware targets Windows environments and has been associated specifically with Ukrainian enterprises and critical infrastructure during wartime disruptive operations. Public reporting links it to broader Russian-aligned destructive activity in Ukraine, though high-confidence attribution at the malware-family level is generally limited to its tracking under UAC-0088 rather than a universally agreed named state actor. Delivery has been observed via ZIP archives using lure-themed filenames, and some assessments indicate the wiper may also have been manually executed after attackers had already obtained privileged access to victim systems.
Mallory pivots from this family to the IOCs, detections, and named campaigns that touch your stack, and pages you when something new lands.
1 distinct threat actor attributed by public researchers. Open in Mallory to see the full evidence chain and overlapping campaigns.
17 distinct techniques documented for this family, organized by ATT&CK tactic.
It also interleaves random code among actual operations, together with flattened control flow, to make the code harder to follow.
The sample enumerates the HKEY_CURRENT_USER, HKEY_USERS, HKEY_LOCAL_MACHINE registry keys including HKEY_LOCAL_MACHINE\BCD00000000... to remove them later.
The malware gets the root drive of the infected device and Operating System information using Environment.SystemDirectory and Environment.OSVersion properties.
Many entries concern “CaddyWiper”, “new data wiper hits Ukraine”, “destructive wiper malware”, and Sandworm operations using CADDYWIPER alongside INDUSTROYER2.
These privileges are used to ensure the wiper has the access right to destroy the target file and reboot the system after all the actions are done.
The corpus contains multiple technical analyses of wiper malware and “The Anatomy of Wiper Malware” focused on destructive techniques.
The DoubleZero wiper, for instance, only erases the first 4096 bytes of targeted files... The Azov wiper also implemented a somewhat more optimized wiping process. It does not remove all data in each file. Instead, it only targets 666 bytes in an alternating pattern...
5 indicators attributed across vendor reports, sandbox runs, and researcher write-ups. Full values are available in Mallory.
IPs, domains, and DNS infrastructure linked to this family.
File hashes (MD5, SHA-1, SHA-256) from samples and reports.
17 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
Mentioned in a list of wipers observed after AcidRain.
Wiper malware targeting Ukraine, mentioned as one of several destructive strains active during the invasion period.
Named as a wiper used in destructive campaigns (mentioned as part of a Russian wiper arsenal).
Wiper optimized for speed by corrupting only the first 4096 bytes of files, rendering them impractical to restore at scale.
Match every observed IP, domain, and hash against your live telemetry.
Named campaigns wielding this family, with evidence pinned to each claim.
CVEs this family uses for access and lateral movement.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Every documented technique, ranked by evidence weight.
Reddit, Mastodon, and CTI community discussion around this family.