Critical Malicious Code Vulnerability in @thedelta/eslint-config Package
Summary
MAL-2025-191055: Malicious code in @thedelta/eslint-config (npm). Affects @thedelta/eslint-config versions 1.0.2. 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 @thedelta/eslint-config package is a configuration package for ESLint, a popular JavaScript linting tool that helps developers identify and fix problems in their JavaScript code. This package is intended to provide a standardized set of rules and configurations to ensure code quality and consistency across projects. However, it has been found to contain malicious code, posing significant security risks to any system where it is installed.
Vulnerability Detail
The vulnerability originates from the presence of embedded malicious code within the @thedelta/eslint-config package. This code can compromise any computer that has the package installed, potentially allowing unauthorized access to sensitive information such as secrets and keys. The malicious nature of the code means that simply removing the package may not eliminate all traces of the compromise, as full control of the affected system may have been handed over to an external entity.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall @thedelta/eslint-configIf 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 workaround, consider using alternative ESLint configuration packages that do not have known vulnerabilities. You can search for reputable ESLint configurations on npm or GitHub and install them using commands like 'npm install <alternative-package-name>'.
Conclusion
The discovery of malicious code in the @thedelta/eslint-config package poses a serious threat to users and their systems. Immediate action is required to remove the package and secure any sensitive information. Users are encouraged to explore alternative packages and utilize tools like Vulert for ongoing vulnerability monitoring.
See every vulnerability recorded for @thedelta/eslint-config →
FAQ
If you have installed the package, you should uninstall it immediately and rotate any sensitive information stored on the affected system.
You can use Vulert to monitor and alert for open-source vulnerabilities in your software. By analyzing your package-lock.json file, Vulert can provide real-time alerts. You can also check your application using the Vulert playground at Vulert Scanner without any signup.
After removing the package, it is crucial to rotate all secrets and keys stored on the compromised system. Additionally, consider running a security audit to identify any other potential vulnerabilities.
Failing to address this vulnerability can lead to unauthorized access to sensitive data, potential data breaches, and complete control of your system by malicious actors.
Yes, there are several alternative ESLint configuration packages available on npm. Research and choose a reputable package that meets your project's needs.
