Malware in @contentprod-authoring/block-manager
Malware was discovered in the npm package @contentprod-authoring/block-manager. Systems with this package installed are considered fully compromised and require immediate remediation.
- Disclosed
- Last updated
- Blast radius
- Any system with the package installed or running
- Ecosystems
- Attack vectors
- Affected entities
- @contentprod-authoring/block-manager
A malicious version of the npm package @contentprod-authoring/block-manager was 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 have provided attackers with access to secrets, keys, and other sensitive data stored on affected systems.\n\nRemoval of the package does not guarantee removal of all malicious software, as the attacker may have established additional persistence mechanisms during the compromise. Full system remediation is required."
Indicators of compromise
- Packages
- @contentprod-authoring/block-manager
Remediation
- Immediately rotate all secrets and keys from a clean, unaffected computer
- Remove the @contentprod-authoring/block-manager package from all systems
- Conduct a full forensic investigation of affected systems for additional malware or persistence mechanisms
- Review system logs and network traffic for signs of unauthorized access or data exfiltration
- Consider full system reimaging if the compromise is confirmed to be widespread
Sources
- GitHub Advisory GHSA-cpfg-m96g-j4j9 · GitHub Advisory Database
Cite this entry
"Malware in @contentprod-authoring/block-manager." supplychainattack.org, Supply Chain Attack Incident Catalog. Disclosed June 29, 2026; last updated June 29, 2026. https://supplychainattack.org/incident/malware-in-contentprod-authoring-block-manager-ojrss1
Suggest a correction
Found an error or have a newer source? Corrections to factual errors take priority over new entries.
Related incidents
- containedcritical
Malicious code in crypto-javas (npm)
The npm package crypto-javas contains malicious code in its postinstall hook and main entrypoint that harvests environment variables (including CI secrets like AWS_*, GITHUB_TOKEN, NPM_TOKEN) and exfiltrates them to an attacker-controlled backend. The package is presented deceptively as @wizlabs/js-crypto with a placeholder repository.
npmCompromised packageTyposquatting - containedcritical
Malicious code in flydev (npm)
The npm package flydev contains malicious code designed to destroy Windows systems. The package masquerades as a utility but executes destructive operations including filesystem deletion, process termination, memory exhaustion, and fork bombs when invoked.
npmCompromised package - resolvedcritical
Malicious code in ranux-dev (npm)
ranux-dev, an npm package, contained malicious code that substituted a popular WhatsApp library dependency with arbitrary code from an unaffiliated GitHub account. The package was heavily obfuscated and designed to harvest WhatsApp sessions and credentials from installers.
npmCompromised packageDependency confusion - containedcritical
Malicious code in npm-wold (npm)
npm-wold@1.1.1 contains malicious code in its postinstall script that fetches remote JSON from a hardcoded endpoint and dynamically invokes attacker-controlled functions with attacker-supplied arguments, enabling code execution at install time.
npmCompromised package