Malicious Code Injection in putri-tek11-breki: A Threat to npm Packages
Summary
MAL-2025-75059: Malicious code in putri-tek11-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
Habilume
Habit tracker with a companion that grows with you
Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent.
Background
The package 'putri-tek11-breki' is part of a series of npm packages associated with the tea.xyz token reward campaign. These packages are designed to inflate developer reputation scores by automatically generating and publishing derivative packages with randomized names. The malicious nature of this package lies in its ability to modify critical files and republish variants, thus polluting the npm registry.
Vulnerability Detail
The vulnerability originates from the package's malicious payload, which alters the package.json file by removing private flags and changing version numbers. It generates random Indonesian-themed package names and continuously republishes these variants, leading to potential security risks for developers who may unknowingly use these compromised packages. This behavior not only affects the integrity of the npm registry but also poses a risk to applications relying on these packages.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall putri-tek11-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 'putri-tek11-breki' package and look for alternative packages that provide similar functionality without the associated risks. Additionally, consider using tools like Vulert to monitor your project for vulnerabilities. You can check if your application is affected by this vulnerability using the Vulert playground at https://vulert.com/scanner without any signup.
Conclusion
The 'putri-tek11-breki' package poses a significant threat due to its malicious code that alters package files and repopulates the npm registry with compromised versions. It is essential to remove this package and monitor your projects for vulnerabilities to maintain security.
See every vulnerability recorded for putri-tek11-breki →
FAQ
The main issue is that it contains malicious code that modifies package.json files and republish variants to inflate developer reputation scores.
You can check your package-lock.json file or use tools like Vulert to monitor for vulnerabilities in your project.
You should uninstall the package immediately using 'npm uninstall putri-tek11-breki' and look for alternatives.
Yes, using this package can lead to security vulnerabilities in your application, as it modifies critical files and can introduce other malicious packages.
Regularly audit your dependencies, use tools like Vulert for real-time monitoring, and stay updated on security advisories related to npm packages.
Habilume
Habit tracker with a companion that grows with you
Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent.
