Malicious Code Injection in teagood-nakamala54: A Threat to npm Ecosystem

teagood-nakamala54 Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-167320: Malicious code in teagood-nakamala54 (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 MarkAI Find prospects already talking about the problem you solve AI watches the communities your customers use to find qualified prospects, then alerts you when a conversation is worth joining. See MarkAI

Background

teagood-nakamala54 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 automatically generating and publishing derivative packages. However, it has been identified as malicious due to its functionality that modifies package metadata and floods the npm registry with unwanted variants.

Vulnerability Detail

The vulnerability in teagood-nakamala54 originates from its malicious design, which includes scripts that alter the package.json file to remove private flags, change version numbers, and generate random package names. This behavior not only compromises the integrity of the npm registry but also poses a risk to developers who may unknowingly install these malicious packages, leading to potential security breaches and reputation damage.

How To Fix

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

npm uninstall teagood-nakamala54

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 teagood-nakamala54 package altogether. If you have already installed it, ensure to remove it and monitor your project for any other potentially malicious packages. Additionally, consider using tools like Vulert to monitor your dependencies for vulnerabilities.

Conclusion

The teagood-nakamala54 package poses a significant risk due to its malicious code designed to manipulate package metadata and flood the npm registry. It is crucial for developers to remove this package and monitor their projects for any vulnerabilities to maintain security and integrity.

See every vulnerability recorded for teagood-nakamala54 →

Share this vulnerability

FAQ

teagood-nakamala54 is an npm package associated with the tea.xyz token reward campaign, designed to generate and publish derivative packages.

The vulnerability can lead to the installation of malicious packages that compromise your project's integrity and security.

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

Yes, you can use Vulert, which monitors your package-lock.json for vulnerabilities in real-time without requiring code access or installation.

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-nakamala54

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