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

teagood-nalikoli87 Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-167646: Malicious code in teagood-nalikoli87 (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 MarkAI Find prospects already talking about the problem you solve AI watches the communities your customers use to find qualified prospects, then alerts you when a conversation is worth joining. See MarkAI

Background

teagood-nalikoli87 is an npm package that appears to be part of a broader campaign related to the tea.xyz token reward system. This package, like others in the campaign, is designed to manipulate the npm registry by generating and publishing numerous derivative packages with randomized names. Its functionality is primarily aimed at inflating developer reputation scores for token rewards, making it a potential threat to the integrity of the npm ecosystem.

Vulnerability Detail

The vulnerability in teagood-nalikoli87 originates from its malicious code that modifies the package.json file. It removes private flags, alters version numbers, and generates random package names, which leads to the continuous republishing of these 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.

How To Fix

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

npm uninstall teagood-nalikoli87

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-nalikoli87 package and look for alternative packages that provide similar functionality without the associated risks. Additionally, you can monitor your package-lock.json file for any unauthorized changes.

Conclusion

The teagood-nalikoli87 package poses a significant risk due to its malicious code designed to manipulate the npm registry. It is crucial for developers to remove this package from their projects and monitor for any unauthorized changes. Utilizing tools like Vulert can help in identifying and mitigating such vulnerabilities in the future.

See every vulnerability recorded for teagood-nalikoli87 →

Share this vulnerability

FAQ

teagood-nalikoli87 is an npm package involved in a malicious campaign that aims to inflate developer reputation scores through the creation of numerous derivative packages.

The vulnerability can lead to the installation of compromised packages that may contain malicious code, potentially compromising your project's security.

If you have installed teagood-nalikoli87, you should uninstall it immediately using the command npm uninstall teagood-nalikoli87 and check for any dependencies that may be affected.

Yes, you can use tools like Vulert, which monitors your package-lock.json file for open-source vulnerabilities in real-time. You can check your application for vulnerabilities using the Vulert playground without any signup.

To prevent similar vulnerabilities, regularly audit your dependencies, use trusted packages, and consider employing automated tools like Vulert to monitor for vulnerabilities.

How To Fix

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

npm uninstall teagood-nalikoli87

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