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

teagood-nakamala38 Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-167302: Malicious code in teagood-nakamala38 (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 Your last release was probably never penetration tested Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

teagood-nakamala38 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 involved in generating and publishing derivative packages. However, it has been identified as malicious due to its capability to modify package metadata and republish variants, which can lead to pollution of the npm registry and compromise developer reputation.

Vulnerability Detail

The vulnerability in teagood-nakamala38 stems from its malicious payload that alters the package.json file by removing private flags, changing version numbers, and generating random package names. This behavior is intended to inflate developer reputation scores fraudulently. The origin of this vulnerability is linked to the tea.xyz token reward campaign, which has flooded the npm ecosystem with similar malicious packages. The ramifications include potential security risks for developers and users, as well as the degradation of the npm registry's integrity.

How To Fix

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

npm uninstall teagood-nakamala38

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 remove the affected package from your project by executing 'npm uninstall teagood-nakamala38'. This will prevent any malicious activity associated with the package until a secure version is available.

Conclusion

The teagood-nakamala38 package poses a significant threat due to its malicious behavior of modifying package metadata and republishing variants. It is essential for developers to take immediate action by updating or removing the package to safeguard their projects and maintain the integrity of the npm ecosystem.

See every vulnerability recorded for teagood-nakamala38 →

Share this vulnerability

FAQ

teagood-nakamala38 is an npm package involved in the tea.xyz token reward campaign, which has been identified as malicious due to its ability to manipulate package metadata.

The vulnerability can lead to the pollution of the npm registry and compromise the integrity of your project by introducing malicious code or dependencies.

If you have installed teagood-nakamala38, it is crucial to uninstall it immediately and check for any updates or patches that may be available.

Yes, you can use Vulert to monitor your project for open-source vulnerabilities. Vulert uses package-lock.json to provide real-time alerts for vulnerabilities without requiring code access.

You can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without needing to sign up.

How To Fix

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

npm uninstall teagood-nakamala38

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