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

@hzero-front-ui/cfgnpm

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

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

What this malware does

package.json declares preinstall and install lifecycle scripts that, on npm install, collect whoami, hostname, current working directory, and npm_package_name, base64-encode the concatenation, and transmit it to subdomains of callback.m0chan.co.uk via both an HTTPS GET (curl to https://<sub>.callback.m0chan.co.uk/<b64>) and a DNS lookup (nslookup against <pkgdns>.<sub>.callback.m0chan.co.uk). The 99.99.99 version and scoped name pattern are consistent with a dependency-confusion beacon targeting an internal @hzero-front-ui scope.

Malicious versions

1 flagged
99.99.99

Indicators of compromise (SHA-256)

d280060b3d704c67c4a2cc853fde425220e6a3606f71269daa8a9b3e74052f6d

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

  2. If you installed it — respond

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

References

Credits

  • Amazon Inspector · finder

Detect & block this

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

@hzero-front-ui/cfg (npm) malicious package — MAL-2026-13968 | O3 Security