Malicious Code Injection in tiara-lapis1-breki: A Threat to npm Packages
Summary
MAL-2025-75638: Malicious code in tiara-lapis1-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-lapis1-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 linked to a series of malicious activities aimed at inflating developer reputation scores. The package's functionality is compromised by malicious scripts that manipulate its metadata and behavior, posing a significant risk to users and the integrity of the npm registry.
Vulnerability Detail
The vulnerability in 'tiara-lapis1-breki' originates from its association with a malicious campaign that floods the npm registry with derivative packages. The malicious payload modifies the package.json file to remove private flags, alters version numbers, and generates random package names. This behavior leads to the continuous republishing of variants, polluting the npm registry and potentially compromising other packages. Users of this package may unknowingly contribute to the spread of malicious code, affecting their applications and the broader developer community.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall tiara-lapis1-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 workaround, consider using alternative packages that provide similar functionality without the associated risks. Additionally, you can monitor your project's dependencies using tools like Vulert to identify vulnerabilities in real-time. For example, you can run the following command to check your package-lock.json file: 'vulert check package-lock.json'.
Conclusion
The 'tiara-lapis1-breki' package poses a significant risk due to its malicious code injection vulnerabilities. Users are advised to remove the package and monitor their dependencies closely. Utilizing tools like Vulert can help in identifying and mitigating such vulnerabilities in real-time.
See every vulnerability recorded for tiara-lapis1-breki →
FAQ
It is an npm package associated with a malicious campaign aimed at inflating developer reputation scores through the creation of derivative packages.
The vulnerability can lead to the injection of malicious code into your application, potentially compromising its security and functionality.
You should immediately remove the 'tiara-lapis1-breki' package from your project and monitor for any signs of compromise.
You can use tools like Vulert, which allows you to check your package-lock.json file for vulnerabilities without requiring access to your code or installation.
Yes, you can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without any signup.
