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

teagood-nakamala73 Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-167341: Malicious code in teagood-nakamala73 (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-nakamala73 is an npm package that is part of the tea.xyz token reward campaign. It is designed to facilitate token rewards through the generation and publication of derivative packages. The package is characterized by its use of autopublish scripts that create numerous variants of itself, often with randomized names, to inflate developer reputation scores.

Vulnerability Detail

The vulnerability in teagood-nakamala73 stems from its malicious code that modifies the package.json file to remove private flags, alters version numbers, and generates random package names. This behavior leads to the continuous republishing of these variants, which pollutes the npm registry and can compromise the integrity of the ecosystem. The malicious payload is part of a broader scheme to exploit npm for token rewards, posing risks to developers and users relying on npm packages.

How To Fix

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

npm uninstall teagood-nakamala73

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, you can avoid using the affected package by removing it from your project and replacing it with a known secure alternative. Ensure to audit your package-lock.json file for any other potentially vulnerable packages.

Conclusion

The discovery of malicious code in teagood-nakamala73 highlights the importance of vigilance in managing npm packages. By understanding the nature of this vulnerability and taking appropriate actions, developers can protect their projects from potential threats.

See every vulnerability recorded for teagood-nakamala73 →

Share this vulnerability

FAQ

teagood-nakamala73 is an npm package involved in the tea.xyz token reward campaign, which generates and publishes derivative packages to inflate developer reputation scores.

The vulnerability can lead to the pollution of the npm registry, compromising the integrity of your project's dependencies and potentially introducing malicious code.

You should uninstall the package immediately using 'npm uninstall teagood-nakamala73' and audit your project for any other vulnerable dependencies.

You can use tools like Vulert, which monitors and alerts for open-source vulnerabilities in real-time by analyzing your package-lock.json file.

Yes, you can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without requiring any signup.

How To Fix

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

npm uninstall teagood-nakamala73

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