Malicious Code Injection in tomi-dodol38-sluey: A Threat to npm Users
Summary
MAL-2025-91126: Malicious code in tomi-dodol38-sluey (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-dodol38-sluey is part of a series of malicious npm packages that emerged during the tea.xyz token reward campaign. These packages are designed to inflate developer reputation scores through the automatic generation and publication of derivative packages with randomized names. This behavior not only clutters the npm registry but also poses significant risks to users who may inadvertently install these compromised packages.
Vulnerability Detail
The vulnerability in tomi-dodol38-sluey stems from its malicious payload that modifies the package.json file to remove private flags, alters version numbers, and generates random package names. This behavior allows the package to continuously republish variants, polluting the npm registry and potentially leading to the installation of harmful code by unsuspecting developers. The origin of this vulnerability is linked to the tea.xyz token reward campaign, which aimed to exploit npm's package management system for malicious purposes.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall tomi-dodol38-slueyIf 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 tomi-dodol38-sluey package and any other packages associated with the tea.xyz campaign. Monitor your project's dependencies and consider using tools like Vulert to check for vulnerabilities in your package-lock.json file.
Conclusion
The tomi-dodol38-sluey package poses a significant risk due to its malicious behavior, which can compromise the security of applications using it. It is crucial for developers to stay vigilant, regularly update their dependencies, and utilize tools like Vulert to monitor for vulnerabilities. By taking proactive measures, you can protect your projects from potential threats.
See every vulnerability recorded for tomi-dodol38-sluey →
FAQ
tomi-dodol38-sluey is an npm package that has been identified as malicious, part of a campaign to inflate developer reputation scores through automated publishing.
The vulnerability can lead to the installation of malicious code, which may compromise your application's security and integrity.
You should immediately uninstall tomi-dodol38-sluey using the command npm uninstall tomi-dodol38-sluey and review your project's dependencies for any other malicious packages.
Regularly update your packages, use trusted sources, and utilize tools like Vulert to monitor your dependencies for vulnerabilities.
Vulert is a tool that monitors and alerts for open-source vulnerabilities in your software using just the package-lock.json file. You can check if your application is affected by vulnerabilities without needing to access the code or install anything.
