Malicious Code Injection in putra-lengko13-breki: A Threat to npm Packages
Summary
MAL-2025-74935: Malicious code in putra-lengko13-breki (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 'putra-lengko13-breki' is part of the npm ecosystem and appears to be associated with a token reward campaign that has been flooding the npm registry. This package is designed to generate and publish derivative packages with randomized names, which can inflate developer reputation scores for token rewards. The malicious nature of this package poses significant risks to developers and the integrity of the npm registry.
Vulnerability Detail
The vulnerability in 'putra-lengko13-breki' originates from its malicious code that modifies the package.json file by removing private flags and changing version numbers. It generates random package names, often themed around Indonesian culture, and continuously republishes these variants to pollute the npm registry. This behavior can lead to reputation damage for developers and compromise the security of applications relying on these packages.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall putra-lengko13-brekiIf 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 avoid using the 'putra-lengko13-breki' package and consider using alternative packages that provide similar functionality without the associated risks. Additionally, you can monitor your package-lock.json file for any unauthorized changes.
Conclusion
The 'putra-lengko13-breki' package poses a significant security threat due to its malicious code that alters package configurations and floods the npm registry. It is essential for developers to remove this package and monitor their dependencies for vulnerabilities using tools like Vulert. Staying informed and proactive can help maintain the integrity of your applications.
See every vulnerability recorded for putra-lengko13-breki →
FAQ
The main risk is the injection of malicious code that can compromise the integrity of your application and lead to unauthorized changes in your project.
You can use Vulert, which monitors your package-lock.json file for vulnerabilities. Visit Vulert Scanner to check if your application is affected without needing to sign up.
Immediately remove the 'putra-lengko13-breki' package from your project and check for any unauthorized changes in your package.json and package-lock.json files.
Yes, consider using other reputable npm packages that offer similar functionality without the risks associated with malicious code.
Vulert uses your package-lock.json file to monitor and alert you in real-time for open-source vulnerabilities, ensuring your application remains secure.
