Malicious Code Injection in teagood-namakai21: A Threat to npm Users

teagood-namakai21 Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-167674: Malicious code in teagood-namakai21 (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 Penetration testing for web, API and mobile Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

teagood-namakai21 is an npm package that is part of the tea.xyz token reward campaign. This package, like many others in the campaign, is designed to manipulate the npm registry by automatically generating and publishing derivative packages with randomized names. Its primary function is to inflate developer reputation scores for rewards associated with the tea protocol, but this functionality comes with significant risks due to its malicious behavior.

Vulnerability Detail

The vulnerability in teagood-namakai21 stems from its malicious code that modifies the package.json file to remove private flags and change version numbers. It generates random Indonesian-themed package names and continuously republishes variants, polluting the npm registry. This behavior not only compromises the integrity of the npm ecosystem but also poses risks to developers who may unknowingly use these compromised packages, leading to potential security breaches in their applications.

How To Fix

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

npm uninstall teagood-namakai21

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 measure, you can avoid using the teagood-namakai21 package and replace it with a trusted alternative. Regularly audit your package-lock.json file for any suspicious packages and remove them promptly.

Conclusion

The teagood-namakai21 package poses a significant threat due to its malicious code that alters package configurations and pollutes the npm registry. It is essential 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 teagood-namakai21 →

Share this vulnerability

FAQ

teagood-namakai21 is an npm package associated with the tea.xyz token reward campaign, designed to manipulate the npm registry.

The malicious code can compromise your application's integrity by introducing untrusted packages and altering your package configurations.

You should uninstall the package immediately using 'npm uninstall teagood-namakai21' and audit your project for any other suspicious packages.

You can use tools like Vulert, which monitors your package-lock.json for open-source vulnerabilities in real-time without requiring code access.

Yes, you can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without any signup.

How To Fix

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

npm uninstall teagood-namakai21

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