Malicious Code Detected in packaging-common (npm) - Version 7.7.8
Summary
MAL-2025-6803: Malicious code in packaging-common (npm). Affects packaging-common versions 7.7.8. 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 'packaging-common' package is a widely used library in the npm ecosystem, designed to facilitate various packaging tasks for JavaScript applications. It provides essential functionalities that developers rely on for efficient package management. However, version 7.7.8 has been flagged for containing malicious code, which poses significant risks to users and their applications.
Vulnerability Detail
The vulnerability in 'packaging-common' version 7.7.8 originates from its communication with a domain associated with malicious activities. This behavior can lead to unauthorized data access, potential data breaches, and compromise the integrity of applications utilizing this package. The malicious code could be exploited by attackers to execute harmful operations within the user's environment.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall packaging-common
If 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, you can remove the 'packaging-common' package from your project until a secure version is confirmed. Use the following command to uninstall it: npm uninstall packaging-common.
Conclusion
The discovery of malicious code in 'packaging-common' version 7.7.8 highlights the importance of vigilance in package management. Users are encouraged to update to the latest version and utilize tools like Vulert to monitor their applications for vulnerabilities effectively.
See every vulnerability recorded for packaging-common →
FAQ
The malicious activity involves the package communicating with a domain known for harmful operations, which can lead to security breaches.
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.
If immediate updates are not possible, consider removing the package temporarily as a workaround until a secure version is available.
Currently, version 7.7.8 is specifically identified as malicious. It is advisable to monitor for any updates or advisories regarding other versions.
Vulert uses the package-lock.json file to monitor and alert users in real-time about open-source vulnerabilities, ensuring that developers are informed of potential risks.