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

teagood-nalikami58 Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-167459: Malicious code in teagood-nalikami58 (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-nalikami58 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 through token rewards. However, it has been identified as containing malicious code that can compromise the integrity of the npm ecosystem.

Vulnerability Detail

The vulnerability in teagood-nalikami58 originates from its design to automatically generate and publish derivative packages with randomized names, which are intended to inflate developer reputation scores for tea protocol token rewards. The malicious payload modifies the package.json file to remove private flags, alters version numbers, and generates random package names, leading to pollution of the npm registry. This can result in developers unknowingly using compromised packages, which may introduce security risks into their applications.

How To Fix

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

npm uninstall teagood-nalikami58

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-nalikami58 package and any other packages that may be associated with the tea.xyz token reward campaign. Instead, look for alternative packages that provide similar functionality without the associated risks.

Conclusion

The discovery of malicious code in the teagood-nalikami58 package highlights the importance of vigilance in the npm ecosystem. Developers should take immediate action to remove affected packages and utilize tools like Vulert to monitor for vulnerabilities in their applications.

See every vulnerability recorded for teagood-nalikami58 →

Share this vulnerability

FAQ

teagood-nalikami58 is an npm package involved in the tea.xyz token reward campaign, which has been identified to contain malicious code.

The malicious code can modify your package.json file, remove private flags, and publish compromised packages, potentially leading to security vulnerabilities in your application.

You can use Vulert to monitor and alert for open-source vulnerabilities in your software. Visit Vulert Scanner to check if your application is affected without requiring any signup.

If you have installed teagood-nalikami58, you should uninstall it immediately using the command: npm uninstall teagood-nalikami58.

Yes, you should look for alternative packages that provide similar functionality without the associated risks of malicious code.

How To Fix

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

npm uninstall teagood-nalikami58

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