Malicious Code Injection in tiara-kue18-breki: A Threat to npm Ecosystem
Summary
MAL-2025-75635: Malicious code in tiara-kue18-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 'tiara-kue18-breki' is part of a larger campaign associated with the tea.xyz token reward system, which has been known to flood the npm ecosystem with malicious packages. These packages are designed to manipulate developer reputation scores by automatically generating and publishing numerous derivative packages with randomized names. This behavior not only affects the integrity of the npm registry but also poses a risk to developers who may unknowingly use these compromised packages.
Vulnerability Detail
The vulnerability in 'tiara-kue18-breki' originates from its malicious payload, which modifies the package.json file to remove private flags, alters version numbers, and generates random package names that are often themed around Indonesian culture. This manipulation leads to the continuous republishing of these variants, effectively polluting the npm registry and potentially compromising the security of applications that depend on these packages. The malicious scripts included in the package (such as auto.js and autopublish.js) are designed to automate this process, making it difficult for developers to detect and mitigate the threat.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall tiara-kue18-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 'tiara-kue18-breki' package and look for alternative packages that provide similar functionality without the associated risks. Always verify the integrity of packages before installation.
Conclusion
The 'tiara-kue18-breki' package presents a significant threat to the npm ecosystem due to its malicious code designed to manipulate package integrity and developer reputation. It is essential for developers to remain vigilant, regularly update their dependencies, and utilize tools like Vulert to monitor for vulnerabilities.
See every vulnerability recorded for tiara-kue18-breki →
FAQ
It is an npm package that is part of a malicious campaign aimed at inflating developer reputation scores through the automatic generation of derivative packages.
Using the 'tiara-kue18-breki' package can lead to security risks, including the potential for your application to be compromised or polluted with malicious code.
You should uninstall the package immediately using 'npm uninstall tiara-kue18-breki' and check your application for any other compromised packages.
You can use tools like Vulert, which monitors your package-lock.json file to alert you in real-time about open-source vulnerabilities in your software.
Yes, you can use the Vulert playground at Vulert Scanner to check if your application is affected without requiring any signup.
