Malicious Code Injection in sparkling_tick_dumbs Package
Summary
MAL-2025-108970: Malicious code in sparkling_tick_dumbs (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 sparkling_tick_dumbs package is part of a series of npm packages that emerged during 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. The functionality of these packages is compromised by malicious scripts that alter package metadata and republish variants to the npm registry.
Vulnerability Detail
The vulnerability in the sparkling_tick_dumbs package originates from its association with a malicious campaign that employs scripts to modify the package.json file. This includes removing private flags, changing version numbers, and generating random package names, which ultimately leads to pollution of the npm registry. The ramifications of this vulnerability include potential security risks for developers who unknowingly use these packages, as they may inadvertently include malicious code in their projects.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall sparkling_tick_dumbsIf 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 sparkling_tick_dumbs package and any other packages associated with the tea.xyz token reward campaign. Additionally, consider using a package monitoring tool like Vulert to keep track of vulnerabilities in your dependencies.
Conclusion
The sparkling_tick_dumbs package poses a significant security risk due to its malicious code injection. Developers should take immediate action to remove this package and monitor their dependencies for vulnerabilities. Utilizing tools like Vulert can aid in maintaining a secure development environment.
See every vulnerability recorded for sparkling_tick_dumbs →
FAQ
The sparkling_tick_dumbs package is an npm package that is part of a malicious campaign aimed at inflating developer reputation scores through automated publishing of derivative packages.
If your project uses the sparkling_tick_dumbs package, it may inadvertently include malicious code, leading to security risks and potential exploitation.
You should remove the sparkling_tick_dumbs package from your project immediately and check for any other compromised packages.
You can use tools like Vulert, which monitors your package-lock.json file for vulnerabilities in real-time without requiring code access or installation.
Yes, you can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without signing up.
