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

teagood-nakamala70 Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-167338: Malicious code in teagood-nakamala70 (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-nakamala70 is an npm package that is part of the tea.xyz token reward campaign. This package is designed to interact with the npm registry, allowing developers to publish and manage their packages. However, it has been identified as containing malicious code that compromises its integrity and the security of the npm ecosystem.

Vulnerability Detail

The vulnerability in teagood-nakamala70 originates from its design to automate the generation and publication of derivative packages with randomized names. This malicious behavior includes modifying the package.json file to remove private flags, altering version numbers, and continuously republishing variants to pollute the npm registry. This can lead to reputation inflation for developers and potentially expose users to untrusted code.

How To Fix

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

npm uninstall teagood-nakamala70

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, avoid using the teagood-nakamala70 package and monitor your project for any unintended dependencies that may have been introduced. You can also use tools like Vulert to check for vulnerabilities in your package-lock.json file.

Conclusion

The discovery of malicious code in the teagood-nakamala70 package highlights the importance of vigilance in managing dependencies within the npm ecosystem. By removing affected packages and utilizing monitoring tools like Vulert, developers can safeguard their projects against similar vulnerabilities.

See every vulnerability recorded for teagood-nakamala70 →

Share this vulnerability

FAQ

teagood-nakamala70 is an npm package involved in a token reward campaign that has been found to contain malicious code.

The vulnerability can lead to the introduction of untrusted code into your project, potentially compromising security and stability.

You should uninstall the package immediately using npm uninstall teagood-nakamala70 and check your project for any other affected dependencies.

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

There is no patch for teagood-nakamala70 since it is recommended to remove the package entirely.

How To Fix

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

npm uninstall teagood-nakamala70

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