Malicious Code Injection in putra-ubi60-breki: A Threat to npm Packages
Summary
MAL-2025-74960: Malicious code in putra-ubi60-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-ubi60-breki' is part of a series of npm packages that have been identified as part of a malicious campaign aimed at manipulating developer reputation scores through the tea.xyz token reward system. These packages are designed to automatically generate and publish derivative packages with randomized names, which can lead to pollution of the npm registry and compromise the integrity of the ecosystem.
Vulnerability Detail
The vulnerability in 'putra-ubi60-breki' stems from its inclusion in a malicious campaign that modifies the package.json file to remove private flags, alters version numbers, and generates random package names. This behavior is orchestrated through autopublish scripts that continuously republish variants, leading to potential security risks and a polluted npm registry. The origin of this vulnerability is linked to the tea.xyz token reward campaign, which exploits npm's publishing mechanisms.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall putra-ubi60-breki
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 avoid using the 'putra-ubi60-breki' package and consider alternative packages that provide similar functionality without the associated risks. Additionally, you can monitor your project for any unauthorized changes to package.json and other critical files.
Conclusion
The 'putra-ubi60-breki' package poses a significant threat due to its malicious code designed to manipulate npm's publishing system. It is crucial for developers to be aware of such vulnerabilities and take proactive measures to secure their projects. Regular monitoring and auditing of dependencies can help mitigate risks associated with malicious packages.
See every vulnerability recorded for putra-ubi60-breki →
FAQ
The malicious code modifies package.json to remove private flags and changes version numbers, allowing for unauthorized republishing of the package.
You can use Vulert, which monitors and alerts for open-source vulnerabilities in your software by analyzing package-lock.json. You can check your application for vulnerabilities using the Vulert playground without any signup.
Using this package can lead to security risks, including unauthorized access to your project and pollution of the npm registry, which can affect other developers.
Regularly audit your dependencies and use tools like Vulert to monitor for vulnerabilities. Additionally, avoid using packages from untrusted sources.
Remove the package immediately and monitor your project for any unauthorized changes. Consider using alternative packages that are well-reviewed and trusted.