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

@hzero-front-ui/hzero-uinpm

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

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

What this malware does

Package @hzero-front-ui/[email protected] is a scope-lookalike of @hzero-front/hzero-ui with a placeholder version, empty author, generic description, and a trivial index.js. Its package.json preinstall and install lifecycle scripts base64-encode $(whoami):$(hostname):$(pwd):$npm_package_name and send the encoded value to attacker-controlled subdomains of callback.m0chan.co.uk over both HTTPS (curl) and DNS (nslookup). This fires automatically on npm install, leaking the installer's OS username, hostname, current working directory, and the internal package name that resolved to this lure — the canonical dependency-confusion beacon shape.

Malicious versions

1 flagged
99.99.99

Indicators of compromise (SHA-256)

a1b33c04eb2fb12d521b76353993517475d9239c9790c085d16c0c3d0a4ba2f9

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/hzero-ui (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/hzero-ui across your stack and pipelines.

  2. If you installed it — respond

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

References

Credits

  • Amazon Inspector · finder

Detect & block this

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