fdhcvriwecv3
Affected
- introduced
0(semver)
Fixed versions
None listed
Fix
No fixed version is listed.
Advisory
Also known as: GHSA-jpxw-96xx-w7qx
Malicious package Its source marks this package as malicious: it is not a vulnerability in a legitimate one.
Malicious code in fdhcvriwecv3 (npm)
---
_-= Per source details. Do not edit below this line.=-_
Source: amazon-inspector (c72894ed6ed82e4ebcbd83619b2a3f591c7dab355050fc1d43a62f90d384ee08)
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.
Source: ghsa-malware (7314c00f6d8976ab86309f197f7b8aba1478cf9257e057a5fd9306f37e8f0e0b)
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.
Not rated by the source.
0 (semver)None listed
No fixed version is listed.
Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.
Check your own computer: guard packages check
Source: OpenSSF Malicious Packages · Apache-2.0