Malicious Code Injection in teagood-nakama20: npm Package Vulnerability

teagood-nakama20 Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-167184: Malicious code in teagood-nakama20 (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

teagood-nakama20 is an npm package that is part of the tea.xyz token reward campaign. This package is designed to facilitate token rewards for developers by generating and publishing derivative packages. 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 teagood-nakama20 originates from its design to automatically generate and publish derivative packages with randomized names. This is achieved through scripts that modify the package.json file, removing private flags and changing version numbers. The malicious payload continuously republishes variants, polluting the npm registry and potentially leading to reputation inflation for developers involved in the tea protocol token rewards. This behavior can result in a compromised npm ecosystem, making it difficult for developers to trust the integrity of packages.

How To Fix

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

npm uninstall teagood-nakama20

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 temporary workaround, you can avoid using the teagood-nakama20 package and look for alternative packages that provide similar functionality without the associated risks. Additionally, consider using tools like Vulert to monitor your project for vulnerabilities.

Conclusion

The teagood-nakama20 npm package has been identified as containing malicious code that compromises the integrity of the npm registry. It is crucial for developers to remove this package and monitor their projects for vulnerabilities using tools like Vulert. Staying informed and proactive can help maintain a secure development environment.

See every vulnerability recorded for teagood-nakama20 →

Share this vulnerability

FAQ

The package contains malicious code that modifies package.json files and republishes variants to pollute the npm registry.

You can use Vulert's playground at Vulert Scanner to check if your application is affected without requiring any signup.

You should remove the teagood-nakama20 package from your project and look for a safe alternative.

Check the npm registry for any updates or patches for the teagood-nakama20 package that address this vulnerability.

Vulert uses the package-lock.json file to monitor and alert in real-time for open-source vulnerabilities in your software.

How To Fix

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

npm uninstall teagood-nakama20

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