Malicious Code Injection in bewildered_pike-smiletea Package
Summary
MAL-2025-99958: Malicious code in bewildered_pike-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 bewildered_pike-smiletea package is part of a token reward campaign associated with the tea.xyz protocol, which aims to incentivize developers through token rewards. This package, like many others in the campaign, is designed to automatically generate and publish derivative packages with randomized names, ultimately inflating developer reputation scores. However, it has been identified as containing malicious code that compromises the integrity of the npm registry.
Vulnerability Detail
The vulnerability stems from the package's malicious payload, which 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 harming developers' reputations and the overall ecosystem. The origin of this issue is linked to the tea.xyz token reward campaign, which has flooded npm with similar malicious packages.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall bewildered_pike-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 workaround, you can monitor your project's dependencies using tools like Vulert, which allows you to check for vulnerabilities in your package-lock.json file. You can access the Vulert playground at https://vulert.com/scanner to see if your application is affected by this vulnerability without needing to sign up.
Conclusion
The bewildered_pike-smiletea package poses a significant risk due to its malicious code that alters package metadata and floods the npm registry. It is essential to remove this package from your projects and utilize tools like Vulert for ongoing monitoring of vulnerabilities.
See every vulnerability recorded for bewildered_pike-smiletea →
FAQ
The malicious code can lead to the automatic generation of numerous derivative packages, polluting the npm registry and potentially damaging developer reputations.
You can use Vulert to monitor your package-lock.json file for vulnerabilities and check if your project is impacted.
No, it is recommended to completely remove the bewildered_pike-smiletea package from your project as it is inherently malicious.
You should immediately uninstall the package using the command 'npm uninstall bewildered_pike-smiletea' to mitigate any risks.
Yes, regularly monitor your dependencies with tools like Vulert and stay updated on known vulnerabilities in the npm ecosystem.
