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

teagood-nalikami7 Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-167472: Malicious code in teagood-nalikami7 (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-nalikami7 is a package associated with the tea.xyz token reward campaign, which has been known to flood the npm registry with numerous packages. This package is designed to automate the generation and publication of derivative packages, often with randomized names, to inflate developer reputation scores for token rewards. Its functionality is primarily centered around creating and publishing these packages, but it has been compromised to include malicious code.

Vulnerability Detail

The vulnerability in teagood-nalikami7 originates from its malicious payload that modifies the package.json file. It removes private flags, alters version numbers, and generates random package names, leading to the continuous republishing of variants. This behavior not only pollutes the npm registry but also poses a risk to developers who may unknowingly install these compromised packages, potentially leading to further exploitation and security breaches.

How To Fix

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

npm uninstall teagood-nalikami7

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 teagood-nalikami7 and any other packages associated with the tea.xyz token reward campaign. Additionally, you can monitor your dependencies using tools like Vulert, which allows you to check for vulnerabilities in your package-lock.json file without requiring code access or installation.

Conclusion

The teagood-nalikami7 package poses a significant threat due to its malicious code that alters package metadata and floods the npm registry. It is essential to take immediate action by updating or removing the package to protect your project from potential security risks. Utilizing tools like Vulert can help in monitoring and identifying vulnerabilities in your dependencies.

See every vulnerability recorded for teagood-nalikami7 →

Share this vulnerability

FAQ

teagood-nalikami7 is an npm package linked to the tea.xyz token reward campaign, designed to automate the publication of derivative packages.

The vulnerability can lead to the installation of malicious packages that may compromise your project's security and integrity.

You should update the package to a patched version if available, or remove it from your project to mitigate the risk.

You can use Vulert to monitor your package-lock.json file for vulnerabilities in real-time without needing to access the code.

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

How To Fix

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

npm uninstall teagood-nalikami7

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