Malicious Code Injection in putri-tempe10-breki: A Threat to npm Ecosystem
Summary
MAL-2025-75063: Malicious code in putri-tempe10-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 'putri-tempe10-breki' is part of the npm ecosystem, which is widely used for JavaScript package management. This package is associated with the tea.xyz token reward campaign, which has been known to flood the npm registry with malicious packages. These packages often contain scripts designed to manipulate package metadata and inflate developer reputation scores, posing significant risks to users and the integrity of the npm registry.
Vulnerability Detail
The vulnerability in 'putri-tempe10-breki' originates from its malicious code that modifies the package.json file. It removes private flags, alters version numbers, and generates random package names, leading to the continuous republishing of these variants. This behavior not only pollutes the npm registry but also compromises the security of applications that depend on this package, potentially allowing for further exploitation.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall putri-tempe10-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 measure, you can avoid using the 'putri-tempe10-breki' package and replace it with a trusted alternative. Always verify the integrity and source of packages before installation.
Conclusion
The 'putri-tempe10-breki' package poses a significant threat to the npm ecosystem due to its malicious code that manipulates package metadata. It is crucial for developers to remove this package from their projects and to adopt best practices for dependency management to safeguard their applications.
See every vulnerability recorded for putri-tempe10-breki →
FAQ
The malicious code can lead to unauthorized modifications of your project's package.json, potentially compromising your application's security and integrity.
You can use tools like Vulert to monitor your package-lock.json for vulnerabilities. Visit Vulert Scanner to check if your application is affected without any signup.
Immediately uninstall the package using 'npm uninstall putri-tempe10-breki' and review your project's dependencies for any other potentially malicious packages.
Yes, consider using well-established and trusted packages that provide similar functionality without the associated risks.
Regularly audit your dependencies, use tools like Vulert for real-time monitoring, and only install packages from reputable sources.
