Malicious Code Injection in tomi-mie35-riris: A Threat to npm Ecosystem
Summary
MAL-2025-91169: Malicious code in tomi-mie35-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 package 'tomi-mie35-riris' 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 known to flood npm with malicious packages. These packages often contain scripts designed to manipulate the npm registry and inflate developer reputation scores through deceptive practices.
Vulnerability Detail
The vulnerability in 'tomi-mie35-riris' originates from its involvement in a malicious campaign that 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 the integrity of other packages. The malicious payload can affect developers' reputations and the overall trustworthiness of the npm ecosystem.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall tomi-mie35-ririsIf 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 'tomi-mie35-riris' package and look for alternative packages that provide similar functionality without the associated risks. Always verify the integrity and reputation of packages before including them in your project.
Conclusion
The 'tomi-mie35-riris' package poses a significant threat to the npm ecosystem due to its malicious code designed to manipulate the npm registry. It is essential for developers to be vigilant, remove affected packages, and utilize monitoring tools like Vulert to safeguard their projects from such vulnerabilities.
See every vulnerability recorded for tomi-mie35-riris →
FAQ
The malicious code can lead to the pollution of the npm registry, affecting the integrity of other packages and potentially harming developers' reputations.
You can use tools like Vulert, which monitors your package-lock.json for vulnerabilities in real-time. Visit Vulert Scanner to check if your application is affected.
Immediately uninstall the package using 'npm uninstall tomi-mie35-riris' and review your project for any other potentially harmful packages.
There are no patches available for the tomi-mie35-riris package as it is inherently malicious. The best course of action is to remove it entirely.
Regularly audit your dependencies, use tools like Vulert for monitoring, and only install packages from trusted sources.
