Malicious Code Injection in variable_guppy_cyan-39: A Threat to npm Packages
Summary
MAL-2025-110336: Malicious code in variable_guppy_cyan-39 (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 'variable_guppy_cyan-39' is part of a series of npm packages associated with 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. This behavior poses a significant risk to the integrity of the npm registry and can lead to the proliferation of malicious software.
Vulnerability Detail
This vulnerability originates from the package's malicious code, which modifies the package.json file to remove private flags, alters version numbers, and generates random package names. The payload continuously republishes these variants, polluting the npm registry and potentially compromising other projects that depend on these packages. The ramifications include the risk of executing untrusted code, loss of control over package versions, and damage to developer reputation.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall variable_guppy_cyan-39If 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 'variable_guppy_cyan-39' package and monitor your dependencies for any similar malicious packages. You can also use Vulert to check if your application is affected by this vulnerability by visiting https://vulert.com/scanner without any signup.
Conclusion
The 'variable_guppy_cyan-39' package poses a significant threat due to its malicious code that alters package configurations and proliferates untrusted packages. It is crucial to remove this package from your project and monitor your dependencies for similar vulnerabilities. Utilizing tools like Vulert can help maintain the security of your applications.
See every vulnerability recorded for variable_guppy_cyan-39 →
FAQ
It is an npm package associated with a token reward campaign that generates and publishes derivative packages to inflate developer reputation scores.
The malicious code modifies your package.json, removes private flags, and can lead to the execution of untrusted code, compromising your project's integrity.
You should uninstall the package immediately using 'npm uninstall variable_guppy_cyan-39' and check your package-lock.json for any lingering references.
Yes, regularly audit your dependencies and use tools like Vulert to monitor for open-source vulnerabilities in real-time.
Yes, you can use the Vulert playground at Vulert Scanner to check for vulnerabilities in your application without any signup.
