Loading malware…
HelloInjector is a Windows first-stage loader used in the HelloNet cyber-espionage campaign targeting Russian organizations, including entities in government, energy, transport, education, logistics, industrial, IT, software development, instrumentation, and electronics sectors. The malware is deployed by abusing the local ViPNet Update System through DLL sideloading: a malicious library is placed alongside the legitimate ViPNet updater component so that it is loaded automatically at system startup. Once executed, HelloInjector locates an svchost.exe instance associated with netsvcs, injects its code into that process, and launches the next-stage payload in memory. Reported implementations use native process-injection primitives to write into the remote process and create a thread, allowing execution under a trusted Windows service host context. This behavior provides stealth, persistence across reboots through the updater startup path, and elevated execution context for follow-on modules. HelloInjector serves primarily as the entry point for additional malware in the toolchain, especially HelloProxy, which in turn can retrieve or launch further components such as HelloExecutor, HelloCleaner, and in some cases HelloBackdoor. The broader operation has been tentatively linked with low confidence to an unidentified Chinese-speaking threat actor, though that attribution remains uncertain and false-flag activity has not been ruled out.
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.
Attackers place a malicious DLL file, HelloInjector, within the ViPNet Update System directory. This file is then sideloaded at startup, injecting into the svchost.exe process to gain elevated privileges and persistence.
6 distinct techniques documented for this family, organized by ATT&CK tactic.
If such a process is found, the loader injects itself into the target process using the NtWriteVirtualMemory and NtCreateThreadEx functions.
If such a process is found, the loader injects itself into the target process using the NtWriteVirtualMemory and NtCreateThreadEx functions.
4 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.
8 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
Malicious loader DLL masquerading as a ViPNet update component, sideloaded by a legitimate update binary, capable of process injection into svchost.exe and loading the next-stage payload.
A component of the HelloNet toolkit used to inject code into svchost.exe.
A malicious DLL sideloaded via the ViPNet Update System that injects into svchost.exe to obtain elevated privileges and persistence, functioning as an initial loader component in the campaign.
First-stage DLL loader placed as a malicious wtsapi32.dll in the local ViPNet update directory; it is sideloaded by itcsrvup64.exe at system startup, injects into svchost.exe, and helps obtain elevated privileges and persistence across reboot.
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.