Which versions of fdhcvriwecv3 are malicious?

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

How do I remediate fdhcvriwecv3 if I installed it?

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

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

Yes — fdhcvriwecv3 is associated with the GHSA-jpxw-96xx-w7qx, IN-MAL-2026-017530 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 fdhcvriwecv3 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 fdhcvriwecv3 (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 fdhcvriwecv3 across your stack and pipelines.

Malicious package

fdhcvriwecv3npm

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

MAL-2026-13807

Immediate action

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

npm uninstall fdhcvriwecv3

What this malware does

The tarball contains only package.json and index.html. package.json declares main as index.html, and there are no preinstall/install/postinstall/prepare scripts. index.html mimics a Cloudflare 'Just a moment...' interstitial and runs obfuscated JavaScript inside a 1-second setTimeout that constructs a URL pointing at a '*.cloud.homes' host and calls window.location.replace() with the current query string forwarded. Because main points at HTML, the module cannot be loaded via require()/import, and no JavaScript executes at npm install time or when the package is required. The behavior only fires if a browser fetches index.html through a public npm CDN (unpkg/jsdelivr) — a CDN-abuse / phishing-hosting pattern that leverages npm as a redirector host, not a supply-chain attack against developers who install the package. No credentials are read, no network callbacks fire on install/import, and no code runs 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)

7314c00f6d8976ab86309f197f7b8aba1478cf9257e057a5fd9306f37e8f0e0b

c72894ed6ed82e4ebcbd83619b2a3f591c7dab355050fc1d43a62f90d384ee08

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 fdhcvriwecv3 (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 fdhcvriwecv3 across your stack and pipelines.
If you installed it — respond
fdhcvriwecv3 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 fdhcvriwecv3 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 fdhcvriwecv3 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. fdhcvriwecv3 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-jpxw-96xx-w7qxIN-MAL-2026-017530

References

Credits

Amazon Inspector · finder

Detect & block this

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