Which versions of cvbniydplwe3 are malicious?

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

How do I remediate cvbniydplwe3 if I installed it?

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

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

Yes — cvbniydplwe3 is associated with the GHSA-x9wp-p3fp-f3rm, IN-MAL-2026-017503 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 cvbniydplwe3 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 cvbniydplwe3 (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 cvbniydplwe3 across your stack and pipelines.

Malicious package

cvbniydplwe3npm

cvbniydplwe3 is a confirmed malicious npm package (MAL-2026-13797) that executes malicious code on install (malicious version 1.0.0). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in cvbniydplwe3 (npm)

MAL-2026-13797

Immediate action

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

npm uninstall cvbniydplwe3

What this malware does

The tarball contains only index.html (declared as package.json main) and no JavaScript, no lifecycle scripts, and no Node-executable entry point. index.html renders a fake 'Just a moment...' Cloudflare Turnstile interstitial; on the Turnstile callback, an obfuscated string-array deobfuscator reconstructs a target URL and assigns it to window.location. HTML cannot be require()'d and there are no preinstall/install/postinstall hooks, so npm install and require('cvbniydplwe3') do not execute this code on the installer's machine. The behavior is a browser-side redirect that would only fire if the HTML were served from a CDN and loaded in a browser. This appears to be npm-registry abuse — parking phishing/redirect content in a package slot — 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

1 flagged

1.0.0

Indicators of compromise (SHA-256)

89d1281e19ef4d5ea3bd76638c1ea282c09b0a07d97ecf03131e950d5b9997b2

9edbef37139b40a366aacea90abbd4b80ca581921f213b98ffb17db3b857bfcd

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 cvbniydplwe3 (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 cvbniydplwe3 across your stack and pipelines.
If you installed it — respond
Remove cvbniydplwe3 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 cvbniydplwe3 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 cvbniydplwe3 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. cvbniydplwe3 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-x9wp-p3fp-f3rmIN-MAL-2026-017503

References

Credits

Amazon Inspector · finder

Detect & block this

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