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

teagood-nakamala82 Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-167351: Malicious code in teagood-nakamala82 (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-nakamala82 is an npm package that appears to be part of a token reward campaign associated with the tea.xyz protocol. This package is designed to facilitate the automatic generation and publication of derivative packages, which can inflate developer reputation scores in exchange for token rewards. 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-nakamala82 stems from its inclusion in a malicious campaign that utilizes autopublish scripts to create and publish numerous derivative packages with randomized names. This behavior modifies the package.json file by removing private flags, altering version numbers, and continuously republishing variants, which pollutes the npm registry. The ramifications include potential security risks for developers who unknowingly use these compromised packages, as well as damage to the reputation of the npm ecosystem.

How To Fix

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

npm uninstall teagood-nakamala82

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-nakamala82 package and look for alternative packages that provide similar functionality without the associated risks. Additionally, you can use the following command to uninstall the package: npm uninstall teagood-nakamala82.

Conclusion

The discovery of malicious code in the teagood-nakamala82 npm package highlights the importance of vigilance in managing dependencies. Developers should take immediate action to remove this package and monitor their projects for vulnerabilities to maintain the integrity and security of their applications.

See every vulnerability recorded for teagood-nakamala82 →

Share this vulnerability

FAQ

teagood-nakamala82 is an npm package involved in a token reward campaign that has been identified as containing malicious code.

The malicious code modifies your package.json file and can lead to the publication of compromised packages, potentially affecting your project's security.

You should uninstall the package immediately and check for any alternative packages that do not pose security risks.

Yes, you can use Vulert, which monitors and alerts for open-source vulnerabilities in your software using just package-lock.json. You can check your application for vulnerabilities without signing up at the Vulert playground.

Regularly update your dependencies, monitor for vulnerabilities using tools like Vulert, and review the packages you use for any reported issues.

How To Fix

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

npm uninstall teagood-nakamala82

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