Skip to content
supplychainattack.orgSupply chain attack incident catalog
containedcritical

Malware in @content-editor/common

Malware was discovered in the npm package @content-editor/common. Systems with this package installed or running 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
  • @content-editor/common

A malware incident was identified in the npm package @content-editor/common, published on GitHub's advisory database. Any computer with this package installed or running should be considered fully compromised.\n\nThe advisory recommends immediate action: all secrets and keys stored on affected computers should be rotated from a different, uncompromised system. The package should be removed, though complete removal of all malicious artifacts cannot be guaranteed given the level of system compromise.\n\nThis represents a critical supply chain attack through a compromised npm package with potential for widespread impact across all systems that installed or executed the affected code.

Indicators of compromise

Packages
  • @content-editor/common

Remediation

  • Immediately isolate any system that has installed or run @content-editor/common
  • Rotate all secrets, API keys, and credentials from a different, uncompromised computer
  • Remove the @content-editor/common package from all systems
  • Conduct a full security audit and forensic analysis of affected systems
  • Monitor for signs of persistent malware or unauthorized access
  • Review all system logs and network traffic for suspicious activity during the period the package was installed

Sources

  1. GitHub Advisory GHSA-wwc7-v7xr-q4pc · GitHub Advisory Database

Cite this entry

"Malware in @content-editor/common." supplychainattack.org, Supply Chain Attack Incident Catalog. Disclosed June 29, 2026; last updated June 29, 2026. https://supplychainattack.org/incident/malware-in-content-editor-common-17wbko

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