Malicious code in classnames-benchmarks (npm)
Summary
MAL-2023-8453: Malicious code in classnames-benchmarks (npm). Affected versions are not published. No fix is published. How to fix ↓
Check if this vulnerability affects your application
Upload a manifest or SBOM and we'll show whether you're affected, plus every other risky package in the same scan.
No signup required · Results in about 60 seconds
Background
The classnames-benchmarks package is an npm package used for benchmarking the performance of the classnames library. It is commonly used in JavaScript projects to generate CSS class names dynamically. The package allows developers to efficiently manage class names in their codebase. However, a vulnerability has been discovered in the package that exposes users to malicious code.
Vulnerability Detail
The vulnerability in the classnames-benchmarks package is due to the presence of malicious code. This code can compromise the security of any computer that has the package installed or running. Once installed, the malicious code gives full control of the computer to an external entity, potentially exposing all secrets and keys stored on that computer. Removing the package may not guarantee the removal of all malicious software installed as a result of its installation. Therefore, immediate action is required to rotate all affected secrets and keys from a different computer.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall classnames-benchmarksIf it arrived as a transitive dependency, remove the package that pulled it in, then reinstall.
Tip — Not sure whether your app is affected? Vulert can check the versions your app actually runs. Scan free →
Workaround
There is no specific workaround mentioned for this vulnerability. However, it is crucial to follow the steps mentioned in the 'how_to_fix' section to mitigate the risk and ensure the security of the affected computer.
Conclusion
The classnames-benchmarks package has been found to contain malicious code, posing a significant security risk to any computer with the package installed or running. It is crucial to take immediate action by rotating affected secrets and keys, removing the package, and conducting a security audit. For further support and assistance in vulnerability remediation, please contact DevNack.com.
See every vulnerability recorded for classnames-benchmarks →
FAQ
The classnames-benchmarks package is an npm package used for benchmarking the performance of the classnames library in JavaScript projects.
The vulnerability exposes the affected computer to malicious code, potentially compromising all secrets and keys stored on that computer.
To fix the vulnerability, rotate all affected secrets and keys from a different computer, remove the classnames-benchmarks package, and conduct a security audit.
There is no specific workaround mentioned for this vulnerability. Following the recommended steps to fix the vulnerability is crucial.
After removing the classnames-benchmarks package, it is recommended to conduct a thorough security audit to ensure no other malicious software or code is present on the affected computer.
