Malicious Code Detected in dessandro-classie: A Security Alert
Summary
MAL-2025-6921: Malicious code in dessandro-classie (npm). Affects dessandro-classie versions >= 1.0.0. 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 'dessandro-classie' package is a utility library for managing CSS class names in JavaScript applications. It simplifies the process of adding, removing, and toggling classes on HTML elements. However, it has been found to communicate with a domain linked to malicious activities, raising significant security concerns for users relying on this package.
Vulnerability Detail
The vulnerability arises from the package's communication with a domain associated with malicious activity. This could potentially lead to data breaches, unauthorized access, or the execution of harmful scripts within applications that utilize this package. The issue was introduced in version 1.0.0 and remains a critical concern for developers who may unknowingly expose their applications to risks.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall dessandro-classieIf 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
As a temporary workaround, consider removing the 'dessandro-classie' package from your project and replacing it with an alternative library that does not have known vulnerabilities. This can be done by running: 'npm uninstall dessandro-classie'.
Conclusion
The 'dessandro-classie' package has been identified with a serious vulnerability due to its communication with a malicious domain. It is crucial for developers to take immediate action by updating or replacing the package to safeguard their applications from potential threats.
See every vulnerability recorded for dessandro-classie →
FAQ
The vulnerability involves the package communicating with a domain linked to malicious activities, posing risks to applications using it.
You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. Visit the Vulert playground at Vulert Scanner to check your application without needing to sign up.
If an immediate update is not possible, consider removing the package and using an alternative library until a secure version is available.
Yes, continuing to use the vulnerable package may expose your application to data breaches and unauthorized access, which can lead to data loss.
You can find more information about the package on its GitHub repository or the npm package page.
