Skip to content
supplychainattack.orgSupply chain attack incident catalog
activecritical

Malware in npmjs_web3-common

Malware was discovered in the npm package web3-common. Systems with this package installed are considered fully compromised and require immediate remediation including secret rotation and package removal.

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

A malicious package named web3-common was published to npm. According to the GitHub Advisory (GHSA-56rf-jfpx-gqf8), any computer with this package installed or running should be considered fully compromised.\n\nThe advisory recommends that all secrets and keys stored on affected computers be rotated immediately from a different, uncompromised system. While the package should be removed, there is no guarantee that removal will eliminate all malicious software that may have been installed as a result of the compromise.\n\nThis appears to be a typosquatting or direct package compromise attack targeting users of the web3 ecosystem.

Indicators of compromise

Packages
  • web3-common

Remediation

  • Immediately rotate all secrets and keys from a different, uncompromised computer
  • Remove the web3-common package from all affected systems
  • Audit system logs for unauthorized access or activity during the period the package was installed
  • Consider the affected system(s) as potentially fully compromised and plan for complete rebuild if handling sensitive data
  • Check for any other suspicious packages or modifications on affected systems

Sources

  1. GitHub Advisory GHSA-56rf-jfpx-gqf8 · GitHub Advisory Database

Cite this entry

"Malware in npmjs_web3-common." supplychainattack.org, Supply Chain Attack Incident Catalog. Disclosed June 10, 2026; last updated June 10, 2026. https://supplychainattack.org/incident/malware-in-npmjs-web3-common-8ov584

Suggest a correction

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

  1. activecritical

    Malware in chain-manager

    Malware discovered in the npm package chain-manager. Systems with this package installed or running are considered fully compromised and require immediate remediation.

    npmCompromised package
  2. containedcritical

    Malicious code in @finxsecdemo/utils (npm)

    The npm package @finxsecdemo/utils version 1.0.2 was identified as malicious by the OpenSSF Package Analysis project. The package communicates with a domain associated with malicious activity.

    npmCompromised package
  3. containedcritical

    Malware in @bowozzz/baileys

    The npm package @bowozzz/baileys contained malware that grants full system compromise to attackers. Any computer with this package installed should be considered fully compromised and all secrets and keys rotated immediately from a different machine.

    npmCompromised package
  4. containedcritical

    Malicious code in blots (npm)

    The npm package 'blots' version 2.1.0 was identified by the OpenSSF Package Analysis project as containing malicious code that executes commands associated with malicious behavior. The package has been flagged in the OpenSSF malicious packages database.

    npmCompromised package