Which versions of dzvchorehui2 are malicious?

The following npm versions of dzvchorehui2 are flagged malicious: 1.0.0. Treat any of these as compromised.

How do I remediate dzvchorehui2 if I installed it?

dzvchorehui2 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 dzvchorehui2 — how do I know if it already compromised me?

If dzvchorehui2 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 dzvchorehui2 part of a known attack campaign?

Yes — dzvchorehui2 is associated with the GHSA-cj4c-xm2v-8m5g, IN-MAL-2026-017419 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 dzvchorehui2 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 dzvchorehui2 (version 1.0.0). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging dzvchorehui2 across your stack and pipelines.

Malicious package

dzvchorehui2npm

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

Malicious code in dzvchorehui2 (npm)

MAL-2026-13804

Immediate action

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

npm uninstall dzvchorehui2

What this malware does

The package contains a single HTML file that impersonates a Cloudflare 'Just a moment' challenge screen. An obfuscated inline script (hex-named identifiers, string-array rotator, self-defending wrapper) reconstructs a URL pointing to the external domain ofte.live, appends the current page's query parameters, and calls window.location.replace to navigate the browser to that destination. The file is HTML, not JavaScript that npm executes; installing or requiring the package does not run this code. There is no lifecycle script, no main-module code, no network activity at install or import time, and no read of installer-side environment or credential material. The package's only purpose is to serve the obfuscated Cloudflare-impersonating redirect if hosted, which is a client-side phishing landing pattern rather than a supply-chain payload against the installer.

Any computer that has this package installed or running should be considered fully compromised. All secrets and keys stored on that computer should be rotated immediately from a different computer. The package should be removed, but as full control of the computer may have been given to an outside entity, there is no guarantee that removing the package will remove all malicious software resulting from installing it.

Malicious versions

1 flagged

1.0.0

Indicators of compromise (SHA-256)

008b78f8f42d9e86e79a7dc0eff151b8a8d22137ed0f04170a01d65d66ea2916

20fb64bc6f1d195b61b422e1857f68a4f0d94133d7066d640db696b73a4364f5

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 dzvchorehui2 (version 1.0.0). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging dzvchorehui2 across your stack and pipelines.
If you installed it — respond
dzvchorehui2 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 dzvchorehui2 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 dzvchorehui2 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. dzvchorehui2 on npm has been identified as a malicious package (version 1.0.0 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-cj4c-xm2v-8m5gIN-MAL-2026-017419

References

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks dzvchorehui2-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