Which versions of dzcvhfruwluwe are malicious?

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

How do I remediate dzcvhfruwluwe if I installed it?

Remove dzcvhfruwluwe from your project and lockfile, then assume any secrets accessible to the build or runtime were exposed: rotate API keys, tokens, and credentials, and audit for unexpected outbound activity or persistence.

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

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

Yes — dzcvhfruwluwe is associated with the GHSA-vfhv-rjx5-6c95, IN-MAL-2026-017413, IN-MAL-2026-017418 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 dzcvhfruwluwe 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 dzcvhfruwluwe (2 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging dzcvhfruwluwe across your stack and pipelines.

Malicious package

dzcvhfruwluwenpm

dzcvhfruwluwe is a confirmed malicious npm package (MAL-2026-13803) that executes malicious code on install (malicious versions 1.0.0, 1.0.1). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in dzcvhfruwluwe (npm)

MAL-2026-13803

Immediate action

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

npm uninstall dzcvhfruwluwe

What this malware does

The package's sole shipped file is index.html, a fake 'Cloudflare Verifying...' page containing an obfuscator.io-style script that reconstructs the URL https://lo<...>ofte.live/ and calls window.location.replace on a 1-second timeout to redirect the viewer to that external.live domain. package.json declares no lifecycle scripts and main points at the HTML file, so neither npm install nor require() executes the payload against the installing developer. The harm is browser-side: end users who somehow load the HTML are redirected to an attacker-controlled destination. This is registry abuse hosting phishing/malvertising content rather than a supply-chain attack against installers.

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

2 flagged

1.0.01.0.1

Indicators of compromise (SHA-256)

e60639d064659647979d4150c2b3e8b7d2ac8db4e2927ebc8fd89b7594ad5ef2

55737dced5f07dc382111a465247930f145efb1a87eaa51f99edc99c7e60eb8f

94746f13a653388ae268279888acdb3aceabbdbc5c7444e406af0dfb6317a6d9

Detection & response playbook

Malicious package

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for dzcvhfruwluwe (2 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging dzcvhfruwluwe across your stack and pipelines.
If you installed it — respond
Remove dzcvhfruwluwe from your project and lockfile, then assume any secrets accessible to the build or runtime were exposed: rotate API keys, tokens, and credentials, and audit for unexpected outbound activity or persistence.
Did it already run?
If dzcvhfruwluwe 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 dzcvhfruwluwe 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. dzcvhfruwluwe on npm has been identified as a malicious package (versions 1.0.0, 1.0.1 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-vfhv-rjx5-6c95IN-MAL-2026-017413IN-MAL-2026-017418

References

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks dzcvhfruwluwe-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the malicious outbound activity and severs the channel.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database