Malicious Code Detected in Deresicl Package (npm)
Summary
MAL-2025-18300: Malicious code in deresicl (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
Deresicl is an npm package designed for [insert functionality here, e.g., data manipulation, web scraping, etc.]. It is utilized by developers for its [insert key attributes, e.g., ease of use, performance, etc.]. However, recent findings have revealed that this package contains malicious code, posing significant risks to applications that rely on it.
Vulnerability Detail
The vulnerability in the deresicl package stems from the inclusion of malicious code that can compromise the security of applications using it. This code may lead to unauthorized access, data breaches, or other harmful effects. The issue was introduced in version 0 and affects all subsequent versions, making it critical for users to address this vulnerability promptly.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall deresiclIf 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 deresicl package from your project until a secure version is released. You can do this by executing the command: 'npm uninstall deresicl'. This will help mitigate the risk of exposure to the malicious code.
Conclusion
The discovery of malicious code in the deresicl package highlights the importance of regularly monitoring and updating dependencies in software projects. Users are urged to take immediate action to mitigate risks associated with this vulnerability.
See every vulnerability recorded for deresicl →
FAQ
The malicious code can lead to unauthorized access and potential data breaches, compromising the security of applications that utilize the package.
You can use Vulert, which monitors and alerts for open-source vulnerabilities in your software. By simply analyzing your package-lock.json file, Vulert can provide real-time alerts regarding vulnerabilities.
Yes, you can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without requiring any signup.
If an immediate update is not possible, consider removing the package from your project as a temporary measure to avoid exposure to the malicious code.
Detailed information about the vulnerability can be found in the GitHub repository of the malicious packages, specifically at https://github.com/ossf/malicious-packages/blob/main/osv/malicious/npm/deresicl/MAL-2025-18300.json.
