Malicious Code Injection in wide_guppy_dumbs: A Threat to npm Packages
Summary
MAL-2025-110904: Malicious code in wide_guppy_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
Habilume
Habit tracker with a companion that grows with you
Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent.
Background
The package 'wide_guppy_dumbs' is part of a series of npm packages that have been identified as malicious. These packages are linked to the tea.xyz token reward campaign, which aims to inflate developer reputation scores through the automatic generation and publication of derivative packages. This behavior poses significant risks to the integrity of the npm ecosystem.
Vulnerability Detail
The vulnerability in 'wide_guppy_dumbs' originates from its design to include autopublish scripts that modify the package.json file. These modifications remove private flags, alter version numbers, and generate random package names, leading to pollution of the npm registry. This can result in developers inadvertently using compromised packages, which may contain malicious code or vulnerabilities.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall wide_guppy_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, avoid using the 'wide_guppy_dumbs' package and consider using alternative packages that provide similar functionality without the associated risks. Regularly audit your package dependencies to ensure they are secure.
Conclusion
The 'wide_guppy_dumbs' package poses a significant threat due to its malicious code designed to manipulate npm package metadata. It is crucial for developers to remove this package and monitor their dependencies for vulnerabilities. Utilizing tools like Vulert can aid in maintaining the security of your projects.
See every vulnerability recorded for wide_guppy_dumbs →
FAQ
The main issue is that it contains malicious code designed to manipulate package metadata and publish harmful variants to the npm registry.
You can use tools like Vulert, which monitors your package-lock.json for vulnerabilities in real-time. Visit Vulert Scanner to check if your application is affected without needing to sign up.
Using this package can lead to security breaches, as it may introduce malicious code into your application, compromising its integrity and security.
Yes, regularly audit your dependencies, use trusted sources for packages, and consider implementing automated tools like Vulert to monitor for vulnerabilities.
Immediately uninstall the package and review your project for any potential impacts. Consider replacing it with a secure alternative.
Habilume
Habit tracker with a companion that grows with you
Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent.
