Malicious Code Injection in teagood-namakai36: A Threat to npm Packages

teagood-namakai36 Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-167690: Malicious code in teagood-namakai36 (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-namakai36 is an npm package that is part of a broader campaign involving the tea.xyz token reward system. This package is designed to interact with the npm registry, potentially inflating developer reputation scores through the automatic generation and publication of derivative packages. The package's functionality includes creating randomized package names and modifying existing package metadata, which can lead to significant issues in the npm ecosystem.

Vulnerability Detail

The vulnerability in teagood-namakai36 stems from its malicious payload that modifies the package.json file. It removes 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 security breaches and loss of trust in the npm ecosystem.

How To Fix

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

npm uninstall teagood-namakai36

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-namakai36 package and instead rely on alternative packages that provide similar functionality without the associated risks. Always verify the integrity and reputation of packages before including them in your projects.

Conclusion

The teagood-namakai36 package poses a significant risk due to its malicious behavior, which can compromise the integrity of the npm registry and the security of projects using it. It is crucial to take immediate action by uninstalling the package and monitoring your dependencies for vulnerabilities.

See every vulnerability recorded for teagood-namakai36 →

Share this vulnerability

FAQ

teagood-namakai36 is an npm package involved in a token reward campaign that automates the generation of derivative packages, potentially compromising the integrity of the npm registry.

The vulnerability can lead to the introduction of malicious code into your project, which may compromise security and affect the reliability of your software.

You should uninstall the package immediately using 'npm uninstall teagood-namakai36' and review your project for any potential impacts.

You can use tools like Vulert, which monitors your package-lock.json file to alert you in real-time for open-source vulnerabilities. You can check your application against vulnerabilities using the Vulert playground without any signup.

Yes, consider using well-established and trusted packages that provide similar functionality without the risks associated with teagood-namakai36.

How To Fix

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

npm uninstall teagood-namakai36

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