Malicious Code Injection in teagood-nalikoli35 Package

teagood-nalikoli35 Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-167589: Malicious code in teagood-nalikoli35 (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

The teagood-nalikoli35 package is part of the tea.xyz token reward campaign, which has been known to flood the npm registry with numerous packages. These packages are designed to inflate developer reputation scores for token rewards through automated scripts. The malicious nature of this package lies in its ability to modify essential files and republish itself under various names, thus compromising the integrity of the npm ecosystem.

Vulnerability Detail

The vulnerability originates from malicious code embedded within the teagood-nalikoli35 package. This code is designed to alter the package.json file by removing private flags, changing version numbers, and generating random package names. The continuous republishing of these variants leads to pollution of the npm registry, which can mislead developers and potentially 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-nalikoli35

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-nalikoli35 package and look for alternative packages that provide similar functionality without the associated risks. Additionally, consider using tools like Vulert to monitor your project for vulnerabilities in real-time.

Conclusion

The teagood-nalikoli35 package poses a significant risk due to its malicious code that alters essential project files and repopulates the npm registry with harmful variants. It is essential to remove this package and monitor your project for vulnerabilities to maintain security and integrity.

See every vulnerability recorded for teagood-nalikoli35 →

Share this vulnerability

FAQ

teagood-nalikoli35 is an npm package associated with the tea.xyz token reward campaign, known for flooding the npm registry with malicious packages.

The malicious code can modify your package.json file, remove private flags, and republish variants, leading to potential security risks and pollution of the npm registry.

You should uninstall the teagood-nalikoli35 package immediately and monitor your project for any vulnerabilities using tools like Vulert.

Regularly audit your dependencies, use tools like Vulert for real-time monitoring, and be cautious when adding new packages from unverified sources.

Yes, you can use the Vulert playground at Vulert Scanner 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-nalikoli35

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