Malicious Code Injection in warm_wolverine-teagooddev: npm Package Vulnerability

warm_wolverine-teagooddev Updated 18 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-110659: Malicious code in warm_wolverine-teagooddev (npm). Affected versions are not published. No fix is published. How to fix ↓

Free scan

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.

Check my app free

No signup required · Results in about 60 seconds

Upload your dependency manifest or SBOM

Drag & drop your file here or

Java Javascript PHP Python Go Rust Ruby Dart C/C++ Elixir CycloneDX SPDX

Upload a supported dependency manifest or SBOM. No installation or source-code access required.

See supported files and SBOM formats
SBOM sbom.json · bom.json · bom.xml · *.spdx.json · *.cdx.json · *.cdx.xml
Java pom.xml · gradle.lockfile · buildscript-gradle.lockfile
Javascript package-lock.json · yarn.lock · pnpm-lock.yaml
PHP composer.lock
Python poetry.lock · requirements.txt · Pipfile.lock
Go go.mod
Rust Cargo.lock
Ruby Gemfile.lock
Dart pubspec.lock
C/C++ conan.lock
Elixir mix.lock
Enter your work email to receive your report link.

Verify your email to view the full report and start 30 days of continuous monitoring. No credit card required.

Sponsored Devnack Mobile apps built by Devnack Design, build and launch iOS and Android apps with a senior product team. From idea to store release Start a project

Background

The package 'warm_wolverine-teagooddev' 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 through the automatic generation and publication of derivative packages. The functionality of these packages is compromised by malicious scripts that manipulate package metadata.

Vulnerability Detail

The vulnerability originates from the presence of malicious code in the 'warm_wolverine-teagooddev' package. This code modifies the package.json file to remove private flags, alters version numbers, and generates random package names, leading to the continuous republishing of these variants. This behavior not only pollutes the npm registry but also poses a risk to developers who may unknowingly use these compromised packages, potentially leading to further exploitation.

How To Fix

This package is malicious. Remove it and rotate any credentials it could have accessed.

npm uninstall warm_wolverine-teagooddev

If 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 avoid using the 'warm_wolverine-teagooddev' package altogether. If it is already in use, consider replacing it with a trusted alternative package that provides similar functionality without the associated risks.

Conclusion

The 'warm_wolverine-teagooddev' package contains malicious code that compromises its integrity and poses a risk to developers. It is crucial to remove this package and monitor your dependencies for similar vulnerabilities. Utilizing tools like Vulert can help maintain the security of your projects.

See every vulnerability recorded for warm_wolverine-teagooddev →

Share this vulnerability

FAQ

The vulnerability involves malicious code that alters package metadata and repackages it, leading to pollution of the npm registry.

You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. Check your application against this vulnerability using the Vulert playground at Vulert Scanner.

Remove the 'warm_wolverine-teagooddev' package from your project and check for any dependencies that may rely on it.

Regularly audit your dependencies and use tools like Vulert to monitor for vulnerabilities in your open-source packages.

While many packages are trustworthy, it is essential to review package details, maintainers, and community feedback before installation.

How To Fix

This package is malicious. Remove it and rotate any credentials it could have accessed.

npm uninstall warm_wolverine-teagooddev

If 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 →

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →
Help improve this record
Report an issue or send feedback