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

teagood-nakamala62 Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-167329: Malicious code in teagood-nakamala62 (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-nakamala62 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 intended for developers looking to enhance their reputation scores through token rewards. However, it has been identified as containing malicious scripts that can compromise the integrity of the npm ecosystem.

Vulnerability Detail

The vulnerability in teagood-nakamala62 originates from its inclusion in a campaign that floods the npm registry with derivative packages. These packages contain scripts that modify the package.json file to remove private flags, alter version numbers, and generate random package names. This behavior not only inflates developer reputation scores but also pollutes the npm registry, potentially leading to security risks for users who unknowingly install these malicious packages.

How To Fix

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

npm uninstall teagood-nakamala62

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-nakamala62 package altogether. If it is already in use, consider removing it from your project by executing: npm uninstall teagood-nakamala62. Additionally, you can monitor your project for any dependencies that may introduce similar vulnerabilities.

Conclusion

The teagood-nakamala62 package poses a significant risk due to its malicious code that alters package metadata and floods the npm registry. It is essential for developers to be vigilant and take necessary actions to mitigate this vulnerability by updating or removing the affected package.

See every vulnerability recorded for teagood-nakamala62 →

Share this vulnerability

FAQ

teagood-nakamala62 is an npm package associated with the tea.xyz token reward campaign, which aims to enhance developer reputation scores.

The vulnerability allows malicious scripts to modify your package.json file and republish variants, potentially compromising your project's integrity and security.

If you have installed teagood-nakamala62, it is crucial to uninstall it immediately and check for any other affected packages in your project.

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

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

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