Critical Malicious Code Vulnerability in @viapip/eslint-config Package
Summary
MAL-2025-191329: Malicious code in @viapip/eslint-config (npm). Affects @viapip/eslint-config versions 0.2.4. 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 @viapip/eslint-config package is an npm package designed to provide a set of ESLint configurations for JavaScript projects. It aims to streamline the process of setting up linting rules, ensuring code quality and consistency across development teams. However, this package has been compromised, leading to severe security vulnerabilities that can affect any system where it is installed.
Vulnerability Detail
The vulnerability stems from a malicious payload embedded within the @viapip/eslint-config package, which was compromised by the Sha1-Hulud: The Second Coming NPM worm. This worm is designed to steal tokens and credentials, publishing them to GitHub. It can also propagate itself to other NPM packages owned by the user and establish persistence through GitHub actions. Furthermore, the worm has the potential to destroy the user's home directory, making it a critical threat to system integrity and security.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall @viapip/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
There are no effective workarounds to mitigate the risks posed by this vulnerability other than removing the package and ensuring that no remnants of the malicious code remain on the system.
Conclusion
The @viapip/eslint-config package has been compromised, leading to a critical vulnerability that can severely impact system security. Immediate action is required to remove the package and secure any affected systems. Utilizing tools like Vulert can help in monitoring and preventing such vulnerabilities in the future.
See every vulnerability recorded for @viapip/eslint-config →
FAQ
You should immediately uninstall the package and rotate any secrets or keys stored on your system.
You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. Check your application using the Vulert playground at Vulert Scanner.
The consequences include unauthorized access to sensitive information, potential destruction of files, and propagation of the malicious code to other packages.
Recovery involves removing the malicious package, rotating all credentials, and restoring any lost data from backups.
Regularly audit your dependencies, use tools like Vulert for monitoring, and stay updated on security advisories related to the packages you use.
