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

teagood-nalikami23 Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-167421: Malicious code in teagood-nalikami23 (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-nalikami23 is an npm package that is part of the tea.xyz token reward campaign. This package is designed to interact with the npm ecosystem, allowing developers to publish and manage packages. However, it has been identified as malicious, containing scripts that manipulate package metadata and flood the npm registry with derivative packages, thereby compromising the integrity of the ecosystem.

Vulnerability Detail

The vulnerability in teagood-nalikami23 originates from its inclusion in a campaign that aims to inflate developer reputation scores through malicious means. The package includes autopublish scripts that modify the package.json file to remove private flags, alter version numbers, and generate random package names. This results in the continuous republishing of variants, which pollutes the npm registry and can lead to confusion and potential security risks for developers relying on legitimate packages.

How To Fix

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

npm uninstall teagood-nalikami23

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 dependencies. If you need similar functionality, consider using alternative packages that do not exhibit malicious behavior.

Conclusion

The discovery of malicious code in teagood-nalikami23 highlights the importance of vigilance in the npm ecosystem. Developers should take immediate action to remove affected packages and monitor their dependencies for vulnerabilities. Utilizing tools like Vulert can help maintain the security of your projects.

See every vulnerability recorded for teagood-nalikami23 →

Share this vulnerability

FAQ

teagood-nalikami23 is an npm package associated with the tea.xyz token reward campaign, which has been identified as containing malicious code.

The malicious code modifies your package.json file, removes private flags, and floods the npm registry with derivative packages, potentially leading to security risks.

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

Yes, consider using other reputable npm packages that provide similar functionality without the associated risks.

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 at the Vulert playground without any signup.

How To Fix

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

npm uninstall teagood-nalikami23

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