Malicious Code Injection in consistent_asp-smiletea Package
Summary
MAL-2025-100881: Malicious code in consistent_asp-smiletea (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 consistent_asp-smiletea package is part of the npm ecosystem and is associated with the tea.xyz token reward campaign. This package is designed to facilitate token rewards by generating and publishing derivative packages. However, it has been compromised to include malicious code that alters its functionality and impacts the npm registry.
Vulnerability Detail
The vulnerability stems from the presence of malicious code within the consistent_asp-smiletea package. This code is designed to automatically modify the package.json file by removing private flags, changing version numbers, and generating random package names, which leads to the pollution of the npm registry. The malicious payload can inflate developer reputation scores fraudulently, posing risks to developers and users relying on the integrity of the npm ecosystem.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall consistent_asp-smileteaIf 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 remove the consistent_asp-smiletea package from your project by executing: npm uninstall consistent_asp-smiletea. This will prevent any malicious code from executing until a secure version is available.
Conclusion
The consistent_asp-smiletea package has been identified as containing malicious code that compromises the npm registry. It is crucial for developers to take immediate action by updating or removing the package to safeguard their projects and maintain the integrity of the npm ecosystem.
See every vulnerability recorded for consistent_asp-smiletea →
FAQ
The vulnerability involves malicious code that modifies package.json and publishes random derivative packages, compromising the integrity of the npm registry.
You can use Vulert to monitor and alert for open-source vulnerabilities in your software. Visit Vulert Scanner to check your application without needing to sign up.
Using the compromised package can lead to unauthorized modifications in your project, potential security breaches, and damage to your reputation as a developer.
It is advisable to check the npm registry for any patched versions of the consistent_asp-smiletea package and update accordingly.
If immediate updates are not possible, consider removing the package from your project as a temporary measure to mitigate risks.
