Critical Malicious Code Vulnerability in @didi-pebble/pblint Package
Summary
MAL-2025-5852: Malicious code in @didi-pebble/pblint (npm). Affects @didi-pebble/pblint versions 1.0.0 – 99.9.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 @didi-pebble/pblint package is a tool designed for linting and ensuring code quality in JavaScript projects. It is part of the npm ecosystem, which is widely used for managing JavaScript packages. However, this package has been identified as containing malicious code that compromises the security of systems where it is installed.
Vulnerability Detail
The vulnerability stems from the presence of embedded malicious code within the @didi-pebble/pblint package. This code can lead to a complete compromise of any computer that has the package installed, allowing unauthorized access to sensitive information such as secrets and keys. The malicious nature of the code is classified under CWE-506, indicating that it appears to be harmful and can result in significant security breaches.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall @didi-pebble/pblintIf 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, you should consider using alternative linting tools that do not have known vulnerabilities. Additionally, ensure that your development environment is secure and monitor for any unauthorized access.
Conclusion
The @didi-pebble/pblint package has been identified as containing malicious code, posing a significant security risk to systems where it is installed. Immediate action is required to remove the package and secure any compromised systems. Utilizing tools like Vulert can help monitor for such vulnerabilities in the future.
See every vulnerability recorded for @didi-pebble/pblint →
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. Visit Vulert Scanner to check your application without any signup.
Keeping this package can lead to unauthorized access to your system, potentially compromising sensitive data and allowing malicious actors to control your environment.
Regularly audit your dependencies, use tools like Vulert for monitoring, and stay updated with security advisories related to the packages you use.
CWE-506 indicates that the code within the package is malicious in nature, which is critical for understanding the potential impact and urgency of addressing the vulnerability.
