Malicious Code Injection in utomo-lapis44-riris Package
Summary
MAL-2025-91586: Malicious code in utomo-lapis44-riris (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 utomo-lapis44-riris package is part of the npm ecosystem, often utilized in various JavaScript applications. It is associated with the tea.xyz token reward campaign, which has been known to flood the npm registry with numerous packages. This package, like others in the campaign, is designed to manipulate developer reputation scores by generating and publishing derivative packages with randomized names.
Vulnerability Detail
The vulnerability in the utomo-lapis44-riris package stems from its malicious code, which modifies the package.json file to remove private flags, alters version numbers, and generates random package names. This behavior is intended to inflate developer reputation scores fraudulently and pollute the npm registry with numerous variants of the package. The origin of this vulnerability is linked to the tea.xyz token reward campaign, which employs autopublish scripts to automate the creation and publication of these malicious packages.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall utomo-lapis44-riris
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 utomo-lapis44-riris package entirely and look for alternative packages that provide similar functionality without the associated risks.
Conclusion
The utomo-lapis44-riris package contains a significant vulnerability due to its malicious code, which can lead to various security risks. It is crucial to remove this package from your project and monitor your dependencies regularly to ensure the integrity of your applications.
See every vulnerability recorded for utomo-lapis44-riris →
FAQ
The vulnerability involves malicious code that modifies package.json to remove private flags and generates numerous derivative packages to inflate developer reputation scores.
You can use Vulert, which monitors and alerts for open-source vulnerabilities in your software. By analyzing your package-lock.json file, Vulert can help identify if your application is affected.
The consequences include the pollution of the npm registry with malicious packages, potential security risks for applications using the affected package, and damage to developer reputation.
Regularly audit your dependencies, use tools like Vulert for real-time monitoring, and avoid using packages from untrusted sources to minimize risks.
If immediate removal is not possible, consider isolating the affected package and monitoring your application closely for any unusual behavior while planning for its removal.