Malicious Code Injection in teagood-nalikoli18: A Threat to npm Users

teagood-nalikoli18 Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-167570: Malicious code in teagood-nalikoli18 (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-nalikoli18 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 associated with generating and publishing derivative packages. Its primary function is to inflate developer reputation scores for rewards related to the tea protocol. 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-nalikoli18 originates from its malicious payload, which modifies the package.json file to remove private flags, alters version numbers, and generates random package names. This behavior leads to the automatic generation and republishing of numerous derivative packages, effectively polluting the npm registry. The ramifications include potential security risks for developers who unknowingly install 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-nalikoli18

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-nalikoli18 package and look for alternative packages that provide similar functionality without the associated risks. Additionally, you can monitor your project dependencies using tools like Vulert to receive real-time alerts for any open-source vulnerabilities.

Conclusion

The discovery of malicious code in the teagood-nalikoli18 package poses a significant threat to the npm ecosystem. Developers should take immediate action to remove the package and monitor their dependencies for vulnerabilities. Utilizing tools like Vulert can help maintain the security of your projects.

See every vulnerability recorded for teagood-nalikoli18 →

Share this vulnerability

FAQ

teagood-nalikoli18 is an npm package associated with the tea.xyz token reward campaign, designed to generate and publish derivative packages.

The malicious code modifies your package.json file, removes private flags, and generates random package names, potentially leading to security vulnerabilities.

You should uninstall the package immediately using 'npm uninstall teagood-nalikoli18' and monitor for any updates or patches.

You can use tools like Vulert, which monitors your package-lock.json file to alert you in real-time for any open-source vulnerabilities.

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

How To Fix

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

npm uninstall teagood-nalikoli18

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