Malicious Code Injection in gleaming_viper_dumbs: npm Package Vulnerability
Summary
MAL-2025-103280: Malicious code in gleaming_viper_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 package 'gleaming_viper_dumbs' is part of the npm ecosystem and is associated with the tea.xyz token reward campaign. This package is designed to facilitate the automatic generation and publication of derivative packages, often with randomized names. It aims to inflate developer reputation scores for rewards associated with the tea protocol. However, it has been identified as containing malicious code that compromises its integrity and the security of the npm registry.
Vulnerability Detail
The vulnerability in 'gleaming_viper_dumbs' originates from its association with 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, which pollutes the npm registry and can potentially harm developers by inflating reputation scores fraudulently. The malicious payload is designed to execute scripts that automate these actions, making it a significant threat to 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 gleaming_viper_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 workaround, you can manually remove the package from your project by executing the following command in your terminal: npm uninstall gleaming_viper_dumbs. Additionally, ensure that your package.json file does not reference this package to avoid reinstallation.
Conclusion
The 'gleaming_viper_dumbs' package poses a significant security risk due to its malicious code that alters package metadata and floods the npm registry. It is essential to remove this package from your project to safeguard your application and maintain the integrity of the npm ecosystem.
See every vulnerability recorded for gleaming_viper_dumbs →
FAQ
The primary risk is that it contains malicious code that modifies package metadata and floods the npm registry with derivative packages, which can lead to reputation inflation and potential security vulnerabilities.
You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. By utilizing the Vulert playground, you can check if your application is affected without needing to sign up.
If you have installed 'gleaming_viper_dumbs', it is recommended to uninstall it immediately using the command: npm uninstall gleaming_viper_dumbs.
Currently, there are no known patched versions of 'gleaming_viper_dumbs'. The best course of action is to remove the package entirely.
Failing to address this vulnerability could lead to your project being associated with malicious activities, potentially harming your reputation and the security of your application.
