Malicious code in noelc-css-blender (npm)
Affects noelc-css-blenderSource GCVE Database
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| npmnoelc-css-blender | Affected– | Fixed in– |
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
Description
The noelc-css-blender npm package contains malicious code that compromises any computer on which it is installed or run. The compromise is severe enough that all secrets and keys stored on the affected machine should be rotated immediately from a different, trusted device. Removing the package alone does not guarantee removal of all malicious software or backdoors introduced by this package.
Impact
Full system compromise on any computer with the package installed or running. Exposure of all stored secrets and keys on the affected machine, requiring immediate rotation from a different computer. Potential persistence of malicious software beyond the package itself.
Defensive guidance
Immediately remove the noelc-css-blender package from affected systems. Rotate all secrets and keys stored on the compromised machine from a separate, trusted device. Conduct a thorough investigation and remediation of the affected system to identify and remove any additional malicious software or backdoors introduced by the package.
Summary
The noelc-css-blender package on npm has been identified as containing malicious code. Installation or execution of this package results in a full compromise of the affected system, potentially allowing an attacker complete control. Due to the severity of the compromise, all credentials and secrets stored on the machine should be considered exposed and rotated from a separate, secure system. The package removal is necessary but insufficient to fully remediate the infection, as additional malicious software may persist.