Malicious Code Injection in lonely_cod-strongdev: A Threat to npm Users
Summary
MAL-2025-105306: Malicious code in lonely_cod-strongdev (npm). Affected versions are not published. 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 lonely_cod-strongdev is part of the npm ecosystem, which is widely used for JavaScript package management. This package has been identified as part of a malicious campaign that aims to inflate developer reputation scores through the generation of derivative packages. It is designed to automatically publish variants of itself, which can lead to pollution of the npm registry and potential security risks for users who inadvertently install these packages.
Vulnerability Detail
The vulnerability originates from the malicious intent behind the lonely_cod-strongdev package, which modifies the package.json file to remove private flags and alters version numbers. It generates random package names, often themed around Indonesian culture, and continuously republishes these variants. This behavior not only compromises the integrity of the npm registry but also poses a risk to developers who may unknowingly install these malicious packages, leading to potential exploitation of their applications.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall lonely_cod-strongdevIf 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 measure, you can avoid using the lonely_cod-strongdev package and instead look for alternative packages that provide similar functionality without the associated risks. Regularly audit your package dependencies to ensure they are secure.
Conclusion
The lonely_cod-strongdev package poses a significant risk due to its malicious code designed to manipulate the npm registry. Developers are advised to remove this package and remain vigilant about their dependencies. Utilizing tools like Vulert can aid in identifying vulnerabilities and maintaining secure software.
See every vulnerability recorded for lonely_cod-strongdev →
FAQ
The malicious code modifies package.json files, removes private flags, and generates random package names to inflate developer reputation scores.
You can use tools like Vulert, which monitors and alerts for open-source vulnerabilities in your software. By analyzing your package-lock.json, it can help identify affected packages.
You should uninstall the package immediately using 'npm uninstall lonely_cod-strongdev' and check your project for any other potentially malicious packages.
While the primary exploit involves the pollution of the npm registry, the risk lies in developers unknowingly using compromised packages that could lead to further security issues.
Regularly audit your dependencies, use trusted sources for packages, and consider employing tools like Vulert to monitor for vulnerabilities in real-time.
