Skip to main content
Mallory
Malware1 associated actor

LittleDaemon

Tracked since Nov 25, 2025 · Updated 7 months ago
Trending this weekNot trendingOutside this week’s top 100
Mention activity · 30 daysNo mention activity in the last 30 days.
Vulns0Associated
Actors1Associated
ATT&CK12Techniques
IOCs1Tracked

LittleDaemon is a custom Windows downloader used by the China-aligned espionage group PlushDaemon as the first stage in a hijacked software-update infection chain. ESET reporting states it is delivered through adversary-in-the-middle attacks enabled by the group’s EdgeStepper network implant, which redirects DNS queries for legitimate software update domains to attacker-controlled infrastructure. The malware has been observed in both DLL and executable 32-bit PE forms and is commonly disguised as a DLL, including as popup_4.2.0.2246.dll. Its primary function is to communicate with the attacker-controlled hijacking node and, if the group’s SlowStepper backdoor is not already present or running on the victim system, fetch the next-stage downloader DaemonicLogistics, which then leads to deployment of SlowStepper on Windows machines. The campaign has included hijacking updates for popular Chinese software such as Sogou Pinyin. LittleDaemon itself does not establish persistence. Reported targeting associated with PlushDaemon includes organizations and individuals in China, Hong Kong, Taiwan, Cambodia, New Zealand, South Korea, and the United States, including universities and manufacturing-related entities. High-confidence indicators directly mentioned in the content include the masqueraded filename popup_4.2.0.2246.dll and its role in the EdgeStepper -> LittleDaemon -> DaemonicLogistics -> SlowStepper infection chain.

Is this in your environment?See whether this family's indicators match your telemetry and which of your assets are exposed to the CVEs associated with it.
Check your exposure
Threat actors

Associated threat actors

1 distinct threat actor Mallory has associated with this family across public reporting. Open in Mallory to see the full evidence chain and overlapping campaigns.

View more details →
PlushDaemon

“…PlushDaemon that leveraged the same technique to distribute a custom downloader called LittleDaemon.”

via the hacker newsthehackernews.com
MITRE ATT&CK

Techniques & procedures

12 distinct techniques documented for this family, organized by ATT&CK tactic.

Initial Access

2 techniques
T1195Supply Chain CompromiseEvidence1

Telemetry data from cybersecurity firm ESET indicates that since 2019, the threat actor has relied on malicious updates to breach target networks.

T1195.002Compromise Software Supply ChainEvidence1

"...hijacking the software update mechanism associated with Sogou Pinyin..."; "...hijack the software update process for Tencent QQ... to serve a trojanized version"

Execution

2 techniques
T1106Native APIEvidence1

The resolution intentionally utilizes LdrGetProcedureAddress (ntdll) instead of GetProcAddress (kernel32), effectively bypassing userland hooks placed by EDRs on the Win32 layer.

T1574.001DLLEvidence2

When a victim tries to update their software, they receive the first-stage malware downloader for Windows called LittleDaemon, which is disguised as a DLL file named ‘popup_4.2.0.2246.dll.’

Privilege Escalation

1 technique
T1055Process InjectionEvidence1

The output binary is explicitly named MemloadX64.dll, strongly suggesting process injection... Three calls to WriteProcessMemory write three stubs: the payload (which is actually an executable file), the PE loader, and the previously resolved APIs.

Stealth

7 techniques
T1027Obfuscated Files or InformationEvidence1

The binary stores their bitwise-inverted representations (NOT byte) in the .rdata section... a second NOT pass in each string initialization function restores the original string in memory.

T1027.007Dynamic API ResolutionEvidence1

Rather than statically importing LdrLoadDll or NtAllocateVirtualMemory, strings that are easily detectable by any static scanner, the binary stores their bitwise-inverted representations... The resolution intentionally utilizes LdrGetProcedureAddress (ntdll) instead of GetProcAddress (kernel32).

T1036MasqueradingEvidence1

The payload chain typically begins with LittleDaemon, a downloader posing as a DLL...

T1055Process InjectionEvidence1

The output binary is explicitly named MemloadX64.dll, strongly suggesting process injection... Three calls to WriteProcessMemory write three stubs: the payload (which is actually an executable file), the PE loader, and the previously resolved APIs.

T1140Deobfuscate/Decode Files or InformationEvidence1

LittleDaemon establishes communication with the attacker's hijacking node and fetches a second malware dropper named DaemonicLogistics, which is decrypted and executed in memory.

T1574.001DLLEvidence2

When a victim tries to update their software, they receive the first-stage malware downloader for Windows called LittleDaemon, which is disguised as a DLL file named ‘popup_4.2.0.2246.dll.’

T1620Reflective Code LoadingEvidence1

This buffer is a function designed to parse a PE binary, load its modules, and execute its entrypoint. This is essentially a custom Windows executable loader.

Credential Access

1 technique
T1557Adversary-in-the-MiddleEvidence2

A China-linked threat actor tracked as 'PlushDaemon' is hijacking software update traffic using a new implant called EdgeStepper in cyberespionage operations.

Collection

1 technique
T1557Adversary-in-the-MiddleEvidence2

A China-linked threat actor tracked as 'PlushDaemon' is hijacking software update traffic using a new implant called EdgeStepper in cyberespionage operations.

Command and Control

1 technique
T1105Ingress Tool TransferEvidence3

A first-stage deployed through hijacked updates, LittleDaemon is designed to communicate with the attacker node to fetch a downloader referred to as DaemonicLogistics if SlowStepper is not running on the infected system. The main purpose of DaemonicLogistics is to download the SlowStepper backdoor from the server and execute it.

Indicators of compromise

Observables

1 indicator attributed across vendor reports, sandbox runs, and researcher write-ups. Values are masked here and available in full in Mallory.

View all in app →
Indicator values are available in Mallory. Pivot on every hash, domain, URL, and IP, or pipe them straight into your SIEM.View all in Mallory
Activity feed

Recent activity

8 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.

View more in app →
+4 more in the timeline. Sign up to see them
Is this in your environment?See whether this family's indicators match your telemetry and which of your assets are exposed to the CVEs associated with it.
Check your exposure
Mallory platform

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets match these IOCs, which detections are missing, which campaigns to expect next, and what to do in the next 30 minutes.
IOC matching1Match every observed IP, domain, and hash against your live telemetry.
Associated threat actors1Groups linked to this family, with evidence pinned to each claim.
Associated vulnerabilitiesCVEs linked to this family, with the reporting behind each link.
Detection signaturesYARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
MITRE ATT&CK mapping12Every documented technique, ranked by evidence weight.
Researcher chatterReddit, Mastodon, and CTI community discussion around this family.