Malicious Code Detected in @sangith/eslint-config: Security Risk Alert
Summary
MAL-2025-6688: Malicious code in @sangith/eslint-config (npm). Affects @sangith/eslint-config 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 package @sangith/eslint-config is an npm package designed to provide a set of ESLint configurations for JavaScript projects. It aims to streamline the linting process by offering predefined rules and settings. However, this package has been identified as having a vulnerability that allows it to communicate with a domain associated with malicious activity, posing a risk to users who integrate it into their projects.
Vulnerability Detail
The vulnerability in @sangith/eslint-config arises from its communication with a domain linked to malicious activities. This could potentially lead to unauthorized data access, code injection, or other security breaches, compromising the integrity of applications that utilize this package. The issue was introduced in version 1.0.0 and remains a concern for developers relying on this package for their linting needs.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall @sangith/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 temporary workaround, consider removing the @sangith/eslint-config package from your project until a secure version is released. You can uninstall it using the following command: npm uninstall @sangith/eslint-config.
Conclusion
The @sangith/eslint-config package has been identified as having a significant vulnerability that allows it to communicate with a malicious domain. Developers should take immediate action to update or remove the package to protect their applications from potential security threats. Utilizing tools like Vulert can help in monitoring and managing open-source vulnerabilities effectively.
See every vulnerability recorded for @sangith/eslint-config →
FAQ
The vulnerability involves the package communicating with a domain associated with malicious activity, which can lead to security risks.
You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. Visit Vulert Scanner to check your application without needing to sign up.
If an immediate update is not possible, consider removing the package as a temporary measure to mitigate risks.
While specific exploits have not been detailed, the potential for unauthorized access and data breaches exists due to the package's malicious communication.
Utilize tools like Vulert to monitor your project's dependencies for vulnerabilities and receive real-time alerts.
