Malicious Code Injection in utomo-lapis39-breki: A Threat to npm Users
Summary
MAL-2025-75911: Malicious code in utomo-lapis39-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 'utomo-lapis39-breki' is part of a series of malicious 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. This behavior not only compromises the integrity of the npm registry but also poses a significant risk to developers who may unknowingly use these packages in their projects.
Vulnerability Detail
The vulnerability in 'utomo-lapis39-breki' originates from its malicious code, which modifies the package.json file to remove private flags and alters version numbers. It generates random package names, often themed around Indonesian culture, and continuously republishes these variants to pollute the npm registry. This behavior can lead to a loss of trust in the npm ecosystem, potential security risks for applications using these packages, and an overall degradation of the quality of available packages.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall utomo-lapis39-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, avoid using the 'utomo-lapis39-breki' package and consider using alternative packages that provide similar functionality without the associated risks. Regularly audit your project's dependencies using tools like Vulert, which monitors and alerts for open-source vulnerabilities in real-time. 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 'utomo-lapis39-breki' package poses a significant threat to npm users due to its malicious code designed to manipulate package metadata and pollute the npm registry. It is crucial for developers to remove this package from their projects and utilize tools like Vulert to monitor for vulnerabilities in their dependencies.
See every vulnerability recorded for utomo-lapis39-breki →
FAQ
It is a malicious npm package that is part of a campaign to inflate developer reputation scores by publishing derivative packages with random names.
Using this package can compromise your application's integrity, lead to security risks, and contribute to the pollution of the npm registry.
You should uninstall the package immediately using 'npm uninstall utomo-lapis39-breki' to mitigate any potential risks.
You can use tools like Vulert, which monitors your dependencies for vulnerabilities in real-time without requiring code access or installation.
Yes, you can use the Vulert playground at Vulert Scanner to check for vulnerabilities in your application without any signup.
