Malicious Code Injection in teagood-nalikoli129 Package

teagood-nalikoli129 Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-167538: Malicious code in teagood-nalikoli129 (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-nalikoli129 package is part of the tea.xyz token reward campaign, which has been known to flood the npm registry with packages. These packages are designed to generate and publish derivative versions with randomized names, aiming to inflate developer reputation scores for token rewards. The package's functionality revolves around automating the publication process, but it has been exploited to introduce malicious scripts.

Vulnerability Detail

The vulnerability in teagood-nalikoli129 originates from its design to include autopublish scripts that modify the package.json file. This modification removes private flags, alters version numbers, and generates random package names, leading to continuous republishing of variants. The malicious payload can pollute the npm registry, potentially compromising other packages and affecting developers' reputations.

How To Fix

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

npm uninstall teagood-nalikoli129

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 workaround, you can temporarily avoid using the teagood-nalikoli129 package and monitor your project for any dependencies that may have been affected by this malicious package. Additionally, consider using tools like Vulert to monitor your package-lock.json for vulnerabilities.

Conclusion

The teagood-nalikoli129 package poses a significant risk due to its malicious code that modifies package.json and repopulates the npm registry with harmful variants. It is crucial to remove this package and monitor your project for vulnerabilities to maintain the integrity of your software.

See every vulnerability recorded for teagood-nalikoli129 →

Share this vulnerability

FAQ

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

The vulnerability can lead to the pollution of the npm registry, affecting the integrity of your project and potentially compromising other packages.

You should remove the teagood-nalikoli129 package from your project and monitor for any dependencies that may have been affected.

Yes, you can use Vulert, which monitors your package-lock.json for open-source vulnerabilities in real-time without requiring code access.

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-nalikoli129

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