MoonBounce
MoonBounce is a UEFI firmware implant/rootkit embedded in SPI flash on a victim motherboard. It was discovered by Kaspersky in late 2021 and is described as the third publicly known malicious SPI-flash UEFI implant after LoJax and MosaicRegressor. The implant tampers with the UEFI CORE_DXE/DXE Foundation component, intercepts the normal boot execution flow, and introduces a sophisticated, largely memory-only infection chain that preserves the normal boot sequence while leaving no disk artifacts. Reported behavior includes inline hooking of EFI Boot Services functions such as AllocatePool, CreateEventEx, and ExitBootServices, hooking later boot components including the Windows loader, introducing a malicious driver into Windows kernel memory, and injecting user-mode malware into svchost.exe.
MoonBounce is designed to deploy additional malware on the compromised system and to provide stealth and persistence. Because it resides in SPI flash, it can survive hard-disk formatting, disk replacement, and operating system reinstallation. Kaspersky reported that the user-mode stager contacted the hardcoded URL hxxp://mb.glbaitech[.]com/mboard.dll to retrieve an additional in-memory payload. Related infrastructure and malware observed in the same victim environment included ScrambleCross/SideWalk and loaders such as StealthVector and StealthMutant; Kaspersky also noted a distinctive self-signed SSL certificate and overlapping infrastructure including mb.glbaitech[.]com, ns.glbaitech[.]com, 188.166.61[.]146, 172.107.231[.]236, 193.29.57[.]161, 136.244.100[.]127, 217.69.10[.]104, and 92.38.178[.]246.
Kaspersky attributed MoonBounce with medium-to-high confidence, and elsewhere with high confidence, to the Chinese-speaking threat actor APT41, also known as Winnti. The broader intrusion activity associated with the campaign included host and network discovery, lateral movement via PsExec and WMI, attempted Active Directory database dumping with ntdsutil IFM, archiving with rar.exe, and cleanup of artifacts in %temp%, consistent with long-term espionage objectives. The initial infection vector for the firmware compromise was not determined; Kaspersky assumed remote infection and noted that successful deployment would require the ability to write to firmware, potentially via firmware vulnerabilities or platform configurations permitting such writes.
MoonBounce is repeatedly cited in reporting as a highly privileged UEFI bootkit/firmware threat alongside LoJax, MosaicRegressor, FinSpy, ESpecter, and BlackLotus. Kaspersky stated that classic Secure Boot would not stop MoonBounce because it does not authenticate firmware-level components and because MoonBounce patches in-memory images after they are loaded rather than bypassing Secure Boot directly. Intel Boot Guard and TPM-based integrity mechanisms were cited as defenses that could have countered the firmware-level modifications.
Hunt this family in your stack
Mallory pivots from this family to the IOCs, detections, and named campaigns that touch your stack, and pages you when something new lands.
Groups observed using it
1 distinct threat actor attributed by public researchers. Open in Mallory to see the full evidence chain and overlapping campaigns.
"MoonBounce... UEFI firmware implant... connection to APT41 (also known as Winnti)."
Techniques & procedures
1 distinct technique documented for this family, organized by ATT&CK tactic.
Persistence
1 technique
Persistence
Secure Boot is designed to thwart UEFI bootkits, a form of malware that alters the Unified Extensible Firmware Interface, the successor to the BIOS, both of which begin the initial boot sequence. Because these bootkits load before the OS and most other code, they can be difficult to detect.
Stealth
1 technique
Stealth
Secure Boot is designed to thwart UEFI bootkits, a form of malware that alters the Unified Extensible Firmware Interface, the successor to the BIOS, both of which begin the initial boot sequence. Because these bootkits load before the OS and most other code, they can be difficult to detect.
Recent activity
12 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
A named UEFI bootkit cited as one of the newer firmware-resident threats.
A highly privileged malware example referenced in the context of UEFI bootkit threats that Secure Boot is designed to block early in the boot process.
UEFI firmware-resident implant that patches the DXE Core (inline hook) to execute very early in the boot/firmware execution path, enabling stealthy, below-OS persistence.
Highly advanced UEFI firmware implant that patches/modifies the DXE Core execution path (inline hook) to execute beneath OS-level controls across legacy and pure UEFI boot paths.
The version that knows your environment.
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.