Skip to content
supplychainattack.orgSupply chain attack incident catalog
activecritical

Malware in fdhcvriwecv3

Malware discovered in the npm package fdhcvriwecv3. Systems with this package installed are considered fully compromised and require immediate remediation.

ShareXLinkedInHacker News
Disclosed
Last updated
Blast radius
Any system with the package installed or running
Ecosystems
Attack vectors
Affected entities
  • fdhcvriwecv3

A malicious npm package named fdhcvriwecv3 has been identified and published to the npm registry. The package contains malware that grants full control of affected systems to an outside entity.\n\nAny computer with this package installed or running should be considered fully compromised. The malware may provide persistent access beyond simple package removal. All secrets, keys, and credentials stored on affected systems should be rotated immediately from a different, uncompromised computer.\n\nWhile the package should be removed, removal alone may not eliminate all malicious software that resulted from the installation, as the attacker may have established additional persistence mechanisms.

Indicators of compromise

Packages
  • fdhcvriwecv3

Remediation

  • Immediately remove the fdhcvriwecv3 package from all systems
  • Rotate all secrets, keys, and credentials stored on affected computers from a different, uncompromised system
  • Perform a full security audit and malware scan of affected systems
  • Monitor affected systems for signs of unauthorized access or persistence mechanisms
  • Review system logs for any suspicious activity or lateral movement
  • Consider full system reimaging if compromise is confirmed

Sources

  1. GitHub Advisory GHSA-jpxw-96xx-w7qx · GitHub Advisory Database

Cite this entry

"Malware in fdhcvriwecv3." supplychainattack.org, Supply Chain Attack Incident Catalog. Disclosed August 12, 2026; last updated August 12, 2026. https://supplychainattack.org/incident/malware-in-fdhcvriwecv3-1jthk5

Suggest a correction

Found an error or have a newer source? Corrections to factual errors take priority over new entries.

  1. containedcritical

    Malicious code in 3-buildsight-web (npm)

    The npm package 3-buildsight-web contains malicious code that fetches and executes arbitrary JavaScript from a remote Bitbucket URL on module load, granting full page privileges to an unverified third party.

    npmCompromised package
  2. resolvedcritical

    Malicious code in @usaa-grp-personal-profile/personal-profile-common (npm)

    Malicious package @usaa-grp-personal-profile/personal-profile-common version 999.0.0 published to public npm as a dependency-confusion attack targeting an organization's internal registry. The package contains preinstall and postinstall hooks that exfiltrate hostname, username, and working directory to an attacker-controlled OAST endpoint on every install.

    npmDependency confusionCompromised package
  3. resolvedcritical

    Malicious code in create-coin (npm)

    create-coin@20.1.1 on npm contained malicious postinstall code that collected sensitive environment variables, credentials, and host reconnaissance data. The package impersonated an esbuild platform build and exfiltrated data to a hardcoded endpoint.

    npmCompromised packageTyposquatting
  4. resolvedcritical

    Malicious code in @syncraft-labs/vue (npm)

    The npm package @syncraft-labs/vue version 0.4.1 contained malicious obfuscated code in its ESM build that implements a blockchain-hosted C2 dropper (EtherHiding pattern), enabling remote code execution on any consumer importing the package.

    npmCompromised package