Which versions of vkldhcmieru6 are malicious?

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

How do I remediate vkldhcmieru6 if I installed it?

vkldhcmieru6 is a typosquat — you almost certainly intended a legitimately-named package. Remove vkldhcmieru6, install the correct package, and rotate any secrets exposed during the install since post-install scripts may have already run.

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

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

Yes — vkldhcmieru6 is associated with the GHSA-6m3r-x867-rw6g, IN-MAL-2026-017523 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 vkldhcmieru6 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 vkldhcmieru6 (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 vkldhcmieru6 across your stack and pipelines.

Malicious package

vkldhcmieru6npm

vkldhcmieru6 is a confirmed malicious npm package (MAL-2026-13841) that typosquats a legitimate package to trick installs (malicious version 1.0.0). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in vkldhcmieru6 (npm)

MAL-2026-13841

Immediate action

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

npm uninstall vkldhcmieru6

What this malware does

The package contains only index.html (declared as main in package.json) and a minimal package.json with no lifecycle scripts. The HTML impersonates a Cloudflare Turnstile 'Just a moment...' challenge and, on Turnstile completion, runs an obfuscator.io-style routine (rotated string array _0x81b7 decoded via _0x28d7) to reconstruct a destination URL and navigates the browser to it via window.location, forwarding the visitor's query string. There is no preinstall/install/postinstall hook, no importable JavaScript entry point, and Node cannot require() an HTML file, so installing or requiring the package does not execute any code on the installer's machine. The harm is directed at browser visitors of the hosted HTML content, not at npm developers or build systems that install this package.

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)

87966821ed013ccb8c027a23f6eadf2efdbab5584d1b74f5180753ee06c30004

25890a37fa8da48d2dc2868e010cef8cb3427faa42218cec4b858ac82db679d7

Detection & response playbook

Typosquat

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for vkldhcmieru6 (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 vkldhcmieru6 across your stack and pipelines.
If you installed it — respond
vkldhcmieru6 is a typosquat — you almost certainly intended a legitimately-named package. Remove vkldhcmieru6, install the correct package, and rotate any secrets exposed during the install since post-install scripts may have already run.
Did it already run?
If vkldhcmieru6 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 vkldhcmieru6 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. vkldhcmieru6 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-6m3r-x867-rw6gIN-MAL-2026-017523

References

Credits

Amazon Inspector · finder

Detect & block this

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