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

teagood-namakai51 Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-167707: Malicious code in teagood-namakai51 (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-namakai51 is an npm package that is part of the tea.xyz token reward campaign. This package is designed to interact with the npm registry and is typically used for generating and publishing derivative packages. However, it has been identified as containing malicious code that can compromise the integrity of the npm ecosystem.

Vulnerability Detail

The vulnerability in teagood-namakai51 originates from its malicious payload, which modifies the package.json file to remove private flags, alters version numbers, and generates random package names. This behavior is intended to inflate developer reputation scores for token rewards, leading to the continuous republishing of variants that pollute the npm registry. The ramifications include potential security risks for developers who unknowingly install these compromised packages, as well as damage to the overall trustworthiness of the npm ecosystem.

How To Fix

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

npm uninstall teagood-namakai51

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, avoid using the teagood-namakai51 package and consider using alternative packages that provide similar functionality without the associated risks.

Conclusion

The discovery of malicious code in the teagood-namakai51 package highlights the importance of vigilance when managing npm packages. By understanding the nature of this vulnerability and taking appropriate actions, developers can protect their projects and maintain the integrity of the npm ecosystem.

See every vulnerability recorded for teagood-namakai51 →

Share this vulnerability

FAQ

teagood-namakai51 is an npm package involved in a token reward campaign that has been identified to contain malicious code.

The malicious code can modify your package.json file, remove private flags, and republish variants, potentially compromising your project's integrity.

You should uninstall the package immediately using npm uninstall teagood-namakai51 and check for any dependencies that may be affected.

Yes, you can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time using just your package-lock.json. You can check if your application is affected by this vulnerability using the Vulert playground at Vulert Scanner.

Regularly audit your npm packages using npm audit, keep your dependencies updated, and monitor for vulnerabilities using tools like Vulert.

How To Fix

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

npm uninstall teagood-namakai51

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