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

teagood-nakamala31 Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-167295: Malicious code in teagood-nakamala31 (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-nakamala31 is an npm package that is part of the tea.xyz token reward campaign. This package is designed to facilitate the generation and publication of derivative packages, often with randomized names, to inflate developer reputation scores for rewards associated with the tea protocol. The package's functionality is compromised by malicious scripts that manipulate its metadata.

Vulnerability Detail

The vulnerability originates from the presence of malicious code within the teagood-nakamala31 package. This code modifies the package.json file to remove private flags, alters version numbers, and generates random package names, leading to the continuous republishing of variants. This behavior pollutes the npm registry and can undermine the integrity of the ecosystem, potentially affecting developers who rely on these packages for legitimate purposes.

How To Fix

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

npm uninstall teagood-nakamala31

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 prevent the installation of the affected package by using npm's package-lock.json to lock down your dependencies. Additionally, consider using a tool like Vulert to monitor your project for vulnerabilities. You can check if your application is affected by this vulnerability using the Vulert playground at https://vulert.com/scanner without any signup.

Conclusion

The presence of malicious code in the teagood-nakamala31 npm package poses a significant threat to the integrity of the npm ecosystem. By understanding the nature of this vulnerability and taking appropriate action, developers can protect their projects from potential harm.

See every vulnerability recorded for teagood-nakamala31 →

Share this vulnerability

FAQ

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

The package contains scripts that modify package.json files, remove private flags, change version numbers, and create random package names, leading to pollution of the npm registry.

You can check your package-lock.json file for the presence of teagood-nakamala31 or use tools like Vulert to monitor for vulnerabilities.

Uninstall the package using 'npm uninstall teagood-nakamala31' and look for secure alternatives to replace it.

Regularly monitor your dependencies using tools like Vulert and keep your packages updated to the latest secure versions.

How To Fix

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

npm uninstall teagood-nakamala31

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