Which versions of csbcldfvivwfgd4 are malicious?

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

How do I remediate csbcldfvivwfgd4 if I installed it?

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

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

Yes — csbcldfvivwfgd4 is associated with the GHSA-5pjw-x44v-j286, IN-MAL-2026-017534 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 csbcldfvivwfgd4 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 csbcldfvivwfgd4 (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 csbcldfvivwfgd4 across your stack and pipelines.

Malicious package

csbcldfvivwfgd4npm

csbcldfvivwfgd4 is a confirmed malicious npm package (MAL-2026-13795) 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 csbcldfvivwfgd4 (npm)

MAL-2026-13795

Immediate action

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

npm uninstall csbcldfvivwfgd4

What this malware does

The package contains a single index.html declared as main. The HTML mimics a Cloudflare 'Just a moment...' challenge and contains obfuscator.io-style control-flow-obfuscated JavaScript that constructs a redirect URL from a rotated string array and calls window.location.replace(targetUrl). There are no lifecycle scripts (preinstall/install/postinstall/prepare) and main pointing at an HTML file means require() cannot load it, so nothing runs on npm install or on import in a Node.js developer/build environment. The harmful behavior only fires when the HTML is fetched by a browser via an npm-backed CDN (unpkg/jsdelivr) and rendered — i.e., abuse of the npm registry as a hosting/CDN for a phishing or malvertising redirect page targeting browser end-users, not developers who install the package. Under this system's installer-centric threat model, installing or requiring this package produces no exfiltration, no code execution, no credential access, and no persistence on the installer's machine.

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)

0ec0ff2d2bfc91e5432374bb1673cdb2a9de424bcfc1474052593f16607d6320

f6d7db017a0499c0fca67cc331c44fa736fe52568177990823cb17bd03ceee21

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 csbcldfvivwfgd4 (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 csbcldfvivwfgd4 across your stack and pipelines.
If you installed it — respond
csbcldfvivwfgd4 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 csbcldfvivwfgd4 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 csbcldfvivwfgd4 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. csbcldfvivwfgd4 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-5pjw-x44v-j286IN-MAL-2026-017534

References

Credits

Amazon Inspector · finder

Detect & block this

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