Skip to content
supplychainattack.orgSupply chain attack incident catalog
activecritical

Malware in @contenteditor-shared/content-editor-common

Malware discovered in the npm package @contenteditor-shared/content-editor-common. 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
  • @contenteditor-shared/content-editor-common

A malicious package, @contenteditor-shared/content-editor-common, was published to npm and contains malware. Any computer with this package installed or running should be considered fully compromised.\n\nThe malware grants full control of affected systems to an outside entity. All secrets and keys stored on compromised computers must be rotated immediately from a different, unaffected system.\n\nWhile the package should be removed, complete removal of all malicious software cannot be guaranteed due to the level of system compromise. A full security audit and potential system rebuild may be necessary for affected users.

Indicators of compromise

Packages
  • @contenteditor-shared/content-editor-common

Remediation

  • Immediately remove the @contenteditor-shared/content-editor-common package from all systems
  • Rotate all secrets, API keys, and credentials from a different, unaffected computer
  • Conduct a full security audit of any system that had this package installed
  • Consider rebuilding affected systems from clean media if full compromise is suspected
  • Check for any unauthorized access or lateral movement in your infrastructure
  • Monitor for indicators of compromise on affected systems

Sources

  1. GitHub Advisory GHSA-3v59-3pc3-p6qm · GitHub Advisory Database

Cite this entry

"Malware in @contenteditor-shared/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-contenteditor-shared-content-editor-common-2mr0wz

Suggest a correction

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

  1. resolvedcritical

    Malicious code in autbank-core (npm)

    The npm package autbank-core contained malicious preinstall and postinstall lifecycle hooks that exfiltrated environment variables, credentials, and system information to a hardcoded webhook.site endpoint during installation.

    npmCompromised package
  2. resolvedcritical

    Malicious code in adxaa (npm)

    The npm package adxaa contained obfuscated malicious JavaScript designed to target users of a specific WordPress site. The payload exfiltrates session data, deletes accounts, and hijacks credentials via email overwrite and password reset.

    npmCompromised package
  3. resolvedcritical

    Malicious code in upload-to-gcp (npm)

    upload-to-gcp@3.2.1 (npm) contains malicious code in its postinstall script that exfiltrates host identifiers to an attacker-controlled endpoint. The package masquerades as a Google Cloud Platform utility but performs unauthorized telemetry collection at install time.

    npmCompromised package
  4. resolvedcritical

    Malicious code in akamai-sensor (npm)

    A malicious npm package named akamai-sensor impersonated Akamai's legitimate sensor_data anti-bot SDK. The package contained hidden JavaScript code concealed using invisible Unicode characters and implemented a dynamic command-and-control channel via a Google Calendar dead-drop, enabling arbitrary code execution on installation.

    npmCompromised packageTyposquatting